We only have two customers with whom we have to do EDI, but there are typically anywhere from a few dozen to a couple of hundred transactions. I don't work with it too much, but I know that my boss spends, maybe, 10 minutes per day While all of the original transactions reside on our System i, he wrote an Access process that sucks that stuff up and then pushes it to the EDI format.
So the EDI function itself resides on a PC. The package is EDI Complete Professional from One EDI Source (or so he alleges). He couldn't remember off the top of his head how much it costs, though we do have a support contract that is based upon number of hours.
I don't recall him having any significant problems with the package itself (the PC sits just outside of my office so I probably would have heard him scream, which he does when things go bump). Our significant concern is timing between us and one of the customers; we have to get the transactions out each day so that they can be received and processed by their computer before the next day's deliveries. We do have problems with the data, which he edits before sending to the EDI system, on occasion when something invalid, like a missing customer SKU, slips through my (normally) immaculate edits during order entry.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, July 23, 2008 9:10 AM
To: Midrange Systems Technical Discussion
Subject: RE: EDI AS2; ( iNovis BizManager) compared to (nuBridges, formerlyTrailblazer)
It's been a decade or so since I was the EDI support person here at Dekko.
Back then, machines were much smaller. Just trying to show a little
perspective. Anyway, we had to start running the purge in EDI on a
regular basis instead of "as needed". Turns out, we didn't have enough
disk space to do a RGZPFM on the one EDI file. Also, we found out the EDI
is extremely string intensive. Which, on ancient hardware, just beat the
snot out of it.
In summary, if you are even remotely planning on upgrading your hardware
and operating system, do so before the installation of the EDI package.
Thus avoiding the "ramming" that you are likely to get from the upgrade
charge. Why buy it twice in the same year?
We have one programmer/analyst who is pretty much full time on EDI
integration with our trading partners. He has one other person that
spends a goodly portion of his time dedicated to the EDI cause also.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
<elehti@xxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/23/2008 09:55 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
<midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: EDI AS2; ( iNovis BizManager) compared to (nuBridges,
formerlyTrailblazer)
We finally realize that we should focus on making and selling wrought
iron and ornamental fence instead of trying to build EDI (electronic
data interchange) systems. (www.montagefence.com
www.ameristarfence.com
The reason why we are moving our EDI X-12 translator and EDI/AS2 off the
PC is because we have a poorly-designed EDI system that does not scale
to our needs. It has limitations and constraints and no one is
available to do tech support and enhance the system.
It takes too much time each day to do EDI. Although we have only four
trading partners and process just 100 documents daily, Our employee
spends about an hour a day performing the EDI tasks because our custom
EDI package requires so much manual intervention at every step in the
process. This is way, way too much time to spend on EDI.
And to top it off, we cannot add a fifth trading partner unless we find
a C++ programmer to rewrite our EDI software (Administration Panel,
etc.) The original C++ consultant found a job elsewhere and does not
support her software anymore.
.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
