Symptom
- When creating a purchase contract using BAPI_CONTRACT_CREATE, the field Supplier Material Number (EKPO-IDNLF) is provided in ITEM and flagged in ITEMX (ITEMX-IDNLF = 'X'), but it is not retained in the saved contract when no Purchase Info Record (PIR) exists.
- When a PIR exists, the value is correctly taken over into the contract.
- In transaction ME31K, a manually entered Supplier Material Number is retained even without a PIR.
- During debugging, method IS_VALID of class LCL_R_IDNLF is called twice per contract item; the field is set on the first call and reset on the second.
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
Product
SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 all versions ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023 ; SAP S/4HANA 2025 ; SAP enhancement package 1 for SAP ERP 6.0 ; SAP enhancement package for SAP ERP, version for SAP HANA all versions
Keywords
bapi_contract_create, idnlf, supplier material number, ekpo-idnlf, outline agreement, contract item, pir, purchase info record, me31k, badi, validation, lcl_r_idnlf, is_valid, itemx-idnlf, mm-pur-oa-bapi , KBA , MM-PUR-OA-BAPI , BAPIs - Outline Agreements , 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