<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: adobe forms in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748076#M901827</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Interactive Forms based on Adobe software is SAP's new solution for forms development. Its first release has the focus on interactive use of forms. High-volume printing is supported in principle, but - being a new solution - the performance has not yet reached the same level as Smart Forms or SAPscript, two established solutions that had years to grow. Interactive Forms is the only solution that will continue to be enhanced with new features, while SAPscript and Smart Forms will be supported without limitations.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;When (or if) to move to Interactive Forms depends on your requirements. For interactive forms usage, i.e. the new functions, you have no choice, as the existing solutions don't support it. High-volume print scenarios need to be carefully analyzed to see whether your concrete requirements can be met at this point.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;However, it is possible to move to Smart Forms and design your forms in such a way that a migration at any point in the future would be but a small step. Smart Forms offers from Web AS 6.40 a migration wizard to Interactive Forms. Technically, everything can be migrated, but we recommend against things like ABAP program nodes, for example.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;You are not forced to ever go to Interactive Forms if you don't want to. It really depends on whether your client needs any of the new features in Interactive Forms. Also, if they are currently working with JetForms, they could enquire with Adobe directly what migration path they offer to the joint solution.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;please check this link&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/adobe" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/adobe&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://wwwimages.adobe.com/www.adobe.com/enterprise/partners/pdfs/bwp_interactive_forms_adobe.pdf" target="test_blank"&gt;http://wwwimages.adobe.com/www.adobe.com/enterprise/partners/pdfs/bwp_interactive_forms_adobe.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;chk these links:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/interactiveforms-elearning" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/interactiveforms-elearning&lt;/A&gt;&lt;/P&gt;&lt;P&gt;/people/thomas.jung3/blog/2005/07/13/lessons-learned-from-adobe-forms-development&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/community.user/blog/2006/11/20/search-help-in-isr-adobe-forms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/franklin.herbas/blog/2005/12/13/2d-barcode-pdf-forms-with-sap-netweaver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/849b3482206353e10000000a11466f/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/43/849b3482206353e10000000a11466f/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/82538c0c4458bbe10000000a422035/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/43/82538c0c4458bbe10000000a422035/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/46/55c841d202c317e10000000a155106/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/46/55c841d202c317e10000000a155106/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/6d/bd2d828aa04eeb9451aad0d02ae9a0/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/6d/bd2d828aa04eeb9451aad0d02ae9a0/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/dd/60694fddb74ad88cdb7d2a094f3dd2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/dd/60694fddb74ad88cdb7d2a094f3dd2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/interactiveforms" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/interactiveforms&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap.com/company/press/press.epx?pressID=2785" target="test_blank"&gt;http://www.sap.com/company/press/press.epx?pressID=2785&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.adobe.com/enterprise/partners/sap.html" target="test_blank"&gt;http://www.adobe.com/enterprise/partners/sap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.adobe.com/enterprise/partners/pdfs/sap_datasheet.pdf" target="test_blank"&gt;http://www.adobe.com/enterprise/partners/pdfs/sap_datasheet.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward id helpful&lt;/P&gt;&lt;P&gt;raam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Apr 2008 11:53:35 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-24T11:53:35Z</dc:date>
    <item>
      <title>adobe forms</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748074#M901825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;              what is use of adobe forms in abap/4 ? and if i learn is it good?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Apr 2008 11:44:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748074#M901825</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-24T11:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: adobe forms</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748075#M901826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hii,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first step for an offline scenario would be to design a form.The steps for form design are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149;Start transaction SFP&lt;/P&gt;&lt;P&gt;&amp;#149;Create an interface &lt;/P&gt;&lt;P&gt;&amp;#149;Create a form object &lt;/P&gt;&lt;P&gt;&amp;#149;In the context link the required parameters from the interface&lt;/P&gt;&lt;P&gt;&amp;#149;Finally create the layout of the form and activate the form.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will not go to the details as this has been covered in by other weblogs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The interesting thing is that once we designthe form assign an interface and generate we have the use of the Generated Function Module which we cna be used in an ABAP program to create the fillable form.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The application program would consist of&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;#149;Data retrieval and processing : A select statement for the pre populates information&lt;/P&gt;&lt;P&gt;&amp;#149;Obtain the name of the Generated Function Module of the form&lt;/P&gt;&lt;P&gt;&amp;#149;Start the form processing&lt;/P&gt;&lt;P&gt;&amp;#149;Call the Generated Function Module&lt;/P&gt;&lt;P&gt;&amp;#149;End form processing&lt;/P&gt;&lt;P&gt;&amp;#149;Send the form to the vendor using Business communication services (BCS)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data retrieval and processing&lt;/P&gt;&lt;P&gt;This is a simple select statement to select the vendor number, name and company code from the vendor table LFA1 based on the vendor from the selection screen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Get vendor data &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select single lifnr name1 bukrs from lfa1 into wa_vndbnk where lifnr = p_lifnr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Get the generated function module&lt;/P&gt;&lt;P&gt;The next step is to get the generated function module. Call function module FP_FUNCTION_MODULE_NAME and pass the form name to it. The parameter e_funcname will contain the name of the generated function module name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First get name of the generated function module &lt;/P&gt;&lt;P&gt;call function 'FP_FUNCTION_MODULE_NAME'&lt;/P&gt;&lt;P&gt;exporting&lt;/P&gt;&lt;P&gt;i_name = 'ZVK_TESTHD'&lt;/P&gt;&lt;P&gt;importing&lt;/P&gt;&lt;P&gt;e_funcname = fm_name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Start the form processing&lt;/P&gt;&lt;P&gt;I use the function FP_JOB_OPEN to open the form for printing. What is of interest here is the parameter ie_outputparams. This determines printer settings. This parameter is also what I used to inform the the generated function module to return a PDF file back. Since this is an offline scenario and there is no printing involved I suppressed the printer dialog popup as well. If you want your form to be to use a specific ADS you can explicitly give the RFC connection to connect to your ADS using the parameter 'CONNECTION'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set output parameters and open spool job &lt;/P&gt;&lt;P&gt;fp_outputparams-nodialog = 'X'. " suppress printer dialog popup&lt;/P&gt;&lt;P&gt;fp_outputparams-GETPDF = 'X'. " launch print preview&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call function 'FP_JOB_OPEN'&lt;/P&gt;&lt;P&gt;changing&lt;/P&gt;&lt;P&gt;ie_outputparams = fp_outputparams&lt;/P&gt;&lt;P&gt;exceptions&lt;/P&gt;&lt;P&gt;cancel = 1&lt;/P&gt;&lt;P&gt;usage_error = 2&lt;/P&gt;&lt;P&gt;system_error = 3&lt;/P&gt;&lt;P&gt;internal_error = 4&lt;/P&gt;&lt;P&gt;others = 5.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call the generated function module&lt;/P&gt;&lt;P&gt;I am finally ready to call the generated function module This is where I specify thay my form needs to be fillable. There is a standard parameter /1bcdwb/docparams which is used to set the forms locale. This also has a field where I tell the form that it is fillable. Once this parameter is set if the license is available in the ADS a fillable savable form will be returned when the function module is executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set form language and country (-&amp;gt;form locale) &lt;/P&gt;&lt;P&gt;fp_docparams-langu = 'E'.&lt;/P&gt;&lt;P&gt;fp_docparams-country = 'US'.&lt;/P&gt;&lt;P&gt;fp_docparams-FILLABLE = 'X'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now call the generated function module &lt;/P&gt;&lt;P&gt;call function fm_name&lt;/P&gt;&lt;P&gt;exporting&lt;/P&gt;&lt;P&gt;/1bcdwb/docparams = fp_docparams&lt;/P&gt;&lt;P&gt;Z_VNDBNK = wa_vndbnk&lt;/P&gt;&lt;P&gt;importing&lt;/P&gt;&lt;P&gt;/1BCDWB/FORMOUTPUT = fp_formoutput&lt;/P&gt;&lt;P&gt;exceptions&lt;/P&gt;&lt;P&gt;usage_error = 1&lt;/P&gt;&lt;P&gt;system_error = 2&lt;/P&gt;&lt;P&gt;internal_error = 3&lt;/P&gt;&lt;P&gt;others = 4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dont forget to close the print job&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Close spool job &lt;/P&gt;&lt;P&gt;call function 'FP_JOB_CLOSE'&lt;/P&gt;&lt;P&gt;exceptions&lt;/P&gt;&lt;P&gt;usage_error = 1&lt;/P&gt;&lt;P&gt;system_error = 2&lt;/P&gt;&lt;P&gt;internal_error = 3&lt;/P&gt;&lt;P&gt;others = 4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The fields fp_formoutput-PDF contains our fillable form.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now that the system has generated a fillable PDF form I can email this to anyone using BCS. The user can than open the form and fill it or save it somewhere and fill it as and when he pleases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vani Krishnamoorthy Netweaver tools consultant. SAP America,Inc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Add to: del.icio.us | Digg | Reddit &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is my first attempt at Blogging. Any comment/suggestion will be welcome.&lt;/P&gt;&lt;P&gt;Comment on this weblog&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Showing messages 1 through 7 of 7. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Titles Only Main Topics Oldest First &lt;/P&gt;&lt;P&gt;u00B7 Fillable form&lt;/P&gt;&lt;P&gt;2006-08-15 13:34:11 Girish Kumar Business Card Reply&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I passed fillable = 'X' no pdf is generated and fp_formoutput-PDF is blank. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I passed fillable = '' pdf is generated and can be output. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this work on ERP2004? Could you please try? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The article &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c2567f2b-0b01-0010-b7b5-977cbf80665d" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c2567f2b-0b01-0010-b7b5-977cbf80665d&lt;/A&gt;&lt;/P&gt;&lt;P&gt;has both sides of fillable form using ABAP. It covers creating as well as reading the data from the form. &lt;/P&gt;&lt;P&gt;u00A7 Adobe forms with ABAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an excellent blog. Looking more such blogs from you. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried to develop Offline Interactive Forms Using ABAP using your technicle article. I struck at one point, where PDF_DATA definition is not given in the article and how to get data into this. Could you please let us know the missing code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Adobe Interactive Forms: Overview&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since SAP NetWeaver (Web) Application Server 6.40 (SAP NetWeaver 04), Adobe document services (ADS) have been available. This is a set of runtime services deployed on the Application Server that provide a range of form and document creation and manipulation functions. The key capabilities of the ADS are the creation of documents in PDF and various print formats from XML form templates and current system data, and the extraction of user-entered data from interactive PDF forms for rendering and generating Adobe Forms. SAP has also provided a single programmatic interface called PDF Document Object (or PDF Object) that enables developers to communicate with ADS. PDF Object is available both in ABAP as well as Java.&lt;/P&gt;&lt;P&gt;This paper shows the basic steps you need for creating an Adobe Interactive Form for offline scenario using the SAP delivered function modules and the PDF object for extracting the data. The paper assumes that the reader already has the basics of PDF based form development.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Business Example&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The business example in this paper is an offline scenario by which a vendor will be able to fill bank information and send this information back so that this can be updated in the vendor master. The SAP vendor no and vendor name are pre populated in the form. Then this form is emailed to the vendor. The vendor completes the form and sends it back. The data from the PDF form is retrieved and the vendor master is updated. This does not require any Web Dynpro development&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Designing a Form&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first step for an offline scenario would be to design a form. This topic has been covered in detail in other How-To documents and is also explained in details in SAP documentation (Designing PDF Forms). The steps for form design are:&lt;/P&gt;&lt;P&gt;&amp;#149; Start transaction SFP&lt;/P&gt;&lt;P&gt;&amp;#149; Create an interface&lt;/P&gt;&lt;P&gt;&amp;#149; Create a form object&lt;/P&gt;&lt;P&gt;&amp;#149; In the context link the required parameters from the interface&lt;/P&gt;&lt;P&gt;&amp;#149; Finally create the layout of the form and activate the form.&lt;/P&gt;&lt;P&gt;This creates a function module that encapsulates the form description. We will be creating an application program that collects the relevant data, calls this function module so as to generate the fillable PDF form.&lt;/P&gt;&lt;P&gt;Make sure that the ADS is configured and ready for use (including a valid credential &amp;#150; See SAP Note 736902). The credential is required if, for example, the form is to be saved after filling.&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 3&lt;/P&gt;&lt;P&gt;Form Builder&lt;/P&gt;&lt;P&gt;Interface&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 4&lt;/P&gt;&lt;P&gt;Form Context&lt;/P&gt;&lt;P&gt;Form Layout&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 5&lt;/P&gt;&lt;P&gt;Generate and Send the Form&lt;/P&gt;&lt;P&gt;The next step is to write the ABAP program which will create the form and email it to the vendor so that it can be filled offline.&lt;/P&gt;&lt;P&gt;The program will have the following steps:&lt;/P&gt;&lt;P&gt;&amp;#149; Data retrieval and processing : A select statement for the pre-populated information&lt;/P&gt;&lt;P&gt;&amp;#149; Obtain the name of the Generated Function Module of the form&lt;/P&gt;&lt;P&gt;&amp;#149; Start the form processing&lt;/P&gt;&lt;P&gt;&amp;#149; Call the Generated Function Module&lt;/P&gt;&lt;P&gt;&amp;#149; End form processing&lt;/P&gt;&lt;P&gt;&amp;#149; Send the form to the vendor using Business communication services (BCS)&lt;/P&gt;&lt;P&gt;Data Retrieval and Processing&lt;/P&gt;&lt;P&gt;This can be as simple as a select statement to complex data selection. In this example we select the vendor number, name and company code from the vendor table LFA1 based on the vendor from the selection screen&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Get vendor data &lt;/P&gt;&lt;P&gt;select single lifnr name1 bukrs from lfa1 into wa_vndbnk where lifnr = p_lifnr.&lt;/P&gt;&lt;P&gt;Get the Generated Function Module&lt;/P&gt;&lt;P&gt;The next step is to get the generated function module. Call function module FP_FUNCTION_MODULE_NAME and pass the form name to it. The parameter e_funcname will contain the name of the generated function module name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First get name of the generated function module &lt;/P&gt;&lt;P&gt;call function 'FP_FUNCTION_MODULE_NAME'&lt;/P&gt;&lt;P&gt;exporting&lt;/P&gt;&lt;P&gt;i_name = 'ZVK_TESTHD'&lt;/P&gt;&lt;P&gt;importing&lt;/P&gt;&lt;P&gt;e_funcname = fm_name.&lt;/P&gt;&lt;P&gt;Start the Form Processing&lt;/P&gt;&lt;P&gt;Form printing needs to be explicitly opened and closed. Use the function FP_JOB_OPEN to open the form for printing. The parameter ie_outputparams determines printer settings. This parameter is also where we ask the generated function module to return a PDF file back. Since this is an offline scenario and there is no printing involved we need to suppress the printer dialog popup as well. Optionally there is a parameter connection which can be used to determine the RFC destination for ADS.&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set output parameters and open spool job &lt;/P&gt;&lt;P&gt;fp_outputparams-nodialog = 'X'. " suppress printer dialog popup&lt;/P&gt;&lt;P&gt;fp_outputparams-GETPDF = 'X'. " launch print preview&lt;/P&gt;&lt;P&gt;call function 'FP_JOB_OPEN'&lt;/P&gt;&lt;P&gt;changing&lt;/P&gt;&lt;P&gt;ie_outputparams = fp_outputparams&lt;/P&gt;&lt;P&gt;exceptions&lt;/P&gt;&lt;P&gt;cancel = 1&lt;/P&gt;&lt;P&gt;usage_error = 2&lt;/P&gt;&lt;P&gt;system_error = 3&lt;/P&gt;&lt;P&gt;internal_error = 4&lt;/P&gt;&lt;P&gt;others = 5.&lt;/P&gt;&lt;P&gt;Call the Generated Function Module&lt;/P&gt;&lt;P&gt;This is similar to the generated function module in Smart Forms. Since the parameters of the function module are defined in the interface, this will vary from form to form. However, /1bcdwb/docparams is a standard parameter. This is used to set the forms locale. This is also where we tell the form that it is fillable. Once this parameter is set - if the ADS is configured correctly (including the credential) - a fillable savable form will be returned when the function module is executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set form language and country (-&amp;gt;form locale) &lt;/P&gt;&lt;P&gt;fp_docparams-langu = 'E'.&lt;/P&gt;&lt;P&gt;fp_docparams-country = 'US'.&lt;/P&gt;&lt;P&gt;fp_docparams-FILLABLE = 'X'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now call the generated function module &lt;/P&gt;&lt;P&gt;call function fm_name&lt;/P&gt;&lt;P&gt;exporting&lt;/P&gt;&lt;P&gt;/1bcdwb/docparams = fp_docparams&lt;/P&gt;&lt;P&gt;Z_VNDBNK = wa_vndbnk&lt;/P&gt;&lt;P&gt;importing&lt;/P&gt;&lt;P&gt;/1BCDWB/FORMOUTPUT = fp_formoutput&lt;/P&gt;&lt;P&gt;exceptions&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 7&lt;/P&gt;&lt;P&gt;usage_error = 1&lt;/P&gt;&lt;P&gt;system_error = 2&lt;/P&gt;&lt;P&gt;internal_error = 3&lt;/P&gt;&lt;P&gt;others = 4.&lt;/P&gt;&lt;P&gt;End Form Processing&lt;/P&gt;&lt;P&gt;Use the function FP_JOB_CLOSE to close the form for printing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Close spool job &lt;/P&gt;&lt;P&gt;call function 'FP_JOB_CLOSE'&lt;/P&gt;&lt;P&gt;exceptions&lt;/P&gt;&lt;P&gt;usage_error = 1&lt;/P&gt;&lt;P&gt;system_error = 2&lt;/P&gt;&lt;P&gt;internal_error = 3&lt;/P&gt;&lt;P&gt;others = 4.&lt;/P&gt;&lt;P&gt;Send the Form to the Vendor&lt;/P&gt;&lt;P&gt;The PDF file generated is available in the parameter fp_result which is returned by the generated function module. The next step would be to extract this PDF and send it to the vendor using BCS.&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;buffer = fp_formoutput-PDF "PDF file from function module&lt;/P&gt;&lt;P&gt;TABLES&lt;/P&gt;&lt;P&gt;binary_tab = lt_att_content_hex.&lt;/P&gt;&lt;P&gt;CLASS cl_bcs DEFINITION LOAD.&lt;/P&gt;&lt;P&gt;DATA:&lt;/P&gt;&lt;P&gt;lo_send_request TYPE REF TO cl_bcs VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;lo_send_request = cl_bcs=&amp;gt;create_persistent( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message body and subject &lt;/P&gt;&lt;P&gt;DATA:&lt;/P&gt;&lt;P&gt;lt_message_body TYPE bcsy_text VALUE IS INITIAL,&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 8&lt;/P&gt;&lt;P&gt;lo_document TYPE REF TO cl_document_bcs VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;APPEND 'Dear Vendor,' TO lt_message_body.&lt;/P&gt;&lt;P&gt;append ' ' to lt_message_body.&lt;/P&gt;&lt;P&gt;APPEND 'Please fill the attached form and send it back to us.'&lt;/P&gt;&lt;P&gt;TO lt_message_body.&lt;/P&gt;&lt;P&gt;append ' ' to lt_message_body.&lt;/P&gt;&lt;P&gt;APPEND 'Thank You,' TO lt_message_body.&lt;/P&gt;&lt;P&gt;lo_document = cl_document_bcs=&amp;gt;create_document(&lt;/P&gt;&lt;P&gt;i_type = 'RAW'&lt;/P&gt;&lt;P&gt;i_text = lt_message_body&lt;/P&gt;&lt;P&gt;i_subject = 'Vendor Payment Form' ).&lt;/P&gt;&lt;P&gt;DATA: lx_document_bcs TYPE REF TO cx_document_bcs VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;TRY.&lt;/P&gt;&lt;P&gt;lo_document-&amp;gt;add_attachment(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;i_attachment_type = 'PDF'&lt;/P&gt;&lt;P&gt;i_attachment_subject = 'Vendor Payment Form'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I_ATTACHMENT_SIZE = &lt;/P&gt;&lt;P&gt;I_ATTACHMENT_LANGUAGE = SPACE &lt;/P&gt;&lt;P&gt;I_ATT_CONTENT_TEXT = &lt;/P&gt;&lt;P&gt;I_ATTACHMENT_HEADER = &lt;/P&gt;&lt;P&gt;i_att_content_hex = lt_att_content_hex ).&lt;/P&gt;&lt;P&gt;CATCH cx_document_bcs INTO lx_document_bcs.&lt;/P&gt;&lt;P&gt;ENDTRY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Add attachment &lt;/P&gt;&lt;P&gt;Pass the document to send request &lt;/P&gt;&lt;P&gt;lo_send_request-&amp;gt;set_document( lo_document ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create sender &lt;/P&gt;&lt;P&gt;DATA:&lt;/P&gt;&lt;P&gt;lo_sender TYPE REF TO if_sender_bcs VALUE IS INITIAL,&lt;/P&gt;&lt;P&gt;l_send type ADR6-SMTP_ADDR value 'email address',&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 9&lt;/P&gt;&lt;P&gt;lo_sender = cl_cam_address_bcs=&amp;gt;create_internet_address( l_send ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set sender &lt;/P&gt;&lt;P&gt;lo_send_request-&amp;gt;set_sender(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;i_sender = lo_sender ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create recipient &lt;/P&gt;&lt;P&gt;*DATA:&lt;/P&gt;&lt;P&gt;lo_recipient TYPE REF TO if_recipient_bcs VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;lo_recipient = cl_sapuser_bcs=&amp;gt;create( sy-uname ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set recipient &lt;/P&gt;&lt;P&gt;lo_send_request-&amp;gt;add_recipient(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;i_recipient = lo_recipient&lt;/P&gt;&lt;P&gt;i_express = 'X' ).&lt;/P&gt;&lt;P&gt;lo_send_request-&amp;gt;add_recipient(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;i_recipient = lo_recipient&lt;/P&gt;&lt;P&gt;i_express = 'X' ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Send email &lt;/P&gt;&lt;P&gt;DATA: lv_sent_to_all(1) TYPE c VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;lo_send_request-&amp;gt;send(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;i_with_error_screen = 'X'&lt;/P&gt;&lt;P&gt;RECEIVING&lt;/P&gt;&lt;P&gt;result = lv_sent_to_all ).&lt;/P&gt;&lt;P&gt;COMMIT WORK.&lt;/P&gt;&lt;P&gt;message 'The payment form has been emailed to the Vendor' type 'I'.&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 10&lt;/P&gt;&lt;P&gt;Generated Email&lt;/P&gt;&lt;P&gt;Payment Form Emailed to Vendor (PDF 82 KB)&lt;/P&gt;&lt;P&gt;Filled Form from the Vendor (PDF 82 KB)&lt;/P&gt;&lt;P&gt;Extract Data&lt;/P&gt;&lt;P&gt;Once the vendor fills the form and sends it back the data needs to be extracted from the PDF file. In this example we are assuming that the vendor sends back the whole PDF file. But we can also make it easier and send only the data as an XML file when the vendor hits the SUBMIT button. For this we will use the PDF document object. SAP provides us with the interfaces IF_FP (Form) and IF_FP_PDF_OBJECT (PDF object). These two are the main interfaces which we will be using. The following are the steps to extract the data from the PDF file.&lt;/P&gt;&lt;P&gt;&amp;#149; Upload the form to the system&lt;/P&gt;&lt;P&gt;&amp;#149; Instantiate a PDF object and assign the PDF file to the object&lt;/P&gt;&lt;P&gt;&amp;#149; Extract the data from the PDF object&lt;/P&gt;&lt;P&gt;&amp;#149; Update the vendor master&lt;/P&gt;&lt;P&gt;Upload the Form&lt;/P&gt;&lt;P&gt;To keep things simple in this example the filled form is saved in the C drive and uploaded using CL_GUI_FRONTEND_SERVICES. But there are many other options like sending the email directly to SAP, Receiving the data using http post etc. but this would be beyond the scope of this paper&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 11&lt;/P&gt;&lt;P&gt;CALL METHOD cl_gui_frontend_services=&amp;gt;file_open_dialog&lt;/P&gt;&lt;P&gt;CHANGING&lt;/P&gt;&lt;P&gt;file_table = lt_file_table&lt;/P&gt;&lt;P&gt;rc = lv_rc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;USER_ACTION = &lt;/P&gt;&lt;P&gt;FILE_ENCODING = &lt;/P&gt;&lt;P&gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;file_open_dialog_failed = 1&lt;/P&gt;&lt;P&gt;cntl_error = 2&lt;/P&gt;&lt;P&gt;error_no_gui = 3&lt;/P&gt;&lt;P&gt;not_supported_by_gui = 4&lt;/P&gt;&lt;P&gt;OTHERS = 5.&lt;/P&gt;&lt;P&gt;IF sy-subrc 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO &lt;/P&gt;&lt;P&gt;WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. &lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;READ TABLE lt_file_table&lt;/P&gt;&lt;P&gt;INTO lv_filename&lt;/P&gt;&lt;P&gt;INDEX 1.&lt;/P&gt;&lt;P&gt;*lv_filename = p_pdf.&lt;/P&gt;&lt;P&gt;cl_gui_frontend_services=&amp;gt;gui_upload(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;filename = lv_filename&lt;/P&gt;&lt;P&gt;filetype = 'BIN' "Binary&lt;/P&gt;&lt;P&gt;IMPORTING&lt;/P&gt;&lt;P&gt;filelength = lv_filelength&lt;/P&gt;&lt;P&gt;CHANGING&lt;/P&gt;&lt;P&gt;data_tab = lt_rawtab&lt;/P&gt;&lt;P&gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;file_open_error = 1&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 12&lt;/P&gt;&lt;P&gt;file_read_error = 2&lt;/P&gt;&lt;P&gt;no_batch = 3&lt;/P&gt;&lt;P&gt;gui_refuse_filetransfer = 4&lt;/P&gt;&lt;P&gt;invalid_type = 5&lt;/P&gt;&lt;P&gt;no_authority = 6&lt;/P&gt;&lt;P&gt;unknown_error = 7&lt;/P&gt;&lt;P&gt;bad_data_format = 8&lt;/P&gt;&lt;P&gt;header_not_allowed = 9&lt;/P&gt;&lt;P&gt;separator_not_allowed = 10&lt;/P&gt;&lt;P&gt;header_too_long = 11&lt;/P&gt;&lt;P&gt;unknown_dp_error = 12&lt;/P&gt;&lt;P&gt;access_denied = 13&lt;/P&gt;&lt;P&gt;dp_out_of_memory = 14&lt;/P&gt;&lt;P&gt;disk_full = 15&lt;/P&gt;&lt;P&gt;dp_timeout = 16&lt;/P&gt;&lt;P&gt;not_supported_by_gui = 17&lt;/P&gt;&lt;P&gt;error_no_gui = 18&lt;/P&gt;&lt;P&gt;OTHERS = 19 ).&lt;/P&gt;&lt;P&gt;Instantiate the PDF Object&lt;/P&gt;&lt;P&gt;The uploaded file is just a stream of raw data. We need to extract just the data from this file. For this we feed the data to the PDF object and use the methods to extract data. The first step would be to create a form object. Once a form object is created we can create a PDF object and assign the file to this object. The PDF object also needs to be informed that the mode would be to extract data. We can then generate a form by connecting to the assigned ADS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Get FP reference &lt;/P&gt;&lt;P&gt;DATA: lo_fp TYPE REF TO if_fp VALUE IS INITIAL,&lt;/P&gt;&lt;P&gt;lo_fp = cl_fp=&amp;gt;get_reference( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For handling exceptions &lt;/P&gt;&lt;P&gt;DATA: lo_fpex TYPE REF TO cx_fp_runtime VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;TRY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create PDF Object using destination 'ADS' (&amp;lt;-- this is how it is &lt;/P&gt;&lt;P&gt;defined in SM59) &lt;/P&gt;&lt;P&gt;DATA: lo_pdfobj TYPE REF TO if_fp_pdf_object VALUE IS INITIAL.&lt;/P&gt;&lt;P&gt;lo_pdfobj = lo_fp-&amp;gt;create_pdf_object( connection = 'ADS' ).&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 13&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set document &lt;/P&gt;&lt;P&gt;lo_pdfobj-&amp;gt;set_document(&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;pdfdata = pdf_data ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tell PDF object to extract data &lt;/P&gt;&lt;P&gt;lo_pdfobj-&amp;gt;set_extractdata( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Execute the call to ADS &lt;/P&gt;&lt;P&gt;lo_pdfobj-&amp;gt;execute( ).&lt;/P&gt;&lt;P&gt;Extract the Data&lt;/P&gt;&lt;P&gt;Now that we have a PDF object we can extract the data by the simple call of a method. The extracted data is in XML format. We can do a transformation to convert the data to ABAP internal table. In this example the standard identity transformation has been used which needs a few additional steps of replacing the XML namespace. But a custom transformation can be used instead and these additional steps can be avoided.&lt;/P&gt;&lt;P&gt;DATA: xml_data TYPE xstring,&lt;/P&gt;&lt;P&gt;lt_xml_data TYPE STANDARD TABLE OF xstring.&lt;/P&gt;&lt;P&gt;APPEND xml_data TO lt_xml_data.&lt;/P&gt;&lt;P&gt;lo_pdfobj-&amp;gt;get_data(&lt;/P&gt;&lt;P&gt;IMPORTING&lt;/P&gt;&lt;P&gt;formdata = xml_data ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Convert XML data from XSTRING format to STRING format &lt;/P&gt;&lt;P&gt;DATA: lv_xml_data_string TYPE string.&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'ECATT_CONV_XSTRING_TO_STRING'&lt;/P&gt;&lt;P&gt;EXPORTING&lt;/P&gt;&lt;P&gt;im_xstring = xml_data&lt;/P&gt;&lt;P&gt;IMPORTING&lt;/P&gt;&lt;P&gt;ex_string = lv_xml_data_string.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remove NEW-LINE character from XML data in STRING format &lt;/P&gt;&lt;P&gt;CLASS cl_abap_char_utilities DEFINITION LOAD.&lt;/P&gt;&lt;P&gt;REPLACE ALL OCCURENCES OF cl_abap_char_utilities=&amp;gt;newline IN&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 14&lt;/P&gt;&lt;P&gt;lv_xml_data_string WITH ''.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make the XML envelope compliant with identity transform &lt;/P&gt;&lt;P&gt;REPLACE '&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&amp;lt;data&amp;gt;'&lt;/P&gt;&lt;P&gt;IN lv_xml_data_string&lt;/P&gt;&lt;P&gt;WITH '&amp;lt;?xml version="1.0" encoding="iso-8859-1"?&amp;gt;&lt;ABAP xmlns=""&gt;&lt;/ABAP&gt;&lt;/P&gt;&lt;P&gt;:asx="http://www.sap.com/abapxml" version="1.0"&amp;gt;&lt;VALUES&gt;'.&lt;/VALUES&gt;&lt;/P&gt;&lt;P&gt;REPLACE '&amp;lt;/data&amp;gt;'&lt;/P&gt;&lt;P&gt;IN lv_xml_data_string&lt;/P&gt;&lt;P&gt;WITH ''.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apply the identity transform and convert XML into ABAP in one step &lt;/P&gt;&lt;P&gt;DATA: wa_VNDBNK type ZVK_VNDBNK VALUE IS INITIAL,&lt;/P&gt;&lt;P&gt;wa_VENDOR type ZHD_VENDOR value is initial,&lt;/P&gt;&lt;P&gt;lv_subrc TYPE sysubrc VALUE IS INITIAL,&lt;/P&gt;&lt;P&gt;lt_messtab TYPE STANDARD TABLE OF bdcmsgcoll,&lt;/P&gt;&lt;P&gt;l_key type SWR_STRUCT-OBJECT_KEY,&lt;/P&gt;&lt;P&gt;l_pack type zhd_vendor-lifnr.&lt;/P&gt;&lt;P&gt;CALL TRANSFORMATION id&lt;/P&gt;&lt;P&gt;SOURCE XML lv_xml_data_string&lt;/P&gt;&lt;P&gt;RESULT Z_VNDBNK = wa_vndbnk.&lt;/P&gt;&lt;P&gt;Update the Vendor Master&lt;/P&gt;&lt;P&gt;Now that the data is available in the internal table the vendor master is updated using standard SAP function calls.&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 15&lt;/P&gt;&lt;P&gt;Upload the form&lt;/P&gt;&lt;P&gt;u00A9 2006 SAP AG 16&lt;/P&gt;&lt;P&gt;Update Vendor Master&lt;/P&gt;&lt;P&gt;Related Content&lt;/P&gt;&lt;P&gt;1. Interactive Forms Based on Adobe Software&lt;/P&gt;&lt;P&gt;2. Creating Print Forms&lt;/P&gt;&lt;P&gt;3. Creating Interactive Forms u00A9 2006 SAP AG 17&lt;/P&gt;&lt;P&gt;Copyright&lt;/P&gt;&lt;P&gt;u00A9 Copyright 2006 SAP AG. All rights reserved.&lt;/P&gt;&lt;P&gt;No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.&lt;/P&gt;&lt;P&gt;Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.&lt;/P&gt;&lt;P&gt;Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.&lt;/P&gt;&lt;P&gt;IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.&lt;/P&gt;&lt;P&gt;Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.&lt;/P&gt;&lt;P&gt;Oracle is a registered trademark of Oracle Corporation.&lt;/P&gt;&lt;P&gt;UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.&lt;/P&gt;&lt;P&gt;Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.&lt;/P&gt;&lt;P&gt;HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3Cu00AE, World Wide Web Consortium, Massachusetts Institute of Technology.&lt;/P&gt;&lt;P&gt;Java is a registered trademark of Sun Microsystems, Inc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/6addbe30-0d01-0010-49bb-e448c756db44" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/6addbe30-0d01-0010-49bb-e448c756db44&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Adobe forms&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check this link on SDN you will find all the details of ADOBE forms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/interactiveforms" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/interactiveforms&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And you can use this link for eLearning in SDN about ADOBE FORMS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/f5718380-0c01-0010-aebf-8786fb890302" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/f5718380-0c01-0010-aebf-8786fb890302&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;sharad.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: sharad narayan on Apr 24, 2008 1:48 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Apr 2008 11:46:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748075#M901826</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-24T11:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: adobe forms</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748076#M901827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Interactive Forms based on Adobe software is SAP's new solution for forms development. Its first release has the focus on interactive use of forms. High-volume printing is supported in principle, but - being a new solution - the performance has not yet reached the same level as Smart Forms or SAPscript, two established solutions that had years to grow. Interactive Forms is the only solution that will continue to be enhanced with new features, while SAPscript and Smart Forms will be supported without limitations.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;When (or if) to move to Interactive Forms depends on your requirements. For interactive forms usage, i.e. the new functions, you have no choice, as the existing solutions don't support it. High-volume print scenarios need to be carefully analyzed to see whether your concrete requirements can be met at this point.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;However, it is possible to move to Smart Forms and design your forms in such a way that a migration at any point in the future would be but a small step. Smart Forms offers from Web AS 6.40 a migration wizard to Interactive Forms. Technically, everything can be migrated, but we recommend against things like ABAP program nodes, for example.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;You are not forced to ever go to Interactive Forms if you don't want to. It really depends on whether your client needs any of the new features in Interactive Forms. Also, if they are currently working with JetForms, they could enquire with Adobe directly what migration path they offer to the joint solution.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;please check this link&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/adobe" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/adobe&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://wwwimages.adobe.com/www.adobe.com/enterprise/partners/pdfs/bwp_interactive_forms_adobe.pdf" target="test_blank"&gt;http://wwwimages.adobe.com/www.adobe.com/enterprise/partners/pdfs/bwp_interactive_forms_adobe.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;chk these links:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/interactiveforms-elearning" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/interactiveforms-elearning&lt;/A&gt;&lt;/P&gt;&lt;P&gt;/people/thomas.jung3/blog/2005/07/13/lessons-learned-from-adobe-forms-development&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/community.user/blog/2006/11/20/search-help-in-isr-adobe-forms&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/franklin.herbas/blog/2005/12/13/2d-barcode-pdf-forms-with-sap-netweaver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/849b3482206353e10000000a11466f/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/43/849b3482206353e10000000a11466f/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/82538c0c4458bbe10000000a422035/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/43/82538c0c4458bbe10000000a422035/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/46/55c841d202c317e10000000a155106/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/46/55c841d202c317e10000000a155106/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/6d/bd2d828aa04eeb9451aad0d02ae9a0/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/6d/bd2d828aa04eeb9451aad0d02ae9a0/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/dd/60694fddb74ad88cdb7d2a094f3dd2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/dd/60694fddb74ad88cdb7d2a094f3dd2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/interactiveforms" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/interactiveforms&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap.com/company/press/press.epx?pressID=2785" target="test_blank"&gt;http://www.sap.com/company/press/press.epx?pressID=2785&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.adobe.com/enterprise/partners/sap.html" target="test_blank"&gt;http://www.adobe.com/enterprise/partners/sap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.adobe.com/enterprise/partners/pdfs/sap_datasheet.pdf" target="test_blank"&gt;http://www.adobe.com/enterprise/partners/pdfs/sap_datasheet.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward id helpful&lt;/P&gt;&lt;P&gt;raam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Apr 2008 11:53:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748076#M901827</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-24T11:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: adobe forms</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748077#M901828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   there is extensive documentation on creating PDF-based forms for printing in ABAP Workbench (transaction SFP) on the SAP Help Portal at &lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/d2/4a94696de6429cada345c12098b009/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/d2/4a94696de6429cada345c12098b009/frameset.htm&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#47" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#47&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Refer these docs&lt;/P&gt;&lt;P&gt;Configuration of GP for Adobe Forms:http://help.sap.com/saphelp_nw04s/helpdata/en/43/849b3482206353e10000000a11466f/frameset.htm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP CAF Application:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b9ea34c2-0701-0010-e2a2-d8e9cd6d85dc" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b9ea34c2-0701-0010-e2a2-d8e9cd6d85dc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuration for GP:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b9ea34c2-0701-0010-e2a2-d8e9cd6d85dc" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b9ea34c2-0701-0010-e2a2-d8e9cd6d85dc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Limitations and known issues for Adobe forms in GP:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393334393831%7d" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393334393831%7d&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Form-based Process(Adobe):&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee8a84ea-0c01-0010-5691-accfb0a172ed" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee8a84ea-0c01-0010-5691-accfb0a172ed&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;chk these links:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132" target="test_blank"&gt;https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d4fe7fca-0b01-0010-569a-9a9c1ddf4132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/7c3bc67e-0c01-0010-dbb3-908315896909&lt;/A&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;&lt;/P&gt;&lt;P&gt;/people/vani.krishnamoorthy/blog/2006/05/17/fillable-adobe-forms-using-abap&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Kiran Sure&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Apr 2008 11:55:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748077#M901828</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-24T11:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: adobe forms</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748078#M901829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi shirish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;adobe forms are latest enhancements to smartforms.its avery best idea to go with them.no doubt its excellent to learn them.its an advanced technology. so updated with it.&lt;/P&gt;&lt;P&gt;iam providing the link.see it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/advancedsearch?query=adobe+forms&amp;amp;cat=sdn_all" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/advancedsearch?query=adobe+forms&amp;amp;cat=sdn_all&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;karthik&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward me points if usefull.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Apr 2008 12:10:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748078#M901829</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-24T12:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: adobe forms</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748079#M901830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THANKS FOR THE GUIDANCE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have one doubt reg. passing a final internal table to our adobe form using the function module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have my final o/p in final itab.i need all the records in same pdf file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can i get it,which FM can i use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please guide me in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thannks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 May 2008 12:46:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/adobe-forms/m-p/3748079#M901830</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-12T12:46:32Z</dc:date>
    </item>
  </channel>
</rss>

