SAP Knowledge Base Article - Preview

3584896 - Inco. Location1 is not correct when creating scheduling agreement via SchedulingAgreementERPRequest - SAP ERP & SAP S/4 HANA

Symptom

Inco. Location1(EKKO-INCO2_L) is set in the payload for SchedulingAgreementERPRequest as below:
<Incoterms>
<ClassificationCode>XXX</ClassificationCode>
<TransferLocationName>YYY</TransferLocationName>    ----> Inco. Location1(EKKO-INCO2_L)
</Incoterms> 

However, after SA creation, the actual Inco. Location1 value is not same with the one in payload.

Same issue can be found when creating scheduling agreement via BAPI_SAG_CREATE.


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 all versions ; SAP S/4HANA all versions

Keywords

BAPI_SAG_CREATE, Inco. Location1, scheduling agreement, EKKO-INCO2_L , KBA , MM-PUR-OA-SCH , Scheduling Agreement , 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.