Yes the 816 is the most common message for what is typically called organization updates. However JCPenney sends an 864 for the same purpose.
Your second comment beckons back to the ole adage Garbage In Garbage Out. A customer's data is only as good as their commitment to keep it current. As has been referenced so eloquently in the past by some of other esteemed members, EDI is or should be a pass-through mechanism for data WITHOUT logical or ultimately making a decision about whether the underlying data is correct. On my system, I simply provide the mechanism to either report via email or do SQL update. Ken edispec ________________________________ From: Jason McMahon <[email protected]> To: Narayanan Bharadwaj <[email protected]>; edi list <[email protected]> Sent: Thu, February 3, 2011 9:05:18 PM Subject: RE: [EDI-L] customer info sync up It sounds like there is a lot of house keeping needed before any one sync's anything. I have only used the 816 in one direction. Usually the customer sends new store/DC addresses or changes to addresses that are entered into or updated by the vendor's system. Someone will have to decide what addresses, accounts etc are correct and update the rest of their system. The 816s could then be sent to all vendors to correct any inaccuracies in their systems. Sincerely, Jason McMahon 8079 Village Drive Cincinnati, OH 45242-4315 <mailto:[email protected]> [email protected] <http://gutausse.weebly.com/articles.html> http://gutausse.weebly.com/articles.html http://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:[email protected]] On Behalf Of Narayanan Bharadwaj Sent: Thursday, February 03, 2011 8:07 PM To: edi list Subject: [EDI-L] customer info sync up Hi all,one more topic in the same week:-)We are a disty and this request came from our vendor.The basic issue is that - we report the end customer information in the EDI messages (867/POS, 852/sell through) to the vendor. However, the structure/format of the end customer information is in our control and is definitely not consistent. The vendor is running some analysis and generating some reports on their end based on the end customer information.So, they are having lot of "unidentifed" records on their end which is a pain to manage. They are proposing to sync up the end customer information on both ends. Their first proposal is to use 816 message. 816 is for sync up of addresses, so we are not sure if this is the best option for us.I just want to get a feel from the group about what is the best way to go about, in this situation. Please share your opinion.Also, if you have any other out of the box alternatives, please do share. Thanks in advance for your help.Take careNB [Non-text portions of this message have been removed] [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/
