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

RE: 830: Auto vs Retail

From: "Hurd, Richard [SLCUS]" <rhurd3@...>
Date: Mon Mar 7, 2005  6:03 pm
Subject: RE: [EDI-L] 830: Auto vs Retail
> The automotive 830 is not exactly used as a purchase order, correct?
> So I should not plan to import into my ERP (Oracle) as an order?

It depends.

At Agere, where I was in EDI until they saw fit to lay me off a couple of
years ago, we used the 830 as two kinds of documents; both the forecast and
as a demand release (i.e., purchase order.) If the qualifier was a
"planning" qualifier, it was a plan; if it was "firm" it meant "this is a
PO" and we actually wrote it to a PO.

It all depends on DaimlerChrysler's business process. What does their IG
say?



[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.