Skip to Content

FAQ: Error Log

Q1: What are the transaction names for the SAP NetWeaver Error Log?
In an SAP NetWeaver Gateway hub system, the transaction name is /IWFND/ERROR_LOG and in an SAP Business Suite backend system the transaction name is /IWBEP/ERROR_LOG.

Q2: Which errors are stored in the Error Log?
Once the SAP NetWeaver Gateway framework is called to process an OData request, any termination with an error is logged in the Error Log in an SAP NetWeaver Gateway hub system. If an error happens in an SAP Business Suite backend system, it is also logged in the Error Log of the backend system. This error situation is shown as an ‘X’ in the column Backend Error in the Error Log in an SAP NetWeaver Gateway hub system.

Contrary to this, if an error happens before the SAP NetWeaver Gateway framework is called (for example, invalid login, wrong HTTP/HTTPS configuration) no entry is written in the Error Log.

Q3: How can I determine and display the source code which raised the exception?
Mark the entry in the Error Log and click Active Source in the Overview screen area to see the corresponding source code.

Click Call Stack in the Error Context screen area to see the call stack.

Q4: Why does the call stack not always fit to the source code of an exception?
This happens because an exception was raised, but the Error Log was called later for creating an Error Log entry.


Q5: Why is some information shown as “***Hide_due_to_secure_log_level***”?
The Error Log has two different levels: Secure and Full. Due to SAP security policy, the Error Log is delivered with level Secure as default. Using the secure level, all sensitive data such as service name or the whole payload is hidden and the text ***Hide_due_to_secure_log_level*** is displayed.

Q6: How can I change the log level?
First, click the icon “I” in transaction /IWFND/ERROR_LOG to see more details about “Log Level and Authority for Error Log”. To change the log level, choose Menu->Error Log->Global Configuration. Here you can also change the duration that error log entries are stored (default: 14 days) and activate or deactivate the entry aggregation by service, user, and error.

Q7: How can I display the request data which leads to a termination with error?
Double-click the affected entry in the Error Log to display the Error Context screen area. Click Request Data in this screen area. A popup is displayed with the complete HTTP headers and the body of the OData request.

Do the same for Response Data.

Q8: When and how can I use the features Download to PC and Upload from PC?
If you want to send the information about one or more entries in the Error Log to your colleagues or to SAP Support, you have to mark these entries and click Download to PC and send the file attachment for a mail or attach to a reported incident. The request and response data will also be stored in this file.

Depending on the original entry (created in the hub or backend system), your colleagues or SAP Support can run the Error Log in an SAP NetWeaver Gateway hub system or in an SAP Business Suite backend system to display the entry. Some features of the Error Log such as Active Source or Replay might not work properly because of different Support Package levels.

CAUTIONS:
The downloaded file uses an XML-like format and can only be used by the Error Log transactions. You can also use an internet browser or an XML editor to display the file content but in case of erroneous $batch requests you might see incomplete payload data. Use a text editor instead.

Q9: How can I re-test an error request without using the OData consumer?
Click Replay on the Error Context screen. In case of an HTTP GET, you can choose the Gateway Client or the default Internet Browser on your PC to replay the error request. In case of modifying operations (POST, PUT, PATCH, MERGE or DELETE) you can only perform a replay in the Gateway Client.

Here you can also save the whole request as a test case for the Gateway Client.

Q10: How can I display the service configuration?
On the Error Context screen click the configuration and choose Maintain Service.

Q11: How can I display the service source codes (Model and Data Provider class)?
On the Error Context screen click the configuration and choose Service Implementation.

Q12: How can I display the SAP Note displayed in the Error Log?
As of SAP NetWeaver Gateway 2.0 Support Package SP08 and higher, a data provider can define an SAP Note explaining the error situation and provide some recommendations to terminate the request processing with an exception. The SAP Note number is also returned to the OData consumer together with other error information. The Error Log is extended to save and display this information. Double-click on LINK_TO_SAP_NOTE to start your default internet browser and display the SAP Note.

Former Member

No comments