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

Re: Internal Expectations of EDI

From: "Dave Taylor" <sysmark@...>
Date: Mon May 3, 2004  6:16 pm
Subject: Re: [EDI-L] Internal Expectations of EDI
Tracy,

Your question should be "How integrated is your EDI translator into your
business rules" that reside in your order processing system?

Your order processing system already has your company's business rules
integrated into it.

Maintaining and updating these business rules is an ongoing job of the IT
department.

Replicating these business rules in your EDI translator is an expensive and
time-consuming duplication of effort if your translator is running on the
same computer as your order processing system and is close to impossible if
it not.

How is your EDI translator, running on a separate computer, going to check
quantities available or the prices of products for each customer, or check
each customer's available credit and put the order on credit hold if the
order exceeds the available credit, etc. etc., while processing the purchase
order?

If your EDI translator is running on the same computer as your order
processing system, then it can be integrated into your order processing
system by converting each EDI purchase order to a sales order using the same
business rules that are applied when a sales order is entered manually.

The great myth perpetuated by the translator industry is that your EDI
translator can become a stand-alone order processing system and data
processing department and eliminate manual intervention in order processing
without being tightly integrated with your product database, your customer
database and, in the case of a manufacturer, your production database.

Even if your EDI translator is running on the same computer as and tightly
integrated with your order processing system, your order processing
department must expect to handle orders that error out due to inadequate
quantities of product available to fill the order, pricing inaccuracies,
credit issues, etc.

Hope this helps frame the question.

Rgds,

Dave Taylor
Sysmark Information Systems, Inc.
49 Aspen Way
Rolling Hills Estates, CA 90274
800-SYSMARK (800-797-6275)
(O) 310-544-1974
(F) 310-377-3550
www.sysmarkinfo.com


----- Original Message -----
From: "Tracy" < To: < Sent: Monday, May 03, 2004 9:20 AM
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
>
>
>
>
>




 
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.