Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


Notes
OverviewThis file provides the customer with information on confirmed collections
FormatsXML
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 ConventionSiteCode_CustomerCode_POCExtr_Datetime.     (csv or 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 


XML
Segment Name
XML
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>6Site Code



<DPName>

25




<DPTown>

25




<DPCode>

8




<CStatus>

6

Collection Status

This will use a number of codes to identify whether the collection was successful or whether there was an issue

CodeDescription
1Collection Complete without issue
2Collection re-landed in Full to stock
3Collections partially re-landed to stock


<CDate>10Date field format dd/mm/yyyy


<CTime>5Time field hh:mm


<CName>50Name of the person collecting and ultimately the signatory

</HD>





<LD>







<PCode>

20




<Rtn>

10




<RtnLn>6



<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>






Summary of some Abbreviated Codes Used within Files

Delivery Problem Codes
CNI         Customer Not In
DMB      Driver Missed Booking
DRB        Delivery Required Booking
IDI          Incorrect Delivery Information
OTH       Other Reason


Delivery Line Problem Codes

BIT          Broken in Transit
BIW        Broken in Warehouse
NLH        Not Loaded Haulier Error
NLW      Not Loaded Warehouse Error
NO         Not Ordered by Customer (Refused Item)
OC          Order Cancelled
OR          Other Reason
PE           Picking Error by Warehouse
UI            Under Investigation

Please contact your warehouse for a full and complete list of the codes that they are using.

  • No labels