I agree here. The value of an EDI package isn't necessarily sending EDI
data (especially if it's "just" FTP). The value is in mapping
capabilities, interfacing to your back-end systems, and receiving and
parsing incoming documents. How often you use these features makes a
difference.
We use an old version of Gentran, and are migrating to Extol; both run
natively on the iSeries. Our ERP vendor seamlessly integrated EDI
support from both of these packages into their product. This keeps us
from worrying about the low-level stuff (sequence numbers, segment
terminators, document formatting, etc) on a day-to-day basis.
For what it's worth, we communicate with our automotive customers using
ANX, and GEIS and TradeWeb on the supplier side. All our communications
are FTP.
Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Keith Carpenter
Sent: Thursday, July 12, 2007 00:00
To: Midrange Systems Technical Discussion
Subject: Re: EDI and Inovis from Library Data
Hi Scott,
Scott Klement wrote:
I'm finding myself REALLY interested in this thread. My company has
been using Inovis' software for years, but now we're in the process of
upgrading our system from a 270 to a 520.
The TrustedLink EDI software was around $10k when we originally
purchased it from Premenos, and we've faithfully paid for maintenance
on
the product. However, just to transfer the license from the 270 to
the
520 they want $15k!!
This is an absolutely absurd price in my mind. This 520 is only 600
CPW,
it's the smallest machine IBM makes. (As was the 270 in it's day).
They are the same software tier, but of course, Inovis doesn't care
what
the software tier is, they only care about the CPW. To me, the notion
that it costs more to transfer a license for software that processes
10-15 orders a day than it does to buy a new machine, or to buy the
original software in the first place... it just boggles the mind.
They probably get their fee most of the time as a lot of shops won't
want the hassle of changing software. You might consider keeping your
old 270 just for running Trustedlink. It could be the easiest and
cheapest solution.
Anyway, my point is -- if I can simply write the EDI data to a stream
file and FTP it, that would be AWESOME! Not only would it save me
money, but I could make the whole process much more efficient.
Can anyone give me more info about what's involved in this? You just
write the EDI formatted data to the IFS (I already know how to do
that)
and FTP it and your done? (Could it be that simple?) I assume the
VAN
requires some sort of contract?
Yes, generating EDI data can be that simple. Processing (parsing)
incoming EDI data is more work.
I'm going to guess you are using ANSI X12 850s for the orders. If you
send them, then besides correctly formatted data, you'll need to
generate unique and consecutive control#s (contained in the ISA and GS
envelopes) for each trading partner. This is how they detect duplicate
or missing data. If you receive orders, then you may be required to
return an acknowledgment (997) document to let your customer(s) know
that you've received their file (again control# driven).
Documentation for ANSI (ASC) X12 documents are available for purchase
from www.x12.org
Yes, VANs will likely require contracts. I assume you are using Inovis.
Even if you drop TrustedLink, you should be able to continue using them
for their VAN service. Other VANs to consider are Sterling Commerce and
GXS.
You can reduce or eliminate VAN fees by exchanging EDI directly with
your trading partners. Not all partners will go for this and if they
do, they may require AS2 connectivity rather than FTP.
Keith
midrange.com
