Ilia, Service hubs represent the 800lb gorilla, not the supplier who has 10-20-50 800 lb gorillas as customers.
But, what is comes down to is does it work for your industry and your employer/customer. Leah ________________________________ From: shluft <[email protected]> To: [email protected] Sent: Friday, February 8, 2013 2:33 PM Subject: [EDI-L] Re: [TECH] 1 map vs many partner based maps (Best EDI Practice?) Hi again. I'd like to thank everyone who responded and shared opinions. Our transactions are fairly simple comparing to retail (in or out). I am confident that most of the partner maps could be converted into a merged template where any custom parameters are driven by external codelists (tables). Besides, if I put in time and effort into conversion now, it would save me a bundle when I need to remap all of our transactions o SAP interface. I've already mapped few newer partners using this concept as a POC, in both unbound and outbound direction, and they've worked so good - I've moved the maps into production. The immediate result is obvious - I no longer have to submit Map Change request for maps to Change Committee, since most of my changes for these partners are "data changes, not a code changes" (wink-wink). Again, thanks for a wonderful feedback. I specially like the statement that single map concept becomes a trend for a service hubs. That's a solid argument right there. Thanks, and have a great weekend, with fries or without. I myself just had a chili fries from Wendy's and it was delish! Take care, Ilia. --- In [email protected], "shluft" wrote: > > Hi. > > In preparation to our SAP migration I've offered my boss to migrate our > numerous customized and mostly simple per-partner maps into centralized map > driven by partner-based parameters configured within the EDI system (Sterling > Integrator). > > 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 :))) > > Never the less, if EDI is not ran by consulting shop, and the long term goal > is reducing maintenance and cost - would this approach fall within "Best > practices of EDI" and would there be any documentation out there to support > it, other then exchange of opinions of EDI gurus on this mailing list? > > Yeah, and I wana fries with that! > > Happy Friday! > > :)))) > > Thanks! > > Ilia. > [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/
