I have to disagree with you (a bit) there. I feel that most <number> Specs I have google'd up provide a "set of possibilities, requirements and options", not really a "context". The Spec for an 850 (say) isn't going to tell me that Walmart might follow that up with an 860 to modify the specific order. Or that they might be expecting an 855 back to acknowledge the order (Oh, yes. If I knew so, I could also goole up specs for those documents. If I actually knew they existed.)
I agree with you, in general, on the 816. But, in practice (at least with my client) it costs (to them) serious money to implement an 816 map (through their service) to actually receive said doc from a Partner (no they don't communicate directly with any Partner except their warehouse). So receiving the new store addr in the 850 allows me to create the ship to map without intervention. This works in almost all cases with this Client (OK, except BBB who doesn't send new addrs. And Macy's that want to send you a StoreID and have you guess the DC.) From: [email protected] [mailto:[email protected]] On Behalf Of Jason McMahon Sent: Sunday, March 13, 2011 2:37 PM To: 'Rich Silva'; [email protected] Subject: RE: [EDI-L] Rapid, Inc. Guidelines Are there any specs or presentations out there that give "context" to a group of EDI Docs? Often the title of the EDI Doc will give a context to the use of said document. You can also Google the document number to learn more about its context. However, each trading partner gives a context to every document they trade with and that becomes the de facto use you will be interested in. For example: The 816 should be used to provide New Store Information; however, Wal-mart loves to put new store information in their 850s (Purchase Orders). Even though it makes much more sense to use the 816, the context for receiving new store information can also come in the 850. Sincerely, Jason McMahon 8079 Village Drive Cincinnati, OH 45242-4315 <mailto:[email protected] <mailto:gutausse%40cinci.rr.com> > [email protected] <mailto:gutausse%40cinci.rr.com> gutausse.weebly com/articles html gutausse.blogspot com <http://www.linkedin.com/pub/jason-mcmahon/11/743/51b> http://www.linkedin.com/pub/jason-mcmahon/11/743/51b _____ From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Rich Silva Sent: Sunday, March 13, 2011 4:51 PM To: [email protected] <mailto:EDI-L%40yahoogroups.com> Subject: RE: [EDI-L] Rapid, Inc. Guidelines Well, yea. I agree with all that. And that is why I liked these specific docs so well. One, there were almost generic. But, they also implied a context. I have attached my favorite as an example. For someone (software focused, IT Tech) new (to EDI and) to Delivery Notes and Ship Notes and under the gun to immediately understand EDI and implement it within a new ERP; these were wonderful education. Where looking at, say, a Walmart 940 spec, would tell you (almost) nothing about what a delivery note "is" or its "context" within the group of Warehouse EDI documents. That's why I liked these specific specs. and why I thought it worthwhile (even though they are NOT a specific Trading Partner of any client I have) to find their origin and to find the "complete list" if I could. So, I expand my "question". Are there any specs or presentations out there that give "context" to a group of EDI Docs. The attached "Spec" seems to at least allude to a set of documents that track Warehouse Activity. I've always wanted to find one that originated with the "Sales Order" (850) and ended with the Invoice (810). PO Ack (855), that includes changes (860), PO Change Ack (865), Shipping Schedule (862). Etc. (What is the real transaction set. and its Business Cases?) Context, context, context. The road to real education? Rich [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/
