Integrating Forms
For Web Dynpro user interfaces, forms can be created and used in the context of SAP Interactive Forms by Adobe. For efficient and straightforward development of the user interface, you can integrate the Adobe LiveCycle Designer tool with editor and the Adobe UI elements into the development workbench.
There are several ways of using the solution SAP Interactive Forms by Adobe:
● Print scenario
This scenario is used for printing and displaying forms. Unlike in the interactive scenario, only non-input-enabled PDF forms (PDF-based print forms) are used here.
● Interactive scenario
With this scenario, forms containing input-enabled elements are created and edited.
● Offline scenario
Forms that
already exist in the system as MIME objects in the
MIME Repository
are stored here within a Web Dynpro application for display
purposes.
● Scenario with digital signatures
See Digital Signatures in Form Integration
The procedure for creating or using the relevant forms is largely the same for the first two scenarios. However, there is a major difference in how the application is called: When an interactive form is first called, a CAB file, containing a plug-in for the locally installed Adobe Reader, is automatically loaded from the server. This Active Components Framework (ACF) allows you to process form contents on your local computer. However, the ACF is not required for displaying or printing a form.
For Adobe integration, the Adobe Library with the InteractiveForm interface element is provided in the Web Dynpro View Designer.
● SAP NetWeaver AS System with Adobe Document Services (ADS)
Details on installation on the SAP Service Marketplace under the quick link: /installNW.
You can find documentation about importing licenses in the Configuration Guide (http://service.sap.com/adobe -> Media Library -> Documentation).
● Adobe Reader (>= 7.0) installed on your local computer See also note 834573
Execute program FP_PDF_TEST_00 to ensure that the ADS was configured correctly. If the configuration is correct, the out put of the test program will be the version number of the installed ADS.
For information
about potential errors see
Adobe Document
Services Problem Analysis Scenarios.
Forms can be created and maintained independently of Web Dynpro applications using the Form Builder (transaction SFP). For information on creating forms and how to handle the Form Builder, see Form Design with the Form Builder. In each view, you can integrate a form in every view in any component, though it can sometimes help better integrate the form if you create a special view for it.
For details about the various steps involved in creating and using a form, see Integrating a PDF Form in a Web Dynpro Application.

You can find e-learning tutorials with code examples of integrating forms in Web Dynpro applications in SDN. These tutorials were created using NW2004s SPS6.
Several example and test applications are available in the system in package SWDP_TEST to help you get to know the various form integration technologies (ACF or ZCI):
● ZCI
The component WDR_TEST_ADOBE offers a complex test application for various scenarios that can arise when integrating forms using ZCI.
● ACF
The component WDR_TEST_IA_FORMS offers a simple example component for an interactive scenario using ACF.
SAP Notes on SAP Service Marketplace
Number |
Short text |
942506 |
Classification of forms by xACF and ZCI |
955795 |
New creation of Web Dynpro ZCI forms in Form Builder |
834573 |
Interactive Forms based on Adobe sw:Acrobat/Reader version |
947675 |
ISR/Adobe: New layout category ZCI as of ERP 2005, SP 5 |
940637 |
OFFI: SetMergeTemplate for Adobe Template Designer |
944954 |
Preassigning interactive forms with script |
978037 |
Converting an ACF-based UI element to ZCI |