Notes | |
|---|---|
Overview | This file provides the customer with information on confirmed collections |
Formats | XML |
Delivery & Scheduling | The report can be scheduled to run automatically on a daily, weekly or monthly basis or it can be requested via the web site on an ad-hoc real time basis. It is up to the customers whether this is scheduled. |
File Name Convention | SiteCode_CustomerCode_POCExtr_Datetime.XML |
XML Identifier | <POCExtr> |
Limitations | Customers should be aware that this file is generated once the goods ARE confirmed as collected within our system and we will normally only send this information on one occasion on the next file generated after the confirmation has been made. From VW v5 this will no longer include collections |
Segment and Element Information
Segment | Segment L1 | Segment L2 | Notes |
|---|---|---|---|
<POCExtr> | |||
<HD> | Can repeat within the <POCExtr> multiple times, relating to seperate orders | ||
<LD> | Can repeat within the <HD> multiple times, relating to lines on an order | ||
</LD> | |||
</HD> | |||
<POCExtr> |
XML Segment Name | XML L1 Sub Segment | XML L2 Sub Segment | XML Element Name | MAX Length | Notes |
|---|---|---|---|---|---|
<HD> | |||||
<UID> | 8 | The warehousing unique reference, can be used to provide a full trace within the system, supplied to customers to aid with investigation work and to assist identification of unique goods withdrawal. | |||
<DRef> | 8 | This is the reference supplied by the customer to uniquely identify the goods withdrawal, called Document Reference | |||
<ORef> | 8 | Normally supplied by the customer and used to provide a unique delivery point identifier for the delivery. For example your customer account code for the delivery point. Known as Order Reference | |||
<DPRef> | 15 | If the receiving customers has requested a “purchase reference” to be quoted then this is supplied, this is known as Delivery Point reference. | |||
<CCode> | 12 | Your customer code at the warehouse used to identify which account the stocks came from. | |||
<Site> | 6 | Site Code | |||
<DPName> | 25 | Delivery Point Name | |||
<DPTown> | 25 | Delivery Point Town | |||
<DPPC> | 8 | Delivery Point Postal Code | |||
<CTrans> | 30 | Advised Collection Transport Company | |||
<CStatus> | 6 | Collection Status This will use a number of codes to identify whether the collection was successful or whether there was an issue 1 - Collection Complete without issue 2 - Collection re-landed in Full to stock 3 - Collections partially re-landed to stock | |||
<CDate> | 10 | At the time of collection Date field format dd/mm/yyyy. | |||
<CTime> | 5 | At the time of collection Time field hh:mm. | |||
<CName> | 50 | At the time of collection Name of the person collecting and ultimately the signatory | |||
<CReg> | 30 | At the time of collection Collection Vehicle Registration Number | |||
</HD> | |||||
<LD> | |||||
<PC> | 20 | Product Code | |||
<Rtn> | 10 | Rotation Number | |||
<RtnLn> | 6 | Rotation Line Number | |||
<OCse> | 6 | Ordered Cases | |||
<OSgl> | 6 | Ordered Singles | |||
<TOSgl> | 6 | Total Ordered quantity in singles | |||
<CCse> | 6 | Collected Cases | |||
<CSgl> | 6 | Collected Singles | |||
<TCSgl> | 6 | Total Collected quantity in singles | |||
<SOLn> | 6 | Your line number as specified in your sales order file | |||
</LD> |