× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2008

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

On Thu, Jun 5, 2008 at 1:06 PM, sjl <sjl_abc@xxxxxxxxxxx> wrote:

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?

what is the difficulty in switching from one edi package to another?
presumably, they all map from and to these edi documents and
transactions. Are there EDI packages written in Java which can be
dropped on an i system and run as is?

basically, why cant customers remove Innovis and replace it with
another package that handles the same EDI specifications?

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.