Well, to tell you the truth, it will probably take longer to rig something up on your own, than it would be to plug in a "reporting tool".
The problem is, you have to format the document for the printer. which means you would have to analyze what is to be printed yourself and determine the page breaks. Any "reporting tool" API will already have done this, and you simply need to use it.
In general, it is quicker to search for, preliminary test, and plug in a third party API than it is to "reinvent" the wheel. There will be times where it is not allowed, has much more than is needed, or is simply to complex, but those are generally the exception to the rule.
And this,
I dnt have time to go for reporting tool
tells me I was right on the money with
you simply want us to do it for you
.
To summarise, it will be quicker (I believe) to find a "reporting tool" than it will be to do it yourself, regardless of the "help"/code you might get here. That code would still need to be analysed and then adapted so it works with your code and for your puposes, and even that alone (even if I were to include a code block) would probably take just as long (or very possibly longer) than it would to plug in a "reporting tool".