Troubleshooting

This section provides additional troubleshooting options.

Check whether notification scenario is activated

If you cannot find any queue entries, run transaction CLB2_PLATF to check whether the Send Notifications option is activated for the relevant target platform. If the option is set, but a service is processed with a queue entry, check the notification filter settings in view CLBV_GW_NOTIFY_C.

Check all Customizing settings

Double-check all of your Customizing settings. In most cases, the problem is due to a missing Customizing step in the configuration of SAP Gateway or ABAP SMI, or the connectivity between the back-end system and the SAP Gateway server.

Activate trace

If the steps mentioned above do not provide the information you need, run transaction SAAB to activate a trace level. Choose checkpoint CLB2_LOG and activate the log option. We recommend activating the trace globally, or for the bgRFC user, rather than for the current user, as the notifications are sent asynchronously under another user.

The trace is written to the application log and can be checked subsequently in transaction SLG1.

Besides the error messages, you can also find success messages throughout the call stack. This allows you to see how far the send process has been executed. It is recommended to dump such a log before opening a ticket for SAP component CA-UI2-AR-SM, and to attach the trace to the ticket.

OAuth2 Troubleshooting

If you encounter issues after setting up the per-user authentication between SAP Jam and SAP Gateway, you can first try the connection with a common user authentication. If the common user works, but the per-user authentication does not, there is an issue with the OAuth2 flow. In this case, see SAP Note 1688545 .

You can also use the tracing capabilities of your SAP Gateway server, or consult the troubleshooting information available for SAP Gateway (for example, SAP Note 1797736 ) and any further information available for troubleshooting SAP Gateway services on SAP Community Network (SCN).

The most important trace and log tools are the following: