Overview
You can create RFCs on the SAP system that invoke services on Integration Server. This allows SAP users to access the information that is available via Adapter for SAP. Before you can create an RFC that invokes a service, or send an IDoc to Adapter for SAP, you must configure the SAP system to have an RFC destination for an RFC listener running at Adapter for SAP. This enables the SAP system to send RFCs to Adapter for SAP. You must also configure the adapter to have an RFC listener that listens for RFCs from the SAP system.
After you have the SAP system and Adapter for SAP configured, you can create a function module on the SAP system that requests the execution of a service synchronously or you can send an IDoc to Adapter for SAP for further synchronous or asynchronous processing. To do so, you also need to create a listener notification on Adapter for SAP. The listener notification indicates either what service the adapter is to execute when it receives a message from the SAP system or how to publish a corresponding document.
Adapter for SAP supports the following types of notifications that can be assigned to an RFC listener.
RFC listener notification (synchronous)
RFC listener notification (asynchronous)
ALE listener notification (synchronous)
ALE listener notification (asynchronous)
If there is no listener notification assigned to the RFC listener, the received message will be forwarded to the routing listener. For more information, see
Routing Messages Through Adapter for
SAP.
Note:
In this context, synchronous or asynchronous refers to the processing on Integration Server. It does not indicate how the message was processed on the SAP system. However, in the case of an ALE listener notification, there is always a TID assigned to the message. In the case of an RFC listener notification, a TID will be present in the pipeline only for transactional RFC calls from the SAP system.