Show TOC

Notification MonitorLocate this document in the navigation structure


The Notification Monitor for SAP Gateway provides an overview of all notifications to be sent using a background Remote Function Call (bgRFC) from an application in the SAP Business Suite backend system to the SAP Gateway framework. It is available for the OData Push Channel. The Notification Monitor facilitates asynchronous processing specifically for SAP Gateway applications and lists all notifications created by an application, before these are actually sent by an outbound bgRFC to the SAP Gateway framework. This has the advantage that you can check the status of the notifications before they are actually sent by bgRFC. This asynchronous processing saves you time and effort.

You can start the Notification Monitor from an SAP Business Suite backend system (transaction /IWBEP/NOTIF_MONITOR) or from your SAP Gateway hub system (transaction /IWFND/NOTIF_MONITOR).

Notification Queue Overview

For ease of use, the notification queues displayed in the Notification Monitor are organized according to the last or newest notification meaning that the most recent notification is always displayed at the top of the list of queues.

The Notification Monitor provides you with an overview of the following data for each notification queue:

  • Line in monitor

  • Queue status

    • Communication error (comm_error)

    • XML conversion error (conv_error)

    • Execution error (exec_error)

    • Executing (executing)

    • Internal bgRFC error (int_error)

    • Queue manually locked (locked)

    • Ready for processing (ready)

    • Retry due to communication error (retry)

    • Wait for update task (upd_wait)


    If the queue status remains ready for more than a couple of minutes, this indicates that the bgRFC scheduler is either not working correctly or is still trying to obtain system resources to process the queue. For more information, see the SAP Gateway Configuration Guide) and run transaction SBGRFCCONF to check the current bgRFC settings. You can also check the system logs in transaction SM21 and analyze runtime errors in transaction ST22.

  • Last notification (date and time)

  • First notification (date and time)

  • Last delivery attempt

    This information is only displayed after a failed attempt has been made to send the notification.

  • Destination (consumer) to which notification is to be pushed

  • Queue name

    For more information, click the queue name to launch the overall Monitor for bgRFC Units.

  • Error text

    The error text displayed originates from the Monitor for bgRFC Units. Consequently, if a notification has not yet been sent by an outbound RFC, no error text is displayed. For example, if the queue status remains ready because a technical issue is preventing the notification from being sent, no error text is displayed in the Notification Monitor.

Resolving Errors in the Error Log

If a notification queue has been processed with an error, that is a notification could not be sent by the application to the SAP Gateway framework, you can launch the SAP Gateway Error Log to examine the exact cause of the technical error and then solve the issue.

Since the Notification Monitor is integrated with the SAP Gateway Error Log, you can navigate directly from the Notification Monitor to the Error Log. To navigate to the Error Log, choose the Error Log pushbutton.

After an error has occurred during the processing of the notification queue and you have made any relevant technical modifications, attempts can be made to re-send the notification to the consumer in the SAP Gateway framework using an inbound RFC.

More Information

For more information, see Error Log.