Online Tutorials & Training Materials | STechies.com
Register Login

Print or Display PDF Based Forms within Preview

|| || 0

Print or Display PDF Based Forms within Preview
Stechies

You want to activate or output a PDF form and receive an error message. You cannot print or display forms in the preview or generate or edit interactive forms, or these processes are defective.

It may occur becuase of:

Possible causes are that the configuration of Adobe document services is incorrect, there are errors in the form or the printer configuration is incorrect.

Solution:

For the printing or the print preview of PDF-based forms, you require a PCL-Postscript printer or a ZPL printer and you must use a relevant device type (for example, POST2, HPLJ4, HP9500, PDF1, AZPL203, AZPL300).

For more information, see 685571 and under "Printing PDF-Based Forms" in the SAP Print Handbook (BC-CCM-PRN). See SAP Help Portal under:

www.help.sap.com/saphelp_nw70/helpdata/de/25/6fa8fd27837846990a7a6813b06f80/frameset.htm

If you want to use a printer with the device type SAPWIN/SWIN, read 1444342.

To generate interactive forms, you require a credential, which you must register as described in the Adobe Configuration Guide.

Contents

In order to find the cause of the error, proceed as follows (depending on the scenario that you use): Note that you require administration authorization for some steps.

I ABAP:

1.  Test program FP_TEST_00
2.  Test program FP_PDF_TEST_00, RFC connection to ADS
3.  Testing the user and password
4.  Test destination service
5.  Interactive forms: Test program FP_TEST_IA_01 (credential test)
6.  Generated PDF with additional information
7.  Activating ADS trace on the J2EE Engine

II Web Dynpro for ABAP

1.  Test program FP_TEST_00
2.  Test program FP_PDF_TEST_00, RFC connection to ADS
3.  Testing the user and password
4.  Test destination service
5.  Interactive forms: Test program FP_TEST_IA_01 (credential test)
6.  Generated PDF with additional information
7.  Activating ADS trace on the J2EE Engine

II Web Dynpro for Java

1.  Testing the user and password
2.  Check whether the credential is installed and configured.
3.  Generated PDF with additional information
4.  Activating ADS trace on the J2EE Engine

I ABAP:

The following test steps are also described on SAP Help Portal in the chapter "Configuration Check for PDF-Based Forms in ABAP"
of the Adobe Document Services Configuration Guide:

SAP NetWeaver 7.0, 7.01, 7.02:

www.help.sap.com/saphelp_nw70/helpdata/en/43/f31e3082221595e10000000a1553f7/frameset.htm

SAP NetWeaver 7.1 and higher:

www.help.sap.com/saphelp_nw73/helpdata/en/4b/94e945ea576e82e10000000a421937/frameset.htm

1.  Use transaction SA38 to execute the program FP_TEST_00.

If the FP_TEST_00 form is displayed in the print preview, the ADS configuration is correct.

-> If you use scenarios with an interactive PDF, proceed with point 5. Otherwise, proceed with the test under point 6.

If the system displays an error message instead of a form, the configuration of ADS is incorrect.

 -> Carry out the additional tests from point 2 onwards.

2.  Use transaction SA38 to execute the program FP_PDF_TEST_00.

This enables you to check the RFC connection to ADS .

If the system displays the version number of ADS, the configuration of the RFC connection is correct.

-> Proceed to point 4.

You receive one of the following error messages:

2.1. If the system displays dialog fields for user and password instead of the version number, the entries for user and password in the RFC connection do not match the entries in user management.

-> Check the user and the password. Continue with point 3.

2.2. The system displays a "SYSTEM ERROR" with the following text:

"ERROR CODE:  100.101"

 "ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code"

or

 "ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP receive failed with exception communication_failure"

-> Contact your system administrator and ask them to check or correct the details for target device, service number and path prefix in the RFC connection (transaction SM59).

If all of these entries are correct and the problem still persists, you should check whether the J2EE Engine is started correctly. Read 1587941 also.

2.3. If the system displays an error message stating that there is no valid HTTP connection, then there is no RFC connection to ADS.

-> Contact your system administrator and ask them to correct or create the RFC connection (transaction SM59).

2. 4 The system does not respond.

 ->   Follow the instrcutions in s 783185 and 1587941.

3.  Check the user and password of ADS

Prerequisite: To perform this test, you must know the user and password for ADS. If you do not know this information, contact your system administrator and ask them to carry out the test.

Note the following: These instructions can be found in the documentation for the Adobe Configuration Guide in the chapter "Checking the User and Password".

For SAP NetWeaver 7.0, 7.01, 7.02 , proceed as follows:

                    1. In your Web browser, enter the following URL:

                    http://:/AdobeDocumentServices/Config

                    < server>: are the name and port of the J2EE Engine on which the Adobe Document Services run.

                    2. The Web page of the Web service Adobe Document Services is displayed. Choose "Test".

                    3. Choose rpdata(test..)

                    4. Choose "Send". No further parameter entries are required.

                    5. Enter "ADSUser" for the user and enter the relevant password.

                    6. Choose "Submit".

As of SAP NetWeaver 7. 1 and higher, the test occurs via the Web Service Navigator, which you call with http://:/wsnavigator. Caution: You require the user and password for the WS Navigator.

In Netweaver 7.10, you filter according to the service "com.adobe/AdobeDocumentServices_com.adobe_AdobeDocumentServicesVi" and execute the operation rpData similar to as described above.

As of NetWeaver 7.11 and higher, enter "Provider System" and "Local AS Java" as the search type to search for the service interface.

Choose "AdobeDocumentServicesVi" from the list of service interfaces. Choose "Continue" - no further parameter entries are required - until the system displays the dialog box for the user and password. Then enter "ADSUser" and the relevant password.

Result of the test for user and password:

If the system displays the version number of ADS, the configuration of the user and password is correct.

-> Proceed to the next point (4).

If the system does not display a version number (the page in the Web browser does not change, and submit continues to be displayed), the configuration of ADS is incorrect.

-> Contact your system administrator and ask them to correct the configuration for the user and password.

4.  Check the settings for the destination service 

To use the destination service on AS Java, settings are required on AS ABAP and AS Java. Therefore, this test contains several steps.

4. 1 In your ABAP system (transaction SA38), execute the following programs in succession:

                    1. FP_CHECK_DESTINATION_SERVICE

                    2. FP_CHECK_HTTP_DATA_TRANSFER (this program only if you bundle your forms).

                       a) First of all, execute the program without selecting the option "With Destination Service".

                       The system processes a test form in the background and displays the size of the generated PDF. It does not use the destination service in the process.

                       Caution: If the system issues an error message here, read 1587941.

                       b) Now select the option "With Destination Service" and execute the program again. The system processes the test form, using the destination service.

If the system displays the same message (file size of generated PDF) as it does in a), the configuration of the destination service is correct.
                    -> If you use scenarios with an interactive PDF, proceed with point 5. For print forms, proceed with point 6.

If the system issues an error message, the configuration of the destination service is incorrect.
                    -> If an error message is issued when you execute FP_CHECK_DESTINATION_SERVICE, execute the following tests 4.2 to 4.4.

                    -> If an error message is issued when you execute FP_CHECK_HTTP_DATA_TRANSFER, you require the ADS runtime information (trace files) for further troubleshooting. You can find out how to determine this runtime information under point 6. After you have made the settings, call the program again. The system saves the runtime information locally on your front-end PC.

                    Create a customer message under the component BC-SRV-FP, describe the problem, and attach the trace file with the runtime information to the message.


4. 2 Check whether the following ICF services are active (transaction SICF):

/default_host/sap/bc/fp
/default_host/sap/bc/fpads

If this service is not active, activate it. Note: You requre the ICF service fpads as of NW7.0 Support Package Stack 12 for bundling forms in distributed systems.

4. 3 Check the settings for the ICF service "fp".

a) Enter the following URL in your Web browser:

www.sap/bc/fp/form/layout/fp_test_00.xdp

< server> is the AS ABAP, is the HTTP port of the AS ABAP. (you can determine this information using transaction SICF).

b) In the dialog box for the user, enter ADS_AGENT and the relevant password.

If the ICF service settings are correct, the browser displays the layout information of the FP_TEST_00 form in XML format.

-> Proceed with point 4.4.

If the browser displays an error message instead of the aforementioned XML file, a configuration error occurred.

-> Check whether the user ADS_AGENT exists on the AS ABAP, and if the user has the required authorizations and roles (SAP_BC_FP_ICF or SAP_BC_FPADS_ICF).    

Note the following: Make sure that the relevant traffic lights for the status of the the profile comparison are green.

4.4. Check the settings for the destination service on AS Java (J2EE Engine)

a) Call Visual Administrator and navigate to Services -> Destinations

(You can also find detailed instructions in the Adobe Document Services Configuration Guide in the chapter "Creating or Changing the Destination Service",)

b) Extend the setting in field URLunder Connection Settings to:

http://:/sap/bc/fp/form/layout/fp_test_00.xdp

(The and that are already available refer to the AS ABAP.)

c) Choose 'Save and Test'

d) The system calls the ABAP system that stores the form templates.

If the settings are correct, the system issues the message: "HTTP GET response code 200 Content Type/xml."

 -> If you use scenarios with an interactive PDF, proceed with point 5. For print forms, proceed with point 6.

If the system issues an error message, the configuration of the destination service is incorrect.

-> Contact your system administrator and ask them to correct the settings for the destination service.

e) Do not forget to change the URL back to http://:.

5.  Check whether the credential is configured.

You must perform this step only if you use interactive scenarios. If you only use print scenarios, proceed with point 6.

Use transaction SA38 to execute the program FP_TEST_IA_01.

If the system displays the form, the ReaderRights credential is installed and configured.

-> Proceed with point 6.

If you receive an error message, for example,

ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)

-> Check whether you have installed and registered a credential. See Note 736902 and the Adobe Configuration Guide at:

 SAP NetWeaver 7.0

http://help.sap. com/saphelp_nw70/helpdata/en/56/f2c94a069f44a785b85748e11f82a0/frameset.htm

SAP NetWeaver 7.1 and higher

www.help.sap. com/saphelp_nwpi711/helpdata/en/56/f2c94a069f44a785b85748e11f82a0/frameset.htm

6.  Generated PDF with additional information

Call your form and save the generated PDF with additional information locally. You receive a PDF with attachments, which enable you to analyze the problem in detail.

Information about the PDF with additional information is available in the problem analysis guide (PAG) for SAP NetWeaver (TM) at:

http://help.sap.com/saphelp_nw70/helpdata/en/71/7ffb3f6c78ee28e10000000a1550b0/frameset.htm ->Usage Type Application Server Java -> Problem Analysis Scenario for Adobe Document Services -> Adobe Rendering Error

The following information about the procedure when setting this function can also be found in the documentation on SAP Interactive Forms by Adobe on the Help Portal under:

www.help.sap.com/saphelp_nw70/helpdata/de/f7/a04aee0cb94978a011401311efe603/frameset.htm (German)

www.help.sap.com/saphelp_nw70/helpdata/en/f7/a04aee0cb94978a011401311efe603/frameset.htm  (English)

You have the following options:

Setting using transaction SFP

                    1. Call the Form Builder (transaction SFP).

                    2. Choose "Utilities -> Settings".

                    3. In the dialog box, choose the option "Very Detailed Trace" for "Trace Level" under "Runtime Information".

                    4. Enter a file name under which the runtime information is to be saved locally as a trace file on your front-end PC. This file is useful for subsequent troubleshooting.

                    5. Set the indicator "PDF with Additional Information" and specify a file name if a PDF display or preview is not possible in your application. With this option, the generated PDF with additional information is then saved locally to your front-end PC.

Setting using user settings

You can also use the user settings to activate the function "PDF with Additional Information".  Proceed as follows:

                    1. Call transaction SU3 ('Maintain User Profile') or SU01 ('User Maintenance').

                    Note that you require the relevant authorization for the user maintenance of other users.

                    2. Choose the tab page 'Parameters', and enter the required parameters and values:

                    FPTRACELEVEL = 04
Setting the trace to the value required for the local saving of runtime information and for the generation of the PDF that contains additional information.

                    FPTRACEFILE =

File for the local saving of runtime information This specification is optional.

FPSAVEERRORPDF = X

The system generates a PDF that contains additional information.

FPERRORPDFFILE =

File for locally saving the PDF that contains additional information

Caution: Local saving is possible only for applications that have a GUI connection, and therefore, this is not supported for Web Dynpro ABAP.

3. These values then have a fixed assignment to the user.

You must reset these settings after troubleshooting is completed.

After you have made these settings, call your application for creating forms. The displayed PDF now contains the additional information that can be used for further troubleshooting. Save the displayed PDF.

Attach these files (PDF with attachment) to a message under the component BC-SRV-FP with a precise description of the problem.

If you cannot generate a PDF, save the trace files and attach them to your problem message as described above.

7. Activating ADS trace on the J2EE Engine 

If you cannot determine the cause of the problem with the aforementioned steps or cannot create a PDF with additional information, we recommend that you activate the ADS trace on the J2EE Engine. Reproduce the problem. All actions relating to the Adobe Document Services are then logged on the J2EE Engine.

Create a customer message under the component BC-SRV-FP with an exact description of the problem and attach the trace files to the message.

You can find out how to activate the ADS trace in 846610.

II Web Dynpro for ABAP

To analyze problems with interactive forms, which are integrated in Web Dynpro for ABAP, you will find detailed information in 999998.

To determine whether the ADS configuration is correct, execute steps 1 to 5 that are described under I ABAP:

1.  Test program FP_TEST_00
2.  Test program FP_PDF_TEST_00, RFC connection to ADS
3.  Test user and password
4.  Test destination service (only FP_CHECK_DESTINATION_SERVICE)
5.  Interactive forms: Test program FP_TEST_IA_01, credential test

6.  Generated PDF with additional information

Call your form in the Web Dynpro application and save the PDF with additional information that is generated by Adobe Reader. If the toolbar does not contain the save icon, use the F8 key to display it. You receive a PDF with attachments, which enable you to analyze the problem in detail.

Setting using user settings

You can only use the user settings to activate the function "PDF with Additional Information". Proceed as follows:

1. Logon to the corresponding ABAP system.

2. Call transaction SU3 ('Maintain User Profile') or SU01 ('User Maintenance').

Note that you require the relevant authorization for the user maintenance of other users.

3. Choose the 'Parameters' tab page and enter the required parameter and value:

FPTRACELEVEL = 04

Sets the trace to the necessary value for generating the PDF with additional information.

4. The assignment of the value to the user is now fixed.

 5. Exit the Web Dynpro application and logon again so that the user parameter configured previously takes affect.

Reset these values after troubleshooting is completed.

> Attach these files (PDF with attachment) to a message with the component BC-SRV-FP, including a precise description of the problem.

7. Activating ADS trace on the J2EE Engine 

See descrption under I ABAP and 846610.

II Web Dynpro for Java

1.  Check the user and password of ADS

The procedure is the same as in chapter I ABAP "3.  Test user and password".

This information can also be found in the Adobe Document Services Configuration Guide in the Help Portal under:

http://help.sap. com/saphelp_nw70/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm -> Adobe Document Services Configuration Guide -> Configuring the Web Service -> Securing Access to the Web Service ->Configuration Check -> Configuration Check for Interactive Forms in Web Dynpro for Java          

2.  Check whether the credential is configured.

              Check whether you have installed and registered a credential. See Note 736902 and the Adobe Configuration Guide at:

              SAP NetWeaver 7.0

              http://help.sap. com/saphelp_nw70/helpdata/en/56/f2c94a069f44a785b85748e11f82a0/frameset.htm

              SAP NetWeaver 7.1 and higher

              http://help.sap. com/saphelp_nwpi711/helpdata/en/56/f2c94a069f44a785b85748e11f82a0/frameset.htm           

3. Generated PDF with additional information

As of SAP NetWeaver 7. 0 Support Package 06, you can generate a PDF with attachments that enable detailed troubleshooting. The procedure depends on the Support Package level of SAP NetWeaver 7.0.

              SAP NetWeaver 7. 0 Support Package 06/07/08

  • Extend your application URL with the "sap-wd-adsTrace=4" addition.
               Note that there will then only be a display if the system can create a PDF. If this is not the case, follow the instructions that are contained in Notes 742674 and 846712.
    SAP NetWeaver 7. 0 Support Package 09 and higher 
  • Set the Trace Level for Web Dynpro to 'ALL'. You can find detailed information about setting the Trace Level in Note 742674.
     
  • Call your form and save the generated PDF with additional information locally. This PDF with attachments is required later for detailed error analysis. Attach these files to a message with the component BC-WD-JAV, including a precise description of the problem.
     
  • Reset the Web Dynpro Trace level.
    SAP NetWeaver '04 
  • In these versions, the system does not display any PDFs with additional information, however, the trace files contain the notes that you require regarding the cause of the problem. Set the Trace Level for Web Dynpro to 'ALL'. You can find detailed information about setting the Trace Level in Note 742674.
     
  • Call your form and save the trace files locally. These are required later for detailed error analysis. Attach these trace files to a message with the component BC-WD-JAV, including a precise description of the problem.
     
  • Reset the Web Dynpro Trace level.
                  Information about the PDF with additional information is available in the SAP NetWeaver Problem Analysis Guide (PAG) at:
                        http://help.sap.com/saphelp_nw70/helpdata/en/71/7ffb3f6c78ee28e10000000a1550b0/frameset.htm ->Usage Type Application Server Java -> Problem Analysis Scenario for Adobe Document Services -> Adobe Rendering Error            

4. Activating ADS trace on the J2EE Engine

See descrption under I ABAP and 846610.


Related Articles