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 | Routing Notifications | Configuring a Routing Notification | BAPI Transport
 
BAPI Transport
Use this transport to route an BAPI to an SAP system via RFC or tRFC.
Set the transport parameters as follows:
Key
Value
serverName
Name of the SAP system to which you want to route the BAPI. Select an RFC connection alias from the drop down list.
The drop down list contains the RFC connection aliases as defined on Adapter for SAP. For instructions on how to define an RFC connection to an SAP system, refer to Configuring Adapter Connections.
Processing restrictions
Processing restrictions: Some BAPIs can be called both synchronously and asynchronously. Callers can choose how they want to execute a call by specifying a transaction id in the XML header (see Using BizTalk Envelopes with Adapter for SAP). If you only want to allow one specific type of call (for example for performance reasons only asynchronous calls, or for administration reasons only synchronous calls). You can define restrictions using the drop down list:
no restrictions
Caller may decide to send both synchronous and asynchronous calls.
synchronous only
Caller may only send calls without a transaction ID. Messages with a transaction ID (asynchronous messages) are rejected and an XML error message is returned.
asynchronous only
Caller may only send calls with a transaction ID. Messages without a transaction ID (synchronous messages) are rejected and an XML error message is returned.