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.
As of NetWeaver 7.0 (NW 7.0) SPS10 forms can be integrated using Zero Client Installation (ZCI).
As of NetWeaver 7.0 SPS10 we strongly recommend you use ZCI forms with an XML interface only. Because additional central features have been added in subsequent SPs (input help and dropdown list boxes), we generally recommend that you always use the most up-to-date Support Package for Web Dynpro ABAP.
We recommend that you always use forms with an XML interface. Existing forms with an ABAP Dictionary-based interface can be used as print forms. We do not recommend their use as interactive forms.
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.
We recommend you use interactive forms only after carefully checking the requirements of your application. Interactive forms should only be used if a PDF-based form really does have advantages over a normal Web Dynpro view. This can include for instance scenarios in which paper-based processes are to be replaced or complimented by an online scenario with exactly the same form layout. Other cases can be applications where, in addition to the online scenario the same form is needed in static form for printing, archiving, sending by e-mail, or for other purposes.
● Offline scenario
Forms that
already exist in the system as MIME objects in the MIME Repository
are stored, or are uploaded (see File Upload) 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. There is however an essential difference with ACF forms when you call applications: When you first call an interactive form 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.
Zero Client Installation (ZCI) and Active Component Framework (ACF)
Interactive forms in the ISR framework are part of ZCI. They can be used as of SAP NetWeaver SPS 10 at runtime in Web Dynpro for ABAP based on Zero Client Installation (ZCI). To enable this, the forms must contain special scripting, which you insert when you create new forms in Form Builder.
Until now, you
needed to install Active Component Framework (ACF) on the front-end PC to use
interactive forms. As of SAP NetWeaver 7.0 SPS10, ZCI enables you to use
interactive forms in Adobe Reader without any additional plug-ins. ACF is
therefore no longer required for interactive forms. You can use a report to
make any interactive forms created with an older version of SAP NetWeaver
ZCI-compliant. For more information, see Check and Update
Functions with the Report FP_CHK_REPORT.
UI Element InteractiveForm
For Adobe
integration, the InteractiveForm
interface element in category integration is provided in the Web Dynpro View
Designer.
Prerequisites
See Form Integration Prerequisites.
Connection Tests
For ZCI run report FP_CHK_REPORT.
For ACF 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 Error and Problem
Analysis and Adobe Document
Services Problem Analysis Scenarios. More information: SAP Note
999998.
Creating Web Dynpro Application Using Forms
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. Note that interfaces that are compatible with Smart Forms
are not supported in Web Dynpro ABAP. In principle, you can integrate a form
in each view in any component, though it is often better to create a separate
view to integrate it.
The individual steps involved in creating or using a form are described in the following:
Integrating PDF Forms in a Web Dynpro application.
You can find e-learning tutorials with code examples of integrating ACF forms in Web Dynpro applications in SDN. These tutorials were created using NW7.0 SPS6.
Restrictions
The integration of forms (and further active controls) into Web Dynpro ABAP popups is not supported.
For further limitations, see SAP Note 1098009.
Example
In the system in component WDR_TEST_ADOBEYou can find a complex test application for various scenarios that can arise when integrating forms using ZCI.
Notes
SAP Notes on SAP Service Marketplace
Number |
Short Text |
942506 |
Classification of forms by xACF and ZCI |
766191 |
Active Component Framework Installation |
999998 |
Error analysis for Web Dynpro ABAP Adobe integration |
846952 |
Removing ACF from Client PC |
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 type ZCI as of ERP 2005, SP 5 |
940637 |
OFFI: SetMerge Template for Adobe Template Designer |
944954 |
Pre-assigning interactive forms with script |
978037 |
Converting an ACF-based UI element to ZCI |