Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Routing Messages Through Adapter for SAP | Sending a BAPI from an SAP System to Adapter for SAP
 
Sending a BAPI from an SAP System to Adapter for SAP
 
Setting Up a Routing Notification for the XML Transport
Dynamic Routing Using the XML Transport
SAP systems communicate with Adapter for SAP on an implementation-level when calling BAPIs. This means, they try to call the implementing function module directly via RFC or, if asynchronous processing is used, they send an IDoc.
Adapter for SAP has a built-in converter to automatically rebuild the original object-based BAPI method call and represent it as an XML message. Therefore, the XML transport can handle these messages using the XML dialect bXML, to build a BAPI-style XML message.
To activate this function, you have to specify a routing notification that maps the BAPI call to the XML transport. The message types used in the routing notification for routing are based on the BAPI implementation. For messages received from an SAP system, this means:
*The RFC name of the BAPI implementation is used for synchronous calls
*The corresponding ALE message type is used for asynchronous calls
These message types can be found using the built-in BAPI browser. At the routing notification setup, you have to specify the name of the business object and BAPI to which the call should be mapped.