Solution : https://service.sap.com/sap/support/notes/744403 (SAP Service marketplace login required)
Summary :
When using BAPIs for confirmation transactions such as BAPI_PRODORDCONF_CREATE_ACT without results, it is often due to the absence of a 'COMMIT WORK' statement post-BAPI call. The standard functioning of these BAPIs requires a follow-up 'COMMIT WORK' or invocation of 'BAPI_TRANSACTION_COMMIT' to finalize database updates. When testing in SE37, employ test sequences to include necessary transaction commits. Employ the 'COMMIT WORK AND WAIT' or set the WAIT parameter in 'BAPI_TRANSACTION_COMMIT' to handle synchronous updates, noting potential locking issues in scenarios where BAPIs follow each other closely.
Key words :
function module --> test --> test sequenceshere, usea test sequence, prerequisites sap standard -->, allthe v1 updates, wait statement/flag, 'commit work' statement, statement 'commit work, confirmation bapi call, function modules, commit work
Related Notes :
| 1586230 | FAQ: Confirmation using BAPI in production order |
| 208477 | Consulting: Process control in confirmation |