Symptom
You have a custom program where you call different BAPIs in the same Logical Unit of Work (LUW). All looks ok but you are observing strange behaviors, such as:
- Short dump, ie. OBJECTS_OBJREF_NOT_ASSIGNED
- Some values are not updated correctly after the first call of the BAPI (however, the first BAPI called has all data saved properly), ie. PO Price.
Read more...
Environment
- Materials Management (MM)
- SAP ERP Central Component
- SAP ERP
- SAP enhancement package for SAP ERP
- SAP enhancement package for SAP ERP, version for SAP HANA
- SAP S/4HANA
- SAP S/4HANA Cloud Public Edition
Product
Keywords
ECC, BAPI, BAPI_PO_CHANGE, BAPI_CONTRACT_CHANGE, BAPI_SAG_CHANGE, BAPI_PR_CHANGE, BAPI_PO_CREATE1, BAPI_CONTRACT_CREATE, BAPI_SAG_CREATE, BAPI_PR_CREATE, BAPI_PO_GETDETAIL1, LUW, IDOC, EDI, BAPI_CONTRACT_GETDETAIL, OBJECTS_OBJREF_NOT_ASSIGNED, SAPLMEOUT, GET_LIST_FOR_BAPI, IF_PURCHASE_OUT_HEADER~IS_CONTRACT, LMEOUTP0, BAPI_ENTRYSHEET_CREATE , KBA , MM-PUR-PO-BAPI , BAPIs - Purchase order , MM-PUR-OA-BAPI , BAPIs - Outline Agreements , MM-PUR-REQ-BAPI , BAPIs - Purchase requisition , 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