Versions Compared

Old Version 12

changes.mady.by.user Alan Gilchrist

Saved on

compared with

New Version 13

changes.mady.by.user Alan Gilchrist

Saved on

Key

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

...

Notes

Questions

 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.

Format

XML – a file structure which takes into account all the functionality and field within the warehousing system.

Expand
titleTradacomms / EDIFACT ?

Whilst the larger organizations like to utilize these formats, we have used these formats in the past but their inability to be flexible, lack of fields and   the cost of integration and development times mean that many smaller customers would not be able to afford the development costs to implements EDI trading.

There are also serious limitations to the EDI format resulting in not all fields being submitted or fields having to be translated before use.

There is also the added problem of using a third party in the sending of the data and all too frequently the third party is blamed for loss of data and for any problems which occur when actually in 99% of cases it is the customers lack of understanding of the process which has caused the problem.

We offer a service using a third party, Atlas Products, who can take files from customers in this format and convert them to our import formats.

If you require further details please contact sales@ontechsolutions.net

Transmission

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.

File naming

Whether testing, sending live or sending an API file using the fall back method the filename must conform to the following.

  1. It must be prefixed with SO

  2. The suffix must be the warehouse customer code.

  3. It must not be zipped

  4. The filename should not exceed 32 characters

Expand
titleSuggestions for filenames

Suggestions for filenames

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 / hh = hour / ttt = milliseconds / MM = month of the year / mm = Minutes past the hour / DD = day of month / ss = seconds 

Customer code for the filename would normally be the same code as HD1 (FKCustomer)

We use this convention to identify the filetype; allows pre-processing before we parse the XML; identify which XML model; process faster; check incoming customer permissions; provide acknowledgements back to you.

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.

...