Solution : https://service.sap.com/sap/support/notes/192235 (SAP Service marketplace login required)
Summary :
When using BAPIs in SAP R/3 system, as of Release 4.0A, data updates initiated by BAPI calls are not executed immediately. Users must manually trigger these updates through the BAPI_TRANSACTION_COMMIT function module. Even then, the asynchronous nature of these updates means they may continue after exiting the module. From Release 4.5A, the addition of the "WAIT" parameter in BAPI_TRANSACTION_COMMIT ensures that the module exits only once the update is complete, solidifying transactional integrity. For users of Release 4.0, manual implementation of this enhancement through specific correction instructions is necessary, whereas, in later releases, it becomes a standard feature.
Key words :
reference field bapif4a-descrip, optional import parameter wait, parameter wait manually, service bapis reason, previous bapi calls, function module bapi_transaction_commit, function module, terms bapi, written data, business object
Related Notes :
| 809747 | BAPIs and update |
| 450442 | BAPI: Data is not updated |
| 131838 | Collective note for BAPIs w/ 'Commit Work' command |