Register Login
Python Photoshop SAP Java PHP Android C++ Hadoop Oracle Interview Questions Articles Other

Error in WD ABAP ALV if choose 'Print Version'

Updated May 18, 2018

Technical information:

In a WD ABAP ALV, if you choose "Print Version", the following behavior occurs:

  • the system uses the RFC connection SALV_WD_EXPORT_PDF to call a portal service
  • the portal service uses Adobe Document Services to generate a PDF document
  • the system uses RFC to return the PDF document to the WD ABAP ALV and displays the document


Technical prerequisites:

If you want to create a print version in WD ABAP ALV, you must meet the following prerequisites.

1. Installation
 

  • The Web Application Server ABAP has at least the following Support Package level: SAP_BASIS 7.00 Support Package 8.
     
  • The usage type BI Java, for which the usage type AS Java and EP is a prerequisite, has to be installed on a Java Web Application Server. This provides the service that is called when you print from WD ABAP ALV.

    In this case, you only have to perform an installation. You do not have to configure the portal or BI to be able to create the print version.

    The BI Java usage type must have at least Support Package level 7.00 Support Package 14.
     
  • Adobe Document Services (ADS) must be completely installed and configured. ADS is part of the usage type AS Java. The release level must be at least 7.00 Support Package Stack 14.

              There are three components:

              A: Application Server ABAP on which your WD ABAP ALV application runs

              B: Application Server Java on which the usage type BI Java is installed and the portal service for printing is provided.

              C : Application Server Java on which your ADS server runs

2. Customizing:
 

  • Transaction SPRO
     
  • Branch to the following entry:
    -> Application Server
    ->  Web dynpro for ABAP
    -> Set-up Printing for Web Dynpro ABAP ALV
     
  • You must proceed as follows:

    Create RFC Destination in SAP NetWeaver Portal

    Create RFC Destination to SAP NetWeaver Portal

    Set-Up Web Service Destination for Adobe Document Services


3. Troubleshooting:

If you have checked your installation and configuration, but an error occurs when you create the print version, this may be caused by the following reasons.

3.1 Communication failure:

The error message that the system issues in the browser window starts with:
"Print Version Communication Failure"

Possible reasons for a communication failure:

  • The Web Application Server Java on which the usage type BI Java is installed and the portal service for printing is provided has not been started.
     
  • The RFC destination in the JCO provider of the Web Application Server Java has not been created.
     
  • The RFC destination SALV_WD_EXPORT_PDF does not exist in the application server.
     
  • The system issues the following error message: "Communication Failure: RFC Destination SALV_WD_EXPORT_PDF does not exist"
     
  • The settings in transaction SM59 on the application server do not correspond to the settings of the RFC destination in the JCO provider of the J2EE Engine.

Solution:

  • Check the following two activities in Customizing:
     
  • Application Server
    ->  Web dynpro for ABAP
    -> Set-up Printing for Web Dynpro ABAP ALV
    -> Create RFC Destination in SAP NetWeaver Portal
     
  • Application Server
    ->  Web dynpro for ABAP
    -> Set-up Printing for Web Dynpro ABAP ALV
    -> Create RFC Destination to SAP NetWeaver Portal
     
  • Perform the connection test of your RFC destination SALV_WD_EXPORT_PDF.
     
  • In transaction SM59, check the RFC destination
    SALV_WD_EXPORT_PDF.
     
  • Perform the connection test of your RFC destination SALV_WD_EXPORT_PDF.
     
  • Also check whether the connection was created to the correct system:
    Choose the following menu path: "Extras -> System Information -> Target System" and check the "System ID" field.

3.2. System Failure:

The error message that the system issues in the browser window starts with:

"Print Version System Failure"

Possible reasons for a system failure:

  • You use Adobe document services to create a PDF document but these services are not available or are configured incorrectly:

    Check the following activity in Customizing:
    Application Server
    ->  Web dynpro for ABAP
    -> Set-up Printing for Web Dynpro ABAP ALV
    -> Set-Up Web Service Destination for Adobe Document Services

    See the "Web Dynpro for Java" paragraph in Note 944221 to check the user and password.
     
  • Print Version System Failure: Bean SALV_WD_EXPORT_PDF not found on host xxx.

    Usage type BI-Java is not installed (completely): Check whether the usage type BI Java was installed on the application server for Java.

    Note 883948 contains information about which components belong to the usage type BI-Java. You must install all components from BI-Java.
    If SOME of these entries DO NOT EXIST, the usage type BI Java is not completely installed.

    Your RFC destination SALV_WD_EXPORT_PDF that you defined in the Application Server ABAP in transaction SM59 does not point to the correct Application Server Java. In transaction SM59, check the RFC destination
    SALV_WD_EXPORT_PDF. Choose the following menu path: "Extras -> System Information -> Target System" and check the "System ID" field.
     
  • System Failure: Server repository could not create function template

    The problem is a missing S_RFC authorization of the user that was defined in the JCO RFC provider.

    Check the following activity in Customizing:
    Application Server
    ->  Web dynpro for ABAP
    -> Set-up Printing for Web Dynpro ABAP ALV
    -> Create RFC Destination in SAP NetWeaver Portal
     
  • If the error continues to occur when the system creates the print version, perform the steps described in point 4 "SAP Support".

3. Source code error:

  • You cannot create the print version because the internal program contains errors. To simplify the error analysis, you can generate an XML file and send as part of a customer message to SAP Support.
     
  • Procedure:

    Log on to the R/3 System with your user.

    SAP menu -> System -> User Profile -> Own Data

    On the 'Parameters' tab page, define the following SAP parameter:
  •  
  • Parameter ID = SALV_WD_PDF                                   
  • Parameter value = XML

    Save the user profile.

    Now start the Web Dynpro ALV application with your user.

    Choose the toolbar button for the print version.
    => The system displays an XML in a separate browser windowUse menu path -> File -> Save as to save this XML as an XML file, and attach this XML file to the customer message

    Then delete the parameter SALV_WD_PDF in your R/3 System.
     
  • In addition, perform the steps described in point 4 "SAP Support".


4. SAP Support:

To simplify the error analysis, refer to Note 937697 and download the latest version of the SupportDesk application.

  • Pushbutton "Start reproducing error"
  • Attempt to create a print version
  • Pushbutton "Stop reproducing error"
  • Pushbutton "Download support info"
  • Attach the generated ZIP file SupportDesk.zip to the customer message.


Note: The SupportDesk tool must run on the server on which the usage type BI-Java is installed and to which the RFC destination SALV_WD_EXPORT_PDF refers.

Ignore any red traffic lights that the SupportDesk tool may display.

 

Recommended Posts:
×