Which Tools Can Be Used for Troubleshooting?
Errors might occur while operating and administrating the SAP Gateway components. A variety of tools are available to help you analyze the cause of the problem and debug such errors.
Error Log
Use this tool to analyze errors that have occurred and led to a termination of an OData request or notification processing (push channel).
SAP Gateway hub system: transaction /IWFND/ERROR_LOG.
SAP Business Suite backend system: transaction /IWBEP/ERROR_LOG.
For more information, see Error Log.
In addition, you can use the Application Log Viewer to check more technical error details.
SAP Gateway hub system: transaction /IWFND_APPS_LOG.
SAP Business Suite backend system: transaction /IWBEP/VIEW_LOG.
For more information, see Application Log Viewer.
Performance Trace
Use this tool to analyze performance problems relating to OData request processing.
SAP Gateway hub system: transaction /IWFND/TRACES.
For more information, see Performance Trace.
Payload Trace
Use this tool to monitor the flow of data sent as part of service requests and responses. It also provides a replay function allowing you to trigger service calls again if unexpected data was initially returned.
SAP Gateway hub system: transaction /IWFND/TRACES.
For more information, see Payload Trace.
SAP Gateway Client
Use this tool to test your OData service provider without an OData consumer application.
SAP Gateway hub system: transaction /IWFND/GW_CLIENT.
For more information, see SAP Gateway Client.
Notification Monitor
Use this tool to check and analyze notification processing (push channel) in the SAP Business Suite backend system or SAP Gateway hub system.
SAP Gateway hub system: transaction /IWFND/NOTIF_MONITOR.
SAP Business Suite backend system: transaction /IWBEP/NOTIF_MONITOR.
For more information, see Notification Monitor.
You can use the following standard ABAP troubleshooting tools for SAP Gateway:
Analyze Application Log: transaction SLG1
CCMS Monitor Sets: transaction RZ20
ABAP Runtime Error: transaction ST22
System Trace: transaction ST01
You can also use SAP Solution Manager diagnostics to perform an end-2-end trace. For more information, see SAP Note 1435190 
(SAP client plug-in) and SAP Note 1041556 (SAP HTTP Plug-In for IE). This is an instrument browser with a plug-in as described in SAP Note 1435190 and it calls SAP Gateway services from a browser. The SAP Solution Manager diagnostics pull standard traces from SAP Gateway.
Before you create a customer service ticket, check the following:
Ensure OData compliance:
Validate test URL against OData specification http://www.odata.org/developers/protocols/overview
Test URL by checking a corresponding URL against the OData reference service http://services.odata.org/OData/OData.svc/
Exclude side-effects caused by metadata cache: see Metadata Cache.
If you are unable to solve the problem yourself using the standard ABAP tools or the supportability tools for SAP Gateway, create a customer service ticket on an SAP Gateway component. For more information about how to create a customer service ticket and to ensure that you include all the relevant context information, see SAP Note 1579681 .