SAP MDG · COMMUNITY
How do I configure and monitor multiple bgRFC inbound destinations for asynchronous ABAP Web Services?
Yes. Asynchronous ABAP Web Services can use more than one bgRFC inbound destination. Maintain the switch `ADD_INB_DEST_MAINTAIN = X`, create the additional destination in `SRT_UTIL`, assign it with `SRT_INB_ASG_MAINTAIN`, and monitor the queue name in `SRT_MONI`.
Yes. Asynchronous ABAP Web Services can use more than one bgRFC inbound destination. Maintain the switch `ADD_INB_DEST_MAINTAIN = X`, create the additional destination in `SRT_UTIL`, assign it with `SRT_INB_ASG_MAINTAIN`, and monitor the queue name in `SRT_MONI`.
Yes, asynchronous ABAP Web Services can use more than one bgRFC inbound destination. The default destination remains available, and additional destinations are maintained in `SRT_UTIL`, assigned with `SRT_INB_ASG_MAINTAIN`, and identified in `SRT_MONI` by queue prefixes such as `SQT<track number>C_` or `SQT<track number>P_`.
Process flow
- Run `SPROXSET` and set `ADD_INB_DEST_MAINTAIN = X` at user or global level.
- Open `SRT_UTIL` and go to **Tools -> Global Configuration**.
- Add the additional bgRFC inbound destination; SAP creates the corresponding `SBGRFCCONF` entry.
- Assign the destination with `SRT_INB_ASG_MAINTAIN` (run via `SE38`) using the configuration key and binding key / technical key.
- Check or adjust resources in `SBGRFCCONF` if required.
- Verify processing in `SRT_MONI` using **Technical View** and the queue name prefix.
Maintain `ADD_INB_DEST_MAINTAIN = X`
Enable maintenance of multiple bgRFC inbound destinations at user or global level.
Tools -> Global Configuration
Create and maintain additional bgRFC inbound destinations.
SE38Run program `SRT_INB_ASG_MAINTAIN`
Assign an additional bgRFC inbound destination to a consumer proxy logical port or service provider endpoint.
Maintain bgRFC inbound destination resources
Adjust resources assigned to a bgRFC inbound destination.
Technical View -> Queue Name
Identify whether an additional or default bgRFC inbound destination processed the message.
Referenced tables
| Object | Purpose |
|---|---|
SBGRFCCONF | Contains the bgRFC inbound destination configuration entry created for additional destinations; resources can also be maintained here. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- Does using an additional destination change the normal message lifecycle?
- Why use multiple bgRFC inbound destinations?
- How do I configure multiple bgRFC inbound destinations?
Possible questions
- What is `ADD_INB_DEST_MAINTAIN`?
- How do I assign a bgRFC destination to a consumer proxy logical port?
- How do I determine which bgRFC inbound destination processed a message?
- What does `SQT1C_` mean?
- Can the default destination be deleted?