You create or define a background remote function call (bgRFC) destination, which is used for communications in an outbound queue, and an inbound queue among SAP systems. This is an activity that is done in the backend system, that is, the system where software component IW_BEP is installed.
If you are using push from a backend system to an SAP Gateway hub system, it is important not to have a trusted RFC connection. This is because the WF-BATCH user which is the current user in the case of Workflow is not a dialog user and therefore cannot be used for RFC. Instead a dedicated technical user like ALEREMOTE has to be maintained in the RFC destination in the backend system.
You can also use an existing bgRFC destination in your SAP system to the host of SAP Gateway.
You can define this remote function call by using the implementation guide (IMG). In transaction SPRO open the SAP Reference IMG and navigate to .
Proceed as follows to create the bgRFC destination:
Click on the Activity icon.
Choose Create. The RFC Destination Window displays.
In RFC Destination specify a name for the RFC destination to be created. For example, BEP_BGRFC_DEST.
In Connection Type enter 3, for ABAP connections.
In Description 1, enter an explanatory text.
Choose Enter, and select tab Technical Settings.
Enter the SAP Gateway host name in Target Host, and enter its corresponding system number.
On tab Logon & Security enter the technical user and make sure that Current User is not selected.
Choose Enter and select the Special Options tab.
Depending on the SAP NetWeaver version, do the following:
For SAP NetWeaver 7.02, go to section Select Transfer Protocol and select 1 Classic with bgRFC from the list.
For SAP NetWeaver 7.0, go to section Select qRFC Version and select bgRFC from the list in qRFC Version.
Choose Save and Yes to close the warning message that displays.
Choose Remote Connection to test the connection. Information about the connection type displays.