Page Comparison

This contains general and hopefully useful information about how the system processes sales order / despatch of stock files.

 To ask general questions on any of the EDI formats, then please send an email to editest@visionsuite.co.uk 
We aim to respond to your request within 3 working days once we have contacted our Vision EDI customer.

XML – a file structure which takes into account all the functionality and field within the warehousing system. We use a very basic form of XML which allows nearly anybody to create the file from many systems.

Each warehouse determine their own cut-off times for transmission of orders, but as Vision EDI is fully automated we prefer if customers are constantly sending sales orders throughout the day, not only does it keep orders flowing to the warehouse but it also stops delays at cut-off times when everybody tries to send.  The other additional benefit is that should you have a system problem at the cut-off the effect is minimised.

We would therefore strongly encourage customers to transmit files on a regular or real time basis.
The Vision EDI service normally operates 24 hours a day and 7 days a week.

Your sale order file names should be of a standard format which will allow us to identify any file uniquely for a particular customer code, each Sales Order file would begin "SO....."

SO(YY)YYMMDD_hhmmssttt.<customer code>       e.g. SO051214_123204000.ABCD1234   OR

SO(YY)YYMMDD_<orderNo>.<customer code>       e.g. SO051214_SO0123456.ABCD1234  OR

SO(YY)YYMMDD_hhmmss_<orderNo>.<customer code>       e.g. SO051214_123204000_0123456.ABCD1234

Key
YY = year        can be 2 or 4 digit year                
hh = hour                    
ttt = milliseconds
MM = month of the year
mm = Minutes past the hour
DD = day of month
ss = seconds 

The customer code for the filename would normally be the same code as used in the customer code field of the order file, although we can accept a file which contains orders for multiple customer accounts.

Please try to avoid exceeding 32 characters in the file name.

We use this convention to identify the filetype, it allows us to pre-process the file before we parse the XML as we perform various checks on the filename existance for duplication purposes.  It also allows us to identify which XML model we will be using for the filetype and allows us to process faster, it also allows us to check whether your customer code has permissions for the filetype without us having to load the file to see what is in it and finally it allows us to acknowledge we have the file back to you without having to open and read the contents.

We also do not allow multiple different file types in the same file, so a sales order file can only contain sales orders, and this then negates the need to use XML namespaces.

See section below

See section below