Symptom
- Sales BAPI (e.g. BAPI_SALESORDER_CREATEFROMDAT2, BAPI_SALESORDER_CHANGE) is used in a custom program and is called in a loop.
The processing terminates with a dump:
Category ABAP programming error
Runtime Errors UNCAUGHT_EXCEPTION
Except. /BOBF/CX_FRW_CONTRCT_VIOLATION
ABAP Program CL_SD_SLS_BOPF_TRANS_MGR_UTIL=CP
Application Component SD-SLS
- The same thing also occur when BAPI is called more than once, even it is not inside a loop.
Read more...
Environment
- Sales and Distribution (SD)
- SAP ERP
- SAP ERP Central Component
- SAP S/4HANA
- SAP S/4HANA Cloud Private Edition
Product
Keywords
SD_SALESDOCUMENT_CREATE, SD_SALESDOCUMENT_CHANGE, SD_SALES_DOCU_MAINTAIN, BAPI_SALESORDER_CHANGE, BAPI_SALESORDER_CREATEFROMDAT2, /BOBF/CX_FRW_CONTRCT_VIOLATION, NO_BOPF_TRANS_MGR_CALLS, CL_SD_SLS_BOPF_TRANS_MGR_UTIL=CP, loop, test sequence, commit, rollback, UNCAUGHT_EXCEPTION , DO_SAVE, illegal state , KBA , SD-SLS-GF-IF , Sales Documents BAPI's , SD-SLS , Sales , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview