Hierarchy
SAP_GWFND (Software Component) SAP Gateway Foundation⤷
OPU-BSE-BEP (Application Component) Gateway Business Eventing and Provisioning⤷
/IWBEP/BEP_DT (Package) Gateway - Backend Event Publisher - Design Time
IMG Activity
| ID | /IWBEP/BGRFC_MONITOR | Monitor bgRFC Queues |
| Transaction Code | /IWBEP/57000008 | (empty) |
| Created on | 20100921 | |
| Customizing Attributes | /IWBEP/BGRFC_MONITOR | Monitor bgRFC Queues |
| Customizing Activity | /IWBEP/BGRFC_MONITOR | Monitor bgRFC Queues |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /IWBEP/IMG_BGRFC_MONITOR |
This activity allows you to monitor the Background Remote Function Call (bgRFC) queue to check for unsent messages. All the messages are written in unit queues.
Note
This is a shared configuration step for notifications for OData Channel Push as well as for the Backend Event Publisher.
Use
You can find all the messages that failed to be transported from the Backend Event Publisher to the consumer environment, because of system fault exceptions. System faults are all SOAP standard errors, for example: communication error, or other errors that occurred on the Web service.
You should analyze each error text and decide how best to correct the error. If the error can be fixed, you should send 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.
Note
Application fault exceptions are displayed in the application logs and not the bgRFC.
Requirements
Standard settings
Activities
To monitor the bgRFC queue proceed as follows:
- Click on the activity to open the bgRFC monitor, or use transaction sbgrfc.
- Select procedure as Outbound and unit type as Queued. Select other parameters of the monitor as required.
- Choose Execute to run the monitor. The status of the queues is displayed.
- Monitor the queue with the event group ID name and instance number for unsent messages.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | SBGRFCMON |
History
| Last changed by/on | SAP | 20110414 |
| SAP Release Created in | 100 |
