There is the 270 document, but it isn't really intended to be used like that. My understanding is that the 270 is really only intended to report a negatively impacting event on the production schedule.
Once an order gets to the transportation stage, the 214 document can be sent multiple times to describe changes in status. From: [email protected] [mailto:[email protected]] On Behalf Of Thorsten Evans Sent: Thursday, February 03, 2011 12:02 PM To: [email protected] Subject: [EDI-L] Order Status - Bulk We have need to get a bulk order status report from a vendor of ours. This report will show at a minimum Order Number, Order Status (Open, Picked, Hold...etc). We need to receive this report several times throughout the day. Currently we have 20K orders that would be referenced in this report. This report should be scalable up to 100K+ orders. Does anyone do anything like this now? Do you use EDI - if so, what doc? I am most interested in how others are implementing this type of information flow and the best practices around it. -Thorsten [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> 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/
