Showing results for 
Search instead for 
Did you mean: 

This note needs to be extended to the BAPI - 3368061 - NO_BOPF Flag for SD Function Modules

0 Kudos

Dear SAP, 

We are currently experiencing short dumps in S/4HANA 2023 On-Premise with some of our programs and jobs that use the standard sales order BAPIs BAPI_SALESORDER_CREATEFROMDAT2 or BAPI_SALESORDER_CHANGE as the BOPF transaction manager cannot be explicitly disabled to allow external commits and rollbacks.

We have soft checks on our user exits (no hard error messages thrown) and don't have any commit statements in there that break transactional consistency of BOPF.

However, without explicitly disabling the BOPF transaction manager in SAPMV45A, we cannot process the above BAPIs within a single LUW.

You have already applied a fix for this to the underlying sales document function modules called by the BAPI adding a parameter named I_NO_BOPF_TRANS_MGR_CALLS via the note 

3368061 - NO_BOPF Flag for SD Function Modules

Could you please extend this parameter to the BAPI as well ? 

Tharindu W

Accepted Solutions (0)

Answers (0)