Skip to end of metadata
Go to start of metadata

Purpose

If an error occurs, the Gateway Error Logs should be checked first. There two transaction to check the Gateway related errors: 

 

Error Log - /IWFND/ERROR_LOG

/IWFND/ERROR_LOG is the transaction for checking errors which occur while OData services are called with OData requests.

To reach the Frontend Errors, use transaction code /IWFND/ERROR_LOG or you can reach it from transaction /IWFND/GW_CLIENT by using the dedicated Error Log button.


The errors appear in the following form:

The Error Text field is the most important, you can see a short error description here.

For further information, click one of the following buttons:

    • Active Source – The Active Source button enables you to navigate directly to the source code where the error occurred and the exception rose. It is useful
      • because you can check if the error rose in your source code or if it was implemented by someone else
      • because you can set a breakpoint to retrace the error
    • Donwload to PC – If you are not able to solve the problem by yourself, you can download the error description by choosing the Download to PC button.
      • You can then create a customer message for SAP and attach the error description. The attachment provides support colleagues with important context information they require to solve the problem.

        The error description in a customer incident is much more helpful than a screenshot of the error log entry.

    • Upload from PC – you can upload the error description to another system in order to check it there
    • Error Context – For further information, select the line with the error you are interested in. The error context provides detailed information about the error that occurred:
      • Error_Info: shows a description of the error
      • Namespace: shows the namespace in which the error occurred. It is important to ascertain whether the error occurred in the SAP Business Suite backend system or in the SAP Gateway hub system.
      • System_Alias: shows the system and client in which the error occurred
      • Request_URI: shows the affected request. It is important to reproduce the error and understand the cause

    • Configuration – this button helps you overcome service-related problems. Two different errors are possible:
      • Service not implemented – If the service has not yet been implemented, you have to choose the Service Implementation option when you press the Configuration button. You will be redirected to the according transaction in the SAP Business Suite backend system.
      • Service erroneous – If the service has already been implemented, but contains an error or it is not active, you have to choose the Maintain Service option when you press the Configuration button.
    • Application Log – If the Error Log does not contain the information you need to solve the error, you can access the Application Log. It is required in rare cases.
      • The Application Log shows you the steps processed when the request was executed. Each line represents one step of the request execution. Additionally, you can see a traffic light in front of every line to see where the error occurred.
        • Lines with green lights  àhave been executed successful
        • Lines with yellow lights à indicate a problem
        • Lines with red lights à mark erroneous execution steps
    • Replay – After finding a solution to the problem, you can check the solution by clicking Replay and choosing the option Gateway Client in order to check the solution.
      • Gateway Client starts automatically where the error context is reproduced and preset.
      • The HTTP method, request URI, and headers are filled in the Gateway Client.

Backend Error Log

If the error occurred in the SAP Business Suite backend system, the Error Log in the backend system should be checked too. To access it, transaction code /IWBEP/ERROR_LOG  can be used or it can be reached from Gateway Error Log by choosing Backend Monitor button.

To reach the Backend Errors, use transaction code /IWBEP/ERROR_LOG in the backend system or you can reach it from transaction /IWFND/ERROR_LOG by using the dedicated Backend Monitor button. It will redirect you to the backend system. 

The checkbox in the "Backend Error" column indicates that whether errors occur in the backend or not.

The Error Log in the backend system looks just like the Error Log in the SAP NetWeaver Gateway hub system, but it includes some additional information in the Error Context.

Similar buttons can be found here as in the frontend Error Log to get further information about the error:

    • Error Context
    • Active Source
    • Download to PC / Upload from PC
    • Service Implementation

Check the Component column as it gives the responsible support component of the error. The backend errors might have different support component than the frontend errors. The reason behind this behavior is pretty simple: the frontend displays errors which occur in the console but the exception encountered in the backend.

If you need to send a customer incident to SAP in order to solve the occurred error, please open it in the responsible component of the backend error because it will be solved most probably at that component and you can speed up the resolution process in this way.

More Information

Error Log

  • No labels