That's kind of an implementation decision. We have our 870 configured to send either a report of all open orders, or orders with cuts on them (exclusive of warehouse cuts, of course, which will only show up after an order drops to the DC for picking.) Our 870 runs at night via a scheduled job in SAP to pull the orders by whatever criteria is assigned to the particular sold-to, and IDocs are sent to the translator to ship out to the trading partner.
My opinion is that the 870 will do the job, but you may need to do some work on your ERP system in order to make that happen. I think that will be true no matter what EDI message you select. From: Thorsten Evans [mailto:[email protected]] Sent: Thursday, February 03, 2011 1:35 PM To: Hurd, Richard [SLCUS] Cc: [email protected] Subject: Re: [EDI-L] Order Status - Bulk We currently use the 870 as an event based order status. As soon as the ship from is determined, we get back an 870-IN status. As soon as the order ships, we get an 870-CC status. We are looking more for an across the board order status for every order in the system. -Thorsten ________________________________ From: "Hurd, Richard [SLCUS]" <[email protected]> To: Thorsten Evans <[email protected]> Cc: [email protected] Sent: Thu, February 3, 2011 1:05:57 PM Subject: Re: [EDI-L] Order Status - Bulk EDI order status report is an 870. We use it mostly for line cuts and the like but I believe it can be used for all sorts of statuses. It looks a lot structurally like an ASN. --- Sent from my iPhone. Replies may be delayed. On Feb 3, 2011, at 1:02 PM, "Thorsten Evans" <[email protected]> wrote: > 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] > > > > ------------------------------------ > > ... > 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 > > > > [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/
