Troubleshooting
Problem
After a commit call is issued in SAP (BAPI_TRANSACTION_COMMIT) the error message '150 The Posting/Update could not be processed' can be seen within the JCO trace. After this, the connection is released and no FAILURE can be seen inside the transaction manager logs resulting in missing data in SAP.
Symptom
A BAPI functional call is sent in SAP which is successful. Afterwards a commit call is issued (BAPI_TRANSACTION_COMMIT)and SAP raises an error which can be seen within SAP SM13 (Error - no retry). At the end of the BAPI_TRANSACTION_COMMIT within the JCO trace is the message '150 The Posting/Update could not be processed'. After that the connection is released and no FAILURE can be seen within the transaction manager.
As the Transaction Manager reads the return message from a function module execution only for BAPI's and not for the commit calls this error goes unnoticed within the Transaction Manager and the transaction is shown as successful.
The results of this behaviour leads to missing data in SAP. The expected behaviour would be that this call of the mediation module fails when any of its used participants returns a fail and a corresponding error message be logged within ESB.
Environment
All SAP Adapter version 7.0.0.3 up to 7.0.0.3_IF15.
Resolving The Problem
This problem has been solved with APAR JR39757.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21508451