Operations on BAPIs
A Business Application Programming Interface (BAPI) is a method of a SAP business object that can be called by an external process. BAPIs are transactional on the SAP system.
The Microsoft BizTalk Adapter for mySAP Business Suite supports BAPI calls in the outbound direction. It surfaces BAPIs in two ways:
As an RFC. You can invoke a BAPI directly by invoking the appropriate RFC.
As methods of business objects. The adapter surfaces BAPIs as methods of business objects as a convenience to help you retrieve metadata when you use the Consume Adapter Service BizTalk Project Add-in or the Add Adapter Service Reference Visual Studio Plug-in.
|You can invoke a BAPI on the adapter as an RFC or as a method of a business object; but regardless of how you invoke the BAPI on the adapter, it always invokes the BAPI on SAP through the RFC interface.|
The adapter supports BAPI transactions. The BAPI transaction model on SAP enables users to combine several BAPIs into one logical unit of work (LUW). An SAP LUW consists of all the steps involved in a transaction including updating the database.
The topics in this section explain how BAPIs are surfaced as business objects and how BAPI transactions (LUWs) are supported by the adapter.
The adapter surfaces BAPIs as business objects methods as a convenience to help you retrieve metadata when you use the Consume Adapter Service BizTalk Project Add-in or the Add Adapter Service Reference Visual Studio Plug-in. The adapter always invokes BAPIs on the SAP system using the RFC interface.
The adapter surfaces BAPIs by name as operations under the appropriate business object for outbound operations. Business objects are collected by functional group under the BAPI category node by the adapter. (You can browse or search for business objects and BAPIs under the BAPI node when you use the Add Adapter Service Reference Plug-in or the Consume Adapter Service Add-in.)
The SAP adapter supports the following on BAPIs:
For more information about the message structures and SOAP actions used for BAPIs surfaced as business object methods, see Message Schemas for BAPI Operations.
When you invoke a BAPI, it is always part of an LUW on the SAP system. This is true whether you invoke the BAPI as an RFC or as a method of a business object. The RFC SDK treats all BAPIs sent over the same SAP connection as part of the same LUW. After a call to commit or roll back the transaction on a connection, the next BAPI sent over the connection begins a new LUW.
You call BAPI_TRANSACTION_COMMIT or BAPI_TRANSACTION_ROLLBACK to commit or roll back the transaction. The adapter surfaces these two BAPIs:
Under the Basis node as RFC operations.
Under each business object.
You control the BAPIs in a transaction by ensuring that they are all sent over the same SAP connection (including the call to commit or roll back the transaction). You can do this in:
BizTalk Solutions by using the ConnectionState message context property to ensure that the BAPIs in a transaction are sent using the same connection. This property is surfaced by the adapter and provides you with explicit control over the connection used to send a message in a BizTalk orchestration.
For performing BAPI transactions using BizTalk Server, the SAP adapter supports the following message context properties.
For more information, see Performing BAPI Transactions by Using BizTalk Server.
Opens a new channel for the transaction.
Reuse existing channel for the transaction.
Commit the transaction and close the existing channel.
Abort the transaction and close the existing channel.
Note Make sure you set the EnableBizTalkCompatibilityMode binding property when performing transactions using BizTalk Server.
WCF service model solutions by ensuring that the BAPIs in a transaction are sent using the same WCF client. For more information, see Invoking BAPIs by Using the WCF Service Model.
WCF channel model solutions by ensuring that the BAPIs in a transaction are sent over the same WCF channel. For more information, see Developing Applications by Using the WCF Channel Model.
Limitations on BAPI Transactions
The following restrictions apply on BAPI transactions:
It is not possible to make two write accesses on the same instance within one LUW. For example, you cannot create an order and update it in the same transaction.
When performing BAPI a transaction using BizTalk Server, all the messages must be sent over a single host instance of the send port.
If an instance is created, updated, or deleted by using a write BAPI, a read BAPI cannot view the most recent data until the write BAPI is committed.
An external client that invokes an LUW should call all the BAPIs that the LUW contains on the same SAP connection.
|BAPIs that belong to Release 3.1 call COMMIT WORK as part of their implementation. This means that these BAPIs cannot be included with other BAPIs in an LUW (because they will commit the transaction). For more information, see the SAP documentation.|