Inbound BAPI Transactional Support
The adapter 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. If the RFC/BAPI call does not return any errors, the transaction or logical unit of work can be committed.
When automatic commit is disabled, Inbound RFC/BAPI transaction support is available only when using a single adapter instance. For the support of multiple load-balanced adapters, the automatic commit feature is recommended.
An external system invoking a BAPI Request-Response service in the adapter 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_CREATEFROMDAT1Server instance in the SAP system from the adapter does not result in permanent changes to the database until an explicit commit invocation is made with the BAPI_TRANSACTION_COMMITServer instance.
To maintain the context for an individual BAPI invocation service, the Request-Response service for the BAPI transaction requires explicit commit which needs additional configuration in TIBCO Designer. Before configuring a BAPI Request-Response service for explicit committing, you need to run through the checklist given below to ensure that the service really requires configuration for explicit commit.
Explicit configuration for this feature is required only when one or more of the following conditions are satisfied:
-
The BAPI transaction requires explicit commit/rollback in the SAP system.
-
Multiple connections (maxConnections > 1) are configured for the client, which invokes the BAPI transaction in the SAP system and can be used to scale the number of concurrent transactions.
See the following table for descriptions of the two BAPI transactions within the context of the SAP system.
|
BAPI Transaction Name |
Description of Transaction Task |
||||||
|
|
|
||||||
|
|
|