Yes it is easy to write your own translator when every 810 is the same, but EDI standards are used differently by every organization that uses them, and if you have 10 trading partners, odds are you will be handling 10 different 810 documents. But invoices are fairly easy. The ASN will be crazy because not only will different trading partners use different loops, they will use them in largely incompatible ways. That is where a mapper becomes invaluable. You can write a different map for each trading partner, and process all the documents together in one shot. Your mileage may vary, but my experience comes from the standpoint of a contract warehouse where our clients defined the EDI standards, and there were no two documents defined the same way, even if it had the same document number. Maybe some overlap in the 997's, but there were even multiple versions of that.
Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx
-----Bob Cagle <bcagle@xxxxxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Bob Cagle <bcagle@xxxxxxxxxxx>
Date: 09/08/2017 10:03AM
Subject: RE: Ownership won't agree to an upgrade
From: Jack Tucky
How many EDI transaction sets do you use? It's SO easy to write your own translator.
We currently only use 8 documents: 810, 846, 850, 855, 856, 860, 865, 997.
The software was already in place before I started, and the GUI Mapper has us spoiled. But, writing my own is something to consider.
Thanks
Bob Cagle
IT Manager
Lynk
midrange.com
