Inbound BAPI Transactional Support

TIBCO ActiveMatrix Adapter for SAP supports one or more RFC/BAPI calls to be executed as a transaction or logical unit of work in the SAP system. The last RFC/BAPI call is used to commit the transaction or logical unit of work in the SAP system.

For the case where the transaction or logical unit of work consists of only one RFC/BAPI call, the adapter supports the feature of automatic commit as described in Enabling Automatic Commit. If the RFC/BAPI call does not return any errors, the transaction or logical unit of work can be committed.

An external system invoking a BAPI Request-Response Service service in the adapter configuration has the choice to explicitly commit or rollback the changes applied to one or more business objects by the BAPI transaction in the SAP system. The explicit commit or rollback is not a mandatory requirement for all BAPI transactions but is needed wherever the underlying BAPI transaction in the SAP system is implemented in this way.

For example, an invocation of BAPI_SALESORDER_CREATEFROMDAT1 function module in the SAP system from an adapter configuration does not result in permanent changes to the database until an explicit commit invocation is made with the BAPI_TRANSACTION_COMMIT function module.

To maintain the context for an individual BAPI invocation service, the Request-Response Service service for the BAPI transaction requires explicit commit which needs additional configuration in TIBCO Business Studio. Before configuring a BAPI Request-Response Service service for explicit committing, you need to run through the following checklist to ensure that the service really requires configuration for explicit commit.