I
think that you are going to find that most companies have "their own"
approach"
to the business process that they have added an EDI process to.
I
know that this is not what you want to here, but it's reality. This is what
makes
the EDI process more complex then your average bear.
The
reason that most information on EDI is generic is because it is a guide not a
mandate.
How one may implement getting information out of the application is up to
the
originator. There is no mandate that the information be provided
by
programs written in COBOL or JAVA for that fact or that the program provide a
capability
or
some others. The collection of business rules is the sum total of your
organization's
ability
to communicate with the trading partner base electronically. The catch is that
this
continues
to change as new partners are acquired and dealt with. Each of us in the role
of a
coordinator
evaluates each new trading partner from the standpoint of what other
capabilities
will
be required to effectively communicate with that partner as well as to continue
with the
rest
of the installed or production base. In some instances, the capabilities
exist, in others,
they
must be built. As each new capability is added, the dynamics of what or who
impacts the
EDI
process changes. As more partners are brought into the process, the capability
of the programs
providing
information for the translator become more robust. They have most all the
capabilities
built
into them. I refer to this as the smoothing effect.
My
recommendation to you is to review your own operations procedures and determine
what
information is extracted from it to report out via EDI. This way you will have
a
fair idea of the information you are looking for. You should not be surprised
that no
two
businesses do everything exactly the same way. They have like processes, but
the
fine
detail and nut and bolts of it are usually unique to that company. We like to
think
that these are competitive advantages, metaphor intended.
Regards,
Mark
-----Original
Message-----
From:
Brian Richardson [mailto:[EMAIL PROTECTED]]
Sent:
Wednesday, May 23, 2001 10:17 AM
To:
[EMAIL PROTECTED]
Subject:
EDI Business Process - Process Flows Wanted
I've
been lurking on the list for awhile, and in light of the recent Dual
997
discussions,
and
Mr./Ms. Srivastava's recently posted question, I would like to
request
pointers
to
'real-world' business process diagrams, flows etc that define the
EDI
business
rules/processes
in a general sense (not some company's specific
approach).
I've been interested in finding some good info along these lines
for
quite
some
time now so that I an offer it as intro reading material to some of
our
news hires, as well as client's unfamiliar with some of the business
processes
involved (or who don't realize how many of their existing business
processes
might
be a factor in the EDI process). I'm looking for something that's a
bit
more detailed than
the
general high-level intro material one typically finds - something
that
illustrates
some of the concepts/issues that folks have been discussing
recently.
Thanks
in advance.
Brian
Richardson
Highlander
Technologies, Inc.
=======================================================================
To
contact the list owner: mailto:[EMAIL PROTECTED]
Archives
at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
- EDI Business Process - Process Flows Wanted Brian Richardson
- Mark Kusiak
Reply via email to