I can't speak to the automotive usage, but in truck manufacturing the 830 data can be split into three logical buckets: Confirmed orders <-- build it and ship it Planned orders <-- you are authorized to acquire required materials but not to build it or ship it Forecast requirements <-- just what it says... My approach has been to build a database which acts as a filter. The entire 830 is loaded into tables, then queries can be used to pull out the different logical buckets of information for passing to the appropriate application. >> 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? Bill Laidley ChangeTech Resources Voice: (604) 628-7121 Cell: (604) 723-7871 Fax: (604) 628-0491 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.6.2 - Release Date: 04/03/2005 . 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 <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
