SAP Basis Tech Supports

Symptom

When you analyze errors concerning the Adobe integration of Web Dynpro ABAP, you cannot determine the cause for the problems.

Other terms

Web Dynpro ABAP, InteractiveForm, Adobe

Reason and Prerequisites

N/A

Solution
Symptom:

The Web Dynpro application terminates with an error message (”WebDynpro Exception: The ADS call has failed…” or similar).
Reason:

The Adobe document services (ADS) have not been installed or configured correctly.
Solution:

If the Adobe Interactive Forms have been installed correctly, the following tests should run without errors:
First test:
1. Call transaction SE38.2. Enter the report name “FP_PDF_TEST_00″ and choose “Execute” (or press F8).3. Enter “ADS” in the entry field for the connection, and choose “Execute” (or press F8).4. The system should display a dialog box containing the current version information.
Second test:
1. Call transaction SE38.2. Enter the report name “FP_TEST_00″ and choose “Execute” (or press F8).3. Enter “FP_TEST_00″ for the form, “2″ for the number of print pages, and “ADS” for the ADS connection. The choose “Execute”.4. Enter a valid output device and choose “Print Preview”.5. The Adobe Reader should be displayed in the GUI and should display two pages with numbered lines.
Third test:
1. Call transaction SE38.2. Enter the report name “FP_TEST_IA_01″ and choose “Execute” (or press F8).3. Enter “FP_TEST_IA_01″ for the form, “ADS” for the ADS connection, and any data in the other entry fields (these are already filled with default values). Then choose “Execute” (or press F8).4. Enter a valid output device and choose “Print Preview”.5. The Adobe Reader should be displayed in the GUI and should display a page with address fields.6. Scroll down to the frame for the new address and fill in those fields. At the end of the form, an entry field for the date and a value help exists. Choose the input help button and check if the system displays the datepicker.

If one of these tests does not work correctly, the problems may be caused by the general Adobe connection to Web Dynpro ABAP.
Check the installation or configuration of the Adobe document services (ADS). Forward the original CSN message to the component BC-SRV-FP.

Symptom:

The Web Dynpro application hangs during submit if an interactive form is displayed. In particular, this symptom occurs after you import a Support Package or implement notes referring to the integration of SAP Interactive Forms by Adobe in Web Dynpro ABAP.
Reason:

For ZCI-based forms, the “ZCI script” is not available in the form or is obsolete and must be updated.
Solution:

SAP NetWeaver Release 7.00: See Notes 1229392 and 1343908 and update the form using transaction SFP_ZCI_UPDATE. This also affects many forms delivered by SAP.
SAP NetWeaver Release 7.01 and higher: As of this release, the Adobe document services provide the option of automatically copying the ZCI script to the form. However, if you use the Adobe document services from SAP NetWeaver Release 7.00 (Java stack) with SAP NetWeaver Release 7.01 (ABAP stack), this function is not yet available. In this case, you must manually insert the script in the form using transaction SFP_ZCI_UPDATE.

Symptom:

The content of dropdown boxes is lost after a server roundtrip.

Reason:

This is caused by an error in the integration of SAP Interactive Forms by Adobe in Web Dynpro ABAP.

Solution:

Implement Note 1354405.

Symptom:

Web Dynpro ABAP applications with interactive forms do not work in Firefox 3.x.

Reason:

The Support Package is too old. SAP Interactive Forms by Adobe are supported for Firefox as of SAP NetWeaver 7.00 Support Package 19.

Solution:

Import Support Package 19. Also implement Note 1322323.

Symptom:

Web Dynpro applications with interactive forms are slow.

Reason:

There are various reasons for this. In particular, the solution becomes more complex due to the integration of Adobe Reader and the Adobe document services (ADS) in the Web Dynpro ABAP framework.
The user interface (UI) element property “pdfSource” of the InteractiveForm UI element is bound. In this case, the Web Dynpro ABAP framework has to request an updated PDF document from the Adobe document services each time data is changed in the form.

Solution:
Only the data that is displayed in the interactive form is to be bound to the Web Dynpro context.The property “pdfSource” should be bound only if the Web Dynpro ABAP application requires the PDF document for further processing (saving data to the database, and so on). However, it is mostly only the data entered in the interactive form that is relevant for the application.

Symptom:

Further symptoms that are not specified here occur.

Solution:
Delete the browser cache.The problem may already be known and may have been solved. Carry out a notes search using the search term “InteractiveForm” or “interactiveForm” for the component “BC-WD-ABA*”.Upgrade the Adobe Reader to the latest version.A browser trace function is available as of SAP NetWeaver Release 7.00 Support Package 18 and for all Enhancement Packages. Activate this trace using the URL parameter “sap-wd-clientDebug=X” (attach it to the URL using “&”). You can activate the trace with the key combination T (move the focus to a Web Dynpro UI element, for example, to an InputField, do NOT move the focus to Adobe Reader). A new browser window with the trace is displayed. An error entry may be contained in the trace (”Network Error”, and so on).

If you still cannot solve the problem, forward the CSN message to the component BC-WD-ABA.
You must add the following to the message:
Version of the Adobe document services (which you can determine using the report FP_PDF_TEST_00)SAP NetWeaver release information (SAP_BASIS): Release and Support Package levelIf the browser trace function is already available: Add the trace of the Web Dynpro application and a copy of the PDF document (”Save” button in the toolbar of Adobe Reader).