Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Templates and file examples

The example template below can be used as a starting point for an FTP integration. CSV file templates can be found here. The specific mapping is confirmed with the client during integration with SEKO.

LR_Load_Receipts.xml

FTP XML Response file examples

For XML FTP uploads, the system provides a response file. Below are examples of the response file. More information on response files can be found here.

FAILURE_LR_Load_ReceiptsReceipts1.xml_1622-1006-1721-111015143525_response.xml

SUCCESS&FAILURE_LR_Load_Receipts.xml_16-10-17-112516_response.xml


XML formatting

Example body

<Requests>
<Request>
<Receipt>
<ReceiptReasonCode>string</ReceiptReasonCode>
<UpdateReceipt>true</UpdateReceipt>
<ReceiptType>string</ReceiptType>
<ASNNumber>string</ASNNumber>
<GUID>string</GUID>
<HBReference>string</HBReference>
<IsReturn>true</IsReturn>
<Notes>string</Notes>
<WarehouseETA>1970-01-01T00:00:00.001Z</WarehouseETA>
</Receipt>
<ReceiptHeader>
<DCCode>string</DCCode>
</ReceiptHeader>
<List>
<ReceiptLineItem>
<LotNumber>string</LotNumber>
<CaseCount>1</CaseCount>
<BestBeforeDate>1970-01-01T00:00:00.001Z</BestBeforeDate>
<SupplierName>string</SupplierName>
<CountryOfOrigin>string</CountryOfOrigin>
<MIDCode>string</MIDCode>
<Channel>string</Channel>
<EAN>string</EAN>
<GUID>string</GUID>
<LineNumber>1</LineNumber>
<ProductCode>string</ProductCode>
<Quantity>1</Quantity>
<ReturnReason>string</ReturnReason>
<SupplierCompanyCode>string</SupplierCompanyCode>
</ReceiptLineItem>
</List>
</Request>
</Requests>
</Responses>

Example success response body (2 entities)

<Responses>
<Response>
<CallStatus>
<Success>true</Success>
<Code>0</Code>
<Message></Message>
</CallStatus>
<GUID>60ce1670-b04e-485d-9441-4d7f0716db91</GUID>
</Response>
<Response>
<CallStatus>
<Success>true</Success>
<Code>0</Code>
<Message></Message>
</CallStatus>
<GUID>60ce1670-b04e-485d-9441-4d7f0716db92</GUID>
</Response>

Example failure response body (2 entities)

<Responses>
<Response>
<CallStatus>
<Success>true<<Success>false</Success>
<Code>0<<Code>100</Code>
<Message><<Message>Error Submitting Receipt: ASNTest123 - Error. Product PMTest123-89 does not exist.</Message>
</CallStatus>
<GUID>60ce1670<GUID>980af636-b04e8f5d-485d4449-9441a85d-4d7f0716db91<35ded0d1c7e0</GUID>
</Response>
<Response>
<CallStatus>
<Success>false</Success>
<Code>100</Code>
<Message>Error . Invalid Mapping - DC<Submitting Receipt: ASNTest456 - Error. Product PMTest123 does not have supplier INDSUP001-7678</Message>
</CallStatus>
<GUID /> <GUID>ae11c373-39ab-4e75-b026-2cad6464a92f</GUID>
</Response>
</Responses>

Example success and failure response in a single XML file (2 entities)<Responses>
<Response>
<CallStatus>
<Success>false</Success>
<Code>100</Code>
<Message>Error. Product PMTest123 does not have supplier INDSUP001</Message>
</CallStatus>
<GUID />
</Response>
<Response>
<CallStatus>
<Success>false</Success>
<Code>100</Code>
<Message>Error. Invalid Mapping - DC</Message>
</CallStatus>
<GUID />
</Response>
</Responses>