I was the work group lead at X12 where the 816 was developed in the Purchasing Subcommittee when it still existed at X12 - with a focus on organizations and their relationships to larger entities, etc. These business processes are now under the purview of the X12M Supply Chain Subcommittee.
The purpose and scope of the 816 is quite clear: "This transaction set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multi-hospital system, a chain of retail stores, a holding company, etc. "This transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases." While you may be able to jury-rig the 816 to send this product information it would clearly be out of scope for the 816. I personally believe that bastardizing a specific standard transaction set to carry data that can be carried in another transaction set for that purpose is not a good idea - and once you do that you no longer have a standard. Rachel Foerster 847-872-8070 From: [email protected] [mailto:[email protected]] On Behalf Of Michael Mattias/LS Sent: Monday, October 03, 2011 10:01 AM To: EDI-L Subject: Re: [EDI-L] 816-Org Relationship >Is there a way to capture the information about the type of items sold at a >given location via EDI 816 message?? >We are planning to implement EDI 816 to capture the store location address >info and we are pondering over if we can get the additional info like "this >store sells >only tools" vs "this store sells both tools and >components"...kind of info from the distributors. >Is this practically possible? If so, what segments would be used for this >purpose?? >Can you please share your thoughts around this?? As mentioned by Mr. Brown, with the REF (and other) segments supported in the 816 document and a little imagination, you and your trading partners can exchange all kinds of information. However, this sounds like the kind of info you should have developed over the years with your distibutors and already have on file "somewhere" within your ERP system. That said, either the '852 Product Activity' or '867 Product Resale and Transfer Report" documents would seem a better choice than the '816 Organizational Relationships' document if you would like your distrbutors to report actual sales of your products. As you said yourself, your purpose in trading the '816' is obtain "address info"... a virtually 'textbook' case for the 816. I've always found trying to fit square pegs ("product type sold") into round holes ("address info") is just asking for long-term problems. (Besides... if not defined by your distribution contracts - product types sold is "currently"... but wouldn't you like ALL your distributors to sell even more of ALL your products?) Michael C. Mattias Tal Systems Inc. Racine WI [email protected] <mailto:mmattias%40talsystems.com> [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/
