[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

RE: Internal Expectations of EDI

From: "Richer, Robert" <robric@...>
Date: Mon May 3, 2004  5:25 pm
Subject: RE: [EDI-L] Internal Expectations of EDI
Bonjour Tracy,

Ipex is fully integrated for inbound POs & outbound Invoices. Having said
that, Internal Sales Reps still have to edit EDI POs when the customer send
the wrong prices, order from a new branch (that we did know of), or products
without a valid UPC, and/or Buyer Code and/or Vendor code. Sales Reps still
have to read messages & notes from customers..because customers expect that
someone will read them. EDI points out the errors but don't make the
corrections. EDI can do a big part of the job but not all....otherwise Order
admin & Customer Services dept would be no longer necessary....They are
there to make sure that customers will be well served & that the right
product will be shipped to them. You can't leave these responsibilities
uniquely to a computer....not in our business anyway.

I hope this help,

Have a nice Monday afternoon,

Robert Richer
Spécialiste EDI
EDI Specialist
IPEX Inc.
3 Place du Commerce
Île-des-Soeurs
Verdun (Québec)
H3E 1H7

Tél.: (514) 769-2200 ext.: 233
1-800-363-2620
Fax: (514) 769-0096
Email: WWW:www.ipexinc.com


-----Original Message-----
From: Tracy [mailto: Sent: May 3, 2004 12:20 PM
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
<http://groups.yahoo.com/group/EDI-L>




_____

Yahoo! Groups Links


* To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/ <http://groups.yahoo.com/group/EDI-L/>


* To unsubscribe from this group, send an email to:
<mailto:

* Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .




[Non-text portions of this message have been removed]




 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.