Regarding adobe form using Webdynpro ABAP

[Former Member]

Hi,

I am new to webdynpro abap.

Currently I am working on a scenario where..

I have a function module which generates the pdf for me based on the vbeln i provide in the first view. The only thing I have to do is to display the generated pdf on explorer.

As for as the examples i gone through.....I should provide the existing form name or the interface name. I don't have either of them as the function module is generating the pdf for me.

Could any one help me on this please....

Thanks,

Vijaya.

[thomas_jung · Accepted solution]

You can still use the InteractiveForm UI element to display the PDF in place, but without the usage of the template property. Instead you feed the complete PDF document to the UI element as an XSTRING context node bound to the pdfSource property.

Have a look at this document on how to display smartforms inside WDA:

[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0de1eb8-0b98-2910-7996-8a3c2fcf6785|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0de1eb8-0b98-2910-7996-8a3c2fcf6785]

It uses the SmartForms function modules to generate the PDF, but the process it shows for using the PDF source of the InteractiveForm UI element is the same regardless.

[Former Member · Accepted solution]

Hi Thomas,

Thanks for your reply.

I went thorugh the exercise you sent me.

Even here I should have some form created right.

In my case, I need not to do anything..just need to pass the vbeln to 'ME_DISPLAY_PURCHASE_DOCUMENT' and this would generate me a pdf and i don't have ne exporting parameter for this function module to bind it to PDF data.

Please help me on this, its an urgent requirement.

Thanks,

Vijaya.

[thomas_jung · Accepted solution]

Well I work for NetWeaver, not ERP so I can't comment definatively upon the function module ME_DISPLAY_PURCHASE_DOCUMENT. My guess however is that this function module isn't going to be appropriate for usage within Web Dynpro ABAP. It must already contain the logic to display the PDF via the SAPGUI if it doesn't export the PDF. For usage in WDA of any way you will need to get access to the raw PDF. You can't expect a function module built for Classic Dynpro/SAPGUI to somehow work in WDA.

I would suggest that you look at the coding inside the function module and pull out the functionality that generates the PDF and throw away the stuff that displays it. I haven't seen the coding of that Function Module, but if you are lucky it will already be broken out into sub-function module calls - one of which might export the PDF content.

[abhimanyu_lagishetti7]

Hi

Instead of showing the PDF, you can provide a FileDownload link and transfer the content, user can open it and see the PDF.

When user clicks the link it automatically asks for open, save option

Abhi

Edited by: Abhimanyu Lagishetti on Jun 9, 2008 1:26 PM