The Error Log for SAP Gateway is a helpful addition to the existing Application Log Viewer. It provides detailed context information about errors that have occurred at runtime.
Developers, administrators, support consultants, and end users can launch the Error Log in transaction /IWFND/ERROR_LOG for hub systems and /IWBEP/ERROR_LOG in backend systems to obtain important context information about the time and location of errors. The Error Log facilitates easy navigation to the affected source code where you can make the necessary corrections.
The Error Log enables you to:
Identify precise time and location of errors in source code.
Determine how often an error has occurred.
Perform root-cause analyses.
Reproduce and correct errors.
The Error Log comprises two screen areas:
The Overview screen area lists all error IDs and their attributes, together with the date and time at which the particular errors occurred. As default, errors are displayed chronologically with the newest error at the top of the list. You can display the error information and descriptive error texts to obtain more detailed information about a particular error and also see how often and where it has occurred. You can determine the Line and Entry Number of an error in the Error Log and also ascertain the number of occurrences in the Error Count column. The error counter is helpful to reduce the amount of data stored in the Error Log as it counts the number of times an identical error (according to standard parameters including User Name, Service Name, Message Class, and Message Number) has occurred within one full hour.
As default, the Overview screen area lists all errors that have occurred on the current date for all users, but you can change the standard setting to suit your requirements. To display errors according to different criteria, choose the Re-Select icon and on the Select Error Log Entries subscreen, select the Free search radio button. The free-search options enable you to search for errors that occurred on a different date and specify the exact time range, for example.
To help you further refine your search, you can display errors according to the following criteria:
T100 Message ID
T100 Message Number
Component: can be cross-referenced if you need to create a customer message
Request URI Part
Request ID: identifier sent from consumer to SAP Gateway
If you do not want to use the free-search criteria, you can select one of the following alternative search options:
Operation ID: identifier within the Error Log
Transaction ID: identifies one transaction and is transferred to all affected SAP systems during processing.
If you select an error on the Overview screen area and then choose the Re-Select icon, the attributes of this particular error are entered automatically in the Select Error Log Entries subscreen. You can select an entire line or parts of the error information.
To enable you to identify where an error has occurred, the component, package, service name, root context ID, transaction ID, and request ID are listed in separate columns in the Overview screen area. You can sort the errors in the table according to various criteria, for example, the time or location they occurred.
If required, you can use the standard SAP Export function in the SAP List Viewer (ALV) to download the errors displayed in the Overview screen area, however the Error Log provides further options for facilitating error analysis.
The Overview screen area provides you with the following functions, which you can execute by choosing the relevant pushbuttons:
Display complete overview of context in which error occurred including technical attributes such as service name, request URI, backend system alias, and RFC destination. This context information is displayed in the Error Context screen area.
To display the context information in the Error Context screen area, you can select an error and then choose the Error Context pushbutton or double-click the error information in the Overview screen area.
Navigate to the source code in which the error has occurred and analyze the cause of the error.
Download to PC
Download the error log in XML format to your local PC. You might want to download the error log to analyze the errors offline at a later time or to forward the log as an attachment to administrators or Active Global Support. If required, you can select multiple errors in the table and download all the relevant error log information in one XML log file.
Upload from PC
Upload error information contained in an XML file to enable easier error analysis. To upload an error log file from your PC, choose Upload from PC, browse to the relevant XML file, and choose Open. The error log information contained in the XML file is displayed in the Overview screen area of the Error Log.
Display a summary of all errors displayed in the list for each component and package together with the date and time of the first and last occurrence.
To display detailed context information about an error, double-click the relevant error item in the Overview screen area, or select the error item and choose the Error Context pushbutton. The relevant context information about the error item is displayed in the Error Context screen area where you can expand or collapse this information depending on the level of detail you require. The information displayed is organized according to Name and Value.
The Error Context screen area includes the following functions, which you can execute by choosing the relevant pushbuttons:
Display error in context in XML format. It is advantageous to display the error in XML so that all text strings are displayed in their entirety and in context. The texts displayed in the Error Context screen area are limited to 100 characters.
Display call stack up to the source code line in which the error occurred. You can select the error event to navigate to and check the relevant line of source code.
Navigate to the corresponding entry in the Application Log. You can also launch the Application Log in transaction /IWFND/APPS_LOG. Expand the tree to navigate to the error.
Display request XML that was sent from external consumer. It contains the HTTP request headers and payload.
Display response XML sent from SAP Gateway. It displayed the HTTP response headers and payload.
Access the Error Log (as of SAP Gateway 2.0 Support Package 5) or the Application Log Viewer (for lower releases) in the SAP Business Suite backend system. Alternatively, launch the ABAP Runtime Error application (transaction ST22) in the SAP Business Suite backend system if a short dump occurred during processing.
Choose from the following two replay options allowing you to reproduce and correct errors:
Choose from the following service maintenance options:
Maintain Service to activate and maintain services in the SAP Gateway hub system.
Service Implementation to navigate to the SAP Business Suite backend system and maintain the service there. In the SAP Business Suite backend system, you can navigate directly to the model provider class or data provider class for the given service.
For more information about how to configure the Error Log, see Configuration Settings for the Error Log.