2/8/13 >My boss was challenging me whether this was within "Best practices of EDI". I >understand this is rather conceptual issue, and >question is whether it would be >hard to maintain centralized map (whenever >there is a need to change something for 1 partner, >you'd have to retest the data for all of them, I get that :)))
I've always believed anything "customer-specific" should be coded in its own module, and that anything "common to all" should be coded in one and only one module. Bottom line: No logic is ever coded in more than one place. YMMV. 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/
