Invoking Multiple RFC/BAPI Transactions as One Transaction in the SAP System

Invoke multiple RFC/BAPI transactions in the SAP system as one transaction.

When the transaction feature is in use, the load balancing functionality of the adapter configuration, RVCMQ and multiple services of the adapter configuration cannot be used.

Procedure

Invoke the first RFC/BAPI transaction.
1. To start a transaction, in the RFCClosure class, set the bInTransactionContext property to 1.
2. If the transaction requires a dynamic connection, you have to populate the properties in the DynamicConnection structure accordingly.
3. Specify the contextTimeout property accordingly.
Note: If the next RFC/BAPI transaction is not made within the time specified by the contextTimeout property, the transaction held inside the adapter configuration can timeout and the resources tied up by the transaction are released.
Invoke the last RFC/BAPI transaction. the property bInTransactionContext is set to 1.
1. Set the bInTransactionContext property to 1.
2. To mark the end of the transaction, set the bContextEnd property to 1.
To invoke the next RFC/BAPI transaction, the session ID returned from the first RFC/BAPI transaction is passed on the RFCCLOSURE class. If the session ID is not passed on the call, a new transaction is created.