I'm sure we've spent more than an hour discussing this. I think I've spent more than an hour deleting the emails. the 850/860 is not my area of expertise, but I'd say, like any other process, one size fits all - generally doesn't.
Leah ________________________________ From: Rob Guerriere <[email protected]> To: [email protected] Sent: Tuesday, November 29, 2011 1:59 PM Subject: [EDI-L] Re: EDI Software and handling the 860 (PO Change) business process Thank you for your replies and thoughts. Brian, please don't hold back. I mean that sincerely as I'll address a couple of your points briefly. - I'm not pandering a service here I want feedback on the 860 challenges. I do have personal interests in both EDI software and service companies. I also write in an opinionated way to help open up an exchange of other opinions. But the overall fighting drive is for supply chain efficiency. The more pervasive we can be implementing EDI technology the more we grow our value and industry. So, I'm not biting the hand that feeds me, I'm opening up dialogue for a better way to handle 20% of EDI becoming manual. Is that issue too fluffy for you Chris? Should we talk no higher than the segment level and meta data meaning behind elements? I spent a damn hour searching back through nearly 500 messages over several years on 860 questions. It only validated the questions to be asked again. My thoughts on past requests, replies here, and the need of the 860 session at the VCF conference go back to the ideas behind the Y2K era of business process networks. I believe that a managed service network today, that is already handling the 860 across multiple customers, is well positioned to take the next step of standardizing the 20% of manual order exceptions. How? It does mean reaching beyond the EDI document and taking ownership of the order to cash process. And I don't want to come across as pandering services so I won't say who, but there are EDI people working with business line directors to tackle this challenge. But the approaches that I have seen are highly specialized. I personally would like to hear more about the approaches taken, which is why I am asking here. All the best, Rob [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/
