3573520 - StandardID (Global Location Number) is Not Recognized in VendorParty in InboundDeliveryExecutionConfirmation

You are facing an issue processing the incoming message from 3PL provider when you maintain in the payload the Standard ID (GLN (Global Location Number)) of the Location under "Vendor Party" instead of the Internal ID.

The system is returning error messages and failing to create the Inbound Delivery.

In the IDEC, the mandatory attribute VendorParty does not seem to accept a StandardID (GLN). Instead, only an InternalID seems to work. However, per IDEC documentation, all Parties can be communicated via internal as well as standard IDs, including the GLN. 

SAP Business ByDesign

1. Logon to the back-end of the system.
2. Open the Transaction MDRS.
3. Open the Inbound Service InboundDeliveryExecutionIn
4. Consume the payload.
5. The system return the response as follows: 

<n0:StandardFaultMessage xmlns:n0="http://sap.com/xi/AP/Common/Global" xmlns:prx="urn:sap.com:proxy:L40:/1SAI/TAS5118194EC91140F9E030:804">
 <standard>
  <faultText>Inbound delivery notification reference is not valid or does not exist.</faultText>
 </standard>
 <addition>
  <Log>
   <Item>
    <TypeID>124(/APDL_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>Identified stock B3034 not valid</Note>
   </Item>
   <Item>
    <TypeID>020(/APDL_CID_VAL/)</TypeID>
    <CategoryCode>INC.COI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>The inbound delivery notificaton reference is not valid. Correct the inbound delivery notification reference.</Note>
   </Item>
   <Item>
    <TypeID>049(/LSC_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>One reference document from type Outbound Delivery and item type Delivery Transfer Item must be assigned</Note>
   </Item>
   <Item>
    <TypeID>124(/APDL_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>Identified stock * not valid</Note>
   </Item>
   <Item>
    <TypeID>093(/LSC_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>The address data is missing.</Note>
   </Item>
   <Item>
    <TypeID>071(/LSC_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>Vendor Party party ID missing</Note>
   </Item>
   <Item>
    <TypeID>149(/APDL_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>Numbering formats must be maintained for warehouse provider</Note>
   </Item>
   <Item>
    <TypeID>014(/LSC_VAL/)</TypeID>
    <CategoryCode>INC.BOI</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>At least one location with role category Ship From Location must be assigned</Note>
   </Item>
   <Item>
    <TypeID>001(/APDL_IDEC_AGENT/)</TypeID>
    <CategoryCode>ENV.CBM.BRU</CategoryCode>
    <SeverityCode>3</SeverityCode>
    <Note>Inbound delivery notification reference is not valid or does not exist.</Note>
   </Item>
  </Log>
 </addition>
</n0:StandardFaultMessage>

You have maintained the GLN under Location, but we noticed that the GLN is not maintained for the Vendor Party under Org. Structure. 

Please kindly maintain the GLN on the org unit level (External Identifiers) as well. 

IDEC, Vendor Party, StandardID, SchemeAgencyID, InboundDeliveryExecutionConfirmation, 3PL , KBA , AP-IDP , Inbound Delivery Processing , Problem