EdiSpecial < Cargooffice

Tags: view all tags
---++ Special EDI formats
   * It is important to understand that every 'Special EDI format' is a tailor made solution.
   * Yes, we do have scripts for standards like Fortras, GS1, EDIFACT etc. but these "standards" are different for everyone, so in effect not "standard" at all. But since we do have a lot of these scripts we are probably able to help you in hours in stead of days.
   * EDI solutions might look simple from the outside but they usually aren't.<br /> Reading an Excel file for example is indeed very simple, yet the content might be TIR (totally incompatible rubbish). An Excel file is nothing more than a scratch-pad and will be rubbish sooner or later as people tend to become less disciplined in typing accurate data in these files.

__There is no such thing as a simple EDI solution.__

Appoint a dedicated person to create a simple overview (ideally 1 or 2 pages) containing:<br />
   1 The parties involved and the general flow of data between these parties,
   1 Communication capabilities of the parties (type of connection, protocols, required equipment)
   1 File-formats (ascii, xls, csv, xml) and file layout (record types, etc.)
   1 Required level of security (authentication, encryption etc.)
   1 Required feedback (logging, notifications, warnings, error reports)

*Mapping* <br /> An important part of EDI is mapping. The picture below shows a standard order entry form together with their fieldnames.<A HREF="%ATTACHURL%/edi1.gif"><img vspace="10" width="500" alt="" src="/pub/Cargooffice/EdiSpecial/edi1.gif" title="Mapping of standard orderentry form (click for enlargement)" border="0" /></A>
   * Start your mapping from your order entry form, check correct namegiving in [[TransportorderFields][Transport order fields]].
   * A mapping document like this is absolutely necessary to successfully complete an EDI project.
   * Send the overview and the mapping to us and we will make sure you receive the correct data or send correct data to the party you wish to communicate with.

*And if you don't understand any of this, send everything you've got to us and we will solve your EDI problem for you.*

<br /> -- Main.RutgerRutgers - 14 Sep 2006/ 2012-08-16
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
gif	edi1.gif	r1	manage	97.3 K	2012-08-16 - 13:26	RutgerRutgers	Edi mapping example
Topic revision: r3 - 2018-10-10 - HenkRoelofs