Show TOC

Monitoring bgRFC QueuesLocate this document in the navigation structure


You can monitor and display items in the Background Remote Function Call (bgRFC) queue to check for messages which the system failed to send.

All the messages are written in unit queues, which consist of function modules to be processed as an indivisible unit. Find all the messages that failed to be transported from the host of the backend or OData Channel to the consumer environment, because of system fault exceptions.

System faults are all standard REST errors, for example: communication error, or other errors that occurred during the activation and operations of Web services.


Application fault exceptions are displayed in the application itself.


Make sure that you have the authorization object S_BGRFC for monitoring or customizing activities assigned to your user role.

Analyzing the Results of the Monitor

You analyze each error message and decide how best to correct the error.

If the error can be fixed, make the necessary corrections and then send it to the unit again, otherwise delete the unit.

You can manually restart the unit even if the retry limit has been exceeded. You can go into the code to debug the unit (this requires the appropriate authorization role), or delete all the units inside the inbound destination.

You can monitor the bgRFC queues by using the implementation guide (IMG). In transaction SPRO open the SAP Reference IMG and navigate to Start of the navigation path SAP NetWeaver Next navigation step SAP Gateway Service Enablement Next navigation step Backend OData Channel Next navigation step Connection Settings to SAP Gateway Next navigation step Monitor bgRFC Queues End of the navigation path.

Proceed as follows to monitor bgRFC queues:

  1. Click on the Activity icon to open the bgRFC monitor.

    Alternatively you can use transaction SBGRFCMON.

  2. Select the option for the Outbound scenario and the Queued unit type. Select other parameters of the monitor as required.

  3. Choose Execute to run the monitor. The status of the queues is displayed.

  4. Monitor the Queue with the Event ID and instance number for the messages which were not sent.