Академический Документы
Профессиональный Документы
Культура Документы
Transaction Model for Developing BAPIs - BAPI Programming Guide Reference (CA-BFA) - SAP Library
SAP ERP
Characteristics
Transactionality
A BAPI must be implemented so that it is transactional. In other words, it complies with the ACID
principle. The BAPI transaction model must also enable users to combine several BAPIs in one LUW.
The BAPI transaction model, therefore, implies both that individual BAPIs must be transactional and that
several BAPIs combined in one LUW must comply with the ACID principle.
Transaction Control in Client
http://help.sap.com/saphelp_46c/helpdata/en/a5/3ec8654ac011d1894e0000e829fbbd/content.htm
1/3
27/6/2014
Transaction Model for Developing BAPIs - BAPI Programming Guide Reference (CA-BFA) - SAP Library
The BAPI transaction model must afford the user explicit transaction control. Therefore, if several BAPIs
are called together, the caller can decide him/herself when to execute a COMMIT WORK (or, as the
case may be, a ROLLBACK WORK). This means that BAPIs themselves cannot (generally) execute a
COMMIT WORK command.
The following restrictions apply to combining several BAPIs in one LUW:
If an instance was created, modified or deleted by a write BAPI, a read BAPI can only access the
most recent data if a COMMIT WORK has taken place.
It is not possible to make two write accesses on the same instance within one LUW. For example,
you cannot first create and then change the object within the same LUW.
You can, however, create several instances of the same object type within an LUW.
Transaction Handling via Service BAPIs
A transaction is completed either using a COMMIT WORK command or a ROLLBACK command. A
BAPI transaction must be ended by calling the BAPIs BapiService.Transaction Commit() or
BapiService.TransactionRollback() .
http://help.sap.com/saphelp_46c/helpdata/en/a5/3ec8654ac011d1894e0000e829fbbd/content.htm
2/3
27/6/2014
Transaction Model for Developing BAPIs - BAPI Programming Guide Reference (CA-BFA) - SAP Library
http://help.sap.com/saphelp_46c/helpdata/en/a5/3ec8654ac011d1894e0000e829fbbd/content.htm
3/3