Both are pretty open. My recommendation is find out what segments/elements/fields your retailer is attracted to in the 879 and why, then find its counterpart solution in the 832. Propose your solution to your retailer citing common usage.
Do what it takes to keep them happy while maintaining minimal change diversity (process variation) in your organization (to keep overhead costs down). Shan Shan Harter Systrends USA. Vice President - Project Management Tempe Arizona, 85284 ph: 480-756-6777 Ext 205, fax: 480-756-9755, cell: 602-821-2951 alt: 480-626-7726 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jayne Gillette Sent: Friday, September 22, 2006 8:09 AM To: [email protected] Subject: [EDI-L] 832 vs. 879 for pricing updates We are doing some work for a non-grocery retailer who is implementing the inbound 832 directly with some select trading partners for item setup and item maintenance (as opposed to using a third-party catalog service). The retailer has said they want to use the 879 instead of the 832 for inbound pricing updates, as they feel the 879 provides more flexibility for communicating price changes. It's early in the project so we are just now beginning our in-depth research and analysis on this, but my initial thought was it would be best to implement a single transaction set if possible (the 832), as long as the 832 can meet the business need for inbound pricing updates. I'm also seeing some information which leads me to believe the 879 is to be used only in conjunction with the 888 Item Maintenance transaction (grocery transactions?), so are the 879 and 832 never used together? If anyone has any information regarding how others, especially in the retail industry, handle the transmission of price changes to update the price information originally transmitted via 832, I would appreciate it. Thanks in advance for your feedback! Jayne ... 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 ... 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: mailto:[EMAIL PROTECTED] mailto:[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/
