"The House of Mouse" (HoM) has always been a bit odd when it comes to doing things.... They have totally disparate systems doing the same things for different departments within a single location....
I've got a pal that's been with Disney for 25+ years - having started off in "the" park (Disneyland) and having moved through retail locations - all at the Disneyland locale i.e. Downtown Disney - and then into the corporate world.... For his group(cast services), he does some purchasing and uses... oh, I don't recall the system.... Yet the retail stores group within the park use Island Pacific for their merchandising and purchasing systems.... So, while he may be buying items for his department's use (say, pins or pens or some other trinket), the SAME EXACT ITEMS are also being purchased through a different system from the same vendors.... Disney has not been one of the better companies at managing IT.... They used to have "in-house" help desk and support for their internal users.... Then it was outsourced to some company in Central California. One of the drawbacks is that Disney has "Disneyfied" the names of their applications - HR uses, say "the Donald Duck system", accounting uses "The Minnie Mouse System", purchasing uses "goofy", legal uses "pluto" and so on.... none of the users actually know that the product they're using is called SAP or Island Pacific or Oracle or Kronos or ...... Creates just a bit of a headache for the help desk company that now has to hear "Hi, this is Walt from Disneyland and I'm having problems with My Goofy system" or something.... So it comes as NO surprise that the HoM would be doing something that is viewed as easier for them - and, obviously, cost saving - but yet creates headaches and problems outside the HoM... It makes perfect sense that they'd be looking to change an existing EDI systems in a way that may be confusing and more difficult for others to use.... One other thing... at a user's conference last year, I was talking to somebody from the HoM and she had said that they were not using ASNs (at that time, anyway) when it came to the products being ordered. So maybe this is a change for the better from them - baby Huey steps forward, as it were.... Oh, wait... baby Huey wasn't Disney.... was he? Craig Dunham EDI Coordinator Big 5 Sporting Goods --- In [email protected], Brian Lehrhoff <[EMAIL PROTECTED]> wrote: > > my experience - when we finally got hooked up - is that disney has no implementation > guides. we got a batch of neutered documents, and i had to use EDISIM to reverse > engineer an IG to do the maps. it was fun, but it was annoying. this was a few > years ago, i can't tell you if it's changed. > > one more thing - disney is one of the few implementations that i've seen where the GS is actually > used. the ISA is the mailbox and postoffice, and the GS is routing within the organization. i can't > imagine what their van bill is (was). > > Brian Lehrhoff, EA ([EMAIL PROTECTED]) > Messaging Consultant 201-913-4506 > Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com > Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html ... 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/
