Solution : https://service.sap.com/sap/support/notes/457499 (SAP Service marketplace login required)
Summary :
When using BAPI_GOODSMVT_CREATE or BAPI_GOODSMVT_CANCEL for posting or canceling goods movements, SAP generates the message M7060 indicating a successful document post. However, the database, including MSEG table, does not reflect these changes as the BAPIs do not handle COMMIT WORK/ROLLBACK WORK. These operations must be manually implemented in the user’s custom application using BAPI_TRANSACTION_COMMIT or BAPI_TRANSACTION_ROLLBACK if needed. The BAPIs work correctly only if no errors occur in the 'Return' parameter, as detailed in their documentation. Transaction SE37 testing does not commit changes, which is expected behavior, not an error. Reference to SAP Note 369518 is recommended for further guidance.
Key words :
system generates message m7060 'document & posted', commit work/rollback work, commit work/ rollback work, customer-specific application, function 'single test', function module bapi_transactions_commit, test bapi bapi_goodsmvt_create, bapi bapi_goodsmvt_create states, transaction se37 -> f8, m7060 reason
Related Notes :
| 520813 | FAQ: BAPIs for goods movements |
| 369518 | Transfer stock not reached if posted with BAPI |