Re: is edi translator software difficult to write? was: edi vendorcomplaining -- MIDRANGE-L

Subject: Re: is edi translator software difficult to write? was: edi vendorcomplaining
From: "sjl" <sjl_abc@xxxxxxxxxxx>
Date: Thu, 5 Jun 2008 12:06:16 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Steve -

If you do some basic research, you would find out that there are hundreds of
EDI documents for various types of transactions that defined by the ANSI
X.12 specifications, the EDIFACT specifications, and the AS2 specifications.
Also, there are the many different versions of each EDI document, and you
could theoretically have several different trading partners that each
require a different version of a given document.

So, what was your question again?

- sjl

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: is edi translator software difficult to write? was: edi vendorcomplaining , Steve Richter

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.