EDI856_ASN Creation for RO

[Former Member]

Hello,

We are using RO (Replenishment Order) process in SNC

Using EDI856 methodology to create ASN against the replenishment order, I am facing Error Message in XML, have tried implementing SAP Note 1696005, but still facing same error... It is looking for customer location determination (/SCA/DM_MDCOMP)

Please help me to resolve this error, attached the XML failure message, EDI File which I tried to process.

Note: When I try to create ASN Against the RO manually in SNC Webview, I am not facing any issue.

Pay Load:

  <?xml version="1.0" encoding="UTF-8" ?>

- <ns0:DespatchedDeliveryNotification xmlns:ns0="http://sap.com/xi/SCMBasis/Global">

- <MessageHeader>

  <ID schemeAgencyID="B2B">D89D677399F01ED5898113A93841D87B</ID>

  <CreationDateTime>2015-07-06T12:54:32</CreationDateTime>

- <SenderParty>

  <InternalID schemeAgencyID="EWD">2000296</InternalID>

  <StandardID schemeAgencyID="EWD">2000296</StandardID>

  </SenderParty>

- <RecipientParty>

  <InternalID>U001</InternalID>

  </RecipientParty>

  </MessageHeader>

- <Delivery actionCode="01">

  <ID />

  <ConsigneeID>530214</ConsigneeID>

  <CreationDateTime>2015-07-06T12:54:32</CreationDateTime>

- <BuyerParty>

  <InternalID>U001</InternalID>

  <ConsigneeID>U001</ConsigneeID>

  </BuyerParty>

- <ConsigneeParty>

  <InternalID>U001</InternalID>

  <ConsigneeID>U001</ConsigneeID>

  </ConsigneeParty>

- <ShipToLocation>

  <InternalID>8312</InternalID>

  <ConsigneeID>8312</ConsigneeID>

  </ShipToLocation>

  <GrossWeightMeasure unitCode="LBR">00000000000000100</GrossWeightMeasure>

  <ArrivalDateTime>2015-07-07T23:59:00</ArrivalDateTime>

  <IssueDateTime>2015-07-09T23:59:00</IssueDateTime>

  <WayBillID>NOTECHK</WayBillID>

- <TransportMeans>

  <ID>302421</ID>

  <DescriptionCode>Z99</DescriptionCode>

  </TransportMeans>

- <Item>

  <ID>000001</ID>

- <PurchaseOrderReference>

  <ID>4100000043</ID>

  <ItemID />

  </PurchaseOrderReference>

- <SchedulingAgreementReference>

  <ID />

  <ItemID />

  </SchedulingAgreementReference>

- <Product>

  <InternalID>0000000000000000000000000004050008535400</InternalID>

  <ConsigneeID>0000000000000000000000000004050008535400</ConsigneeID>

  </Product>

- <Batch>

  <InternalID>POCHK123</InternalID>

  </Batch>

  <Quantity unitCode="LBR">233.000</Quantity>

  </Item>

  </Delivery>

  </ns0:DespatchedDeliveryNotification>

[former_member194108 · Accepted solution]

Hi Guru,

i think you are missing SchedulingAgreementReference in XML. Can you check uploading XML afte rputting the value for Schedulig Agreement reference.

- <PurchaseOrderReference>

  <ID>4100000043</ID>

  <ItemID />

  </PurchaseOrderReference>

- <SchedulingAgreementReference>

  <ID />

  <ItemID />

  </SchedulingAgreementReference>

Regards,

Rahul

[Former Member · Accepted solution]

Hi Rahul,

RO Process work on Contract reference and not SA, this is SAP Standard.

Its Looking at this Customizing : But Failing at Customer Determination

IMG <> Basic Settings <>  Processing Inbound and Outbound Messages <> Maintain Settings for Master Data Completion

DDN <> DESDLVRY_I (MD Profile),

SHIP FROM

SHIP TO

CUSTOMER LOCATION

In sequence with Location number column as blank.... as per SAP Std.

regards,

Guru

[former_member194108 · Accepted solution]

Hi Guru,

Please check your BP & T-lanes are in place. BP should be assigned to Location also in Location master.

Regards,

Rahul

[Former Member · Accepted solution]

Hi Guru,

System is failing to determine the customer location(Plant) 8312 from the PO refrence doc.i.e nothing but your contract or the info record.

1. Please check wether you using the correct plant code.?

2. Check the T lane for the involved product. refrence doc and Purchase org should be there. Based on the Purchase org only system will determine the customer location.

2. Check the External procuremnt relation ship. it shoukd be active and the valididty end date should be in future.

[Former Member · Accepted solution]

Hello Mahesh,

1) Yes, Correct Plant Code is seen in T Lane Header as 8312 only.

2) Yes, T Lane has right Contract reference and POrg also for Plant 8312

3) EPR is active and Validity till 2017.

My doubt, I am able to create ASN against the RO Manually using Portal without any issues, only when I try to process through EDI Process, its failing...

Regards,

Guru

[Former Member · Accepted solution]

Hey Rahul,

T Lanes are right, and BP are assigned to Locations, else XML will fail with this reason..

Some problem in EDI file, which need to be figured out

Regards,

Guru

[Former Member]

Hi Guru,

Please check the data and the data format in the EDI file. Issue seems to be with the data in the EDI file.

Regards,

Mahesh