|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: Internal Expectations of EDI
Tracy,
It is unrealistic for EDI to correct errors on incoming documents. In fact
in UCC standards manuals, there was verbiage to the effect that incoming
data must not be modified by EDI.
The application's import process we use in our product sales system checks
product codes, prices, locations, etc - and, based on business rules, either
rejects or flags purchase orders with problems. We run frequent audit
reports to alert our customer service representatives when problems are
detected with inbound POs. CSRs and EDI staff work with our trading
partners to get the POs into our system and to iron out these problems.
Also, we are working with our Marketing and Product Supply people to make
sure the communications going out to customers are unambiguous as to price
and product code.
Maintaining good relations with your company's customer service, accounts
receivable, accounts payable, etc. teams is an important aspect of our jobs.
I suggest you prioritize communicating effectively, developing mutual
understanding and respect with people in these groups. Without it, your
life and your team's effectiveness will suffer.
Good luck,
Art Douglas
Manager, eCommerce Systems
PaperPak
San Dimas, CA
909-971-5025
"Truth never damages a cause that is just." - Mohandas K. Gandhi
-----Original Message-----
From: Tracy [mailto:
Sent: Monday, May 03, 2004 9:20 AM
To:
Subject: [EDI-L] Internal Expectations of EDI
Hello all,
I have noticed that internally in my company (specifically in the
Order Admin or Customer Service department), there is sometimes
animosity/resentment/hatred of EDI. I finally figured out it's
because their expectation is that EDI orders should come in, go into
our system, and process without anyone ever seeing them, hearing
about them, or touching them. In this and other companies where I've
done EDI, EDI's expectation is that while we'll make things as easy
as possible for Order Admin, they will still have to do some manual
intervention--fixing terms, fixing pricing, fixing customer sku #'s.
They want EDI to check data against all business rules, but I am
thinking that checking for all business rules would be prohibitive
for EDI.
I am curious about industry-wide practices. How integrated are your
business rules into your EDI translator?
Thank you for your input!
Tracy
.
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
