> However in many cases the complexity and nuances of the EDI system are a > reflection of the complexity and nuances of the business process it > supports, so a change of EDI system may still leave you dependent on > someone who understands how it all fits together.
I cannot sign up for this. The reason you end up with all kinds of hard-coded exceptions and winding roads and twisting turns is because the system was not designed to support "today's buiness conditions." If it had been so designed, adding new partners, documents, processing rules etc would be a ten-minute update to some configuration table. That is, starting over *using today's business conditions* as the basis for the design offers long-term maintenance benefits going forward. Not to mention ... additional efficiencies gained by NOT performing some processing step, the business conditions it was designed to support having been obsoleted six years ago. (Oh, come on. I *know* you have found processes where NOBODY knows "WHY THE HECK DO WE DO THAT?" We ALL have encountered these!) Michael C. Mattias Tal Systems Inc. Racine WI [email protected] ------------------------------------ ... 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/
