I receive e-mails all the time offering positions for EDI work for iSeries and mainframe systems. At best EDI is a convenient front engine for translating data into a usable form without requiring customers and vendors to provide compatible flat files. Because so much money, time and resources have been spent developing programs that run on these systems programmers are at a premium. The movement away from this falls on those companies that have either abandoned these legacy systems, or never had one to begin with. Now that the cloud is becoming more popular, I believe there will be even less dependency upon EDI and much more direct interaction between companies.
One thing EDI forces all companies to enact is standardization between customers and vendors. And it forces everyone to comply with a transaction standard. Be clear about what you are ordering, how you are shipping and invoicing and save on time and labor costs, while minimizing mistakes. I hope that whatever replaces EDI maintains this compliance. Sincerely, Jason McMahon 10830 Lake Thames Apt A Cincinnati, OH 45242-3126 [email protected] <http://www.linkedin.com/pub/jason-mcmahon/11/743/51b> http://www.linkedin.com/pub/jason-mcmahon/11/743/51b _____ From: [email protected] [mailto:[email protected]] On Behalf Of Rachel Foerster & Associates Sent: Friday, November 16, 2012 12:21 PM To: 'Michael Mattias/LS'; [email protected] Subject: RE: [EDI-L] Transaction Set for Product Dimensions I don't interpret Mike's comments to be shooting the messenger at all - rather, Mike is just providing current insight into changing business processes. Rachel Foerster 847-872-8070 -----Original Message----- From: [email protected] <mailto:EDI-L%40yahoogroups.com> [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf Of Michael Mattias/LS Sent: Friday, November 16, 2012 8:12 AM To: [email protected] <mailto:EDI-L%40yahoogroups.com> Subject: Re: [EDI-L] Transaction Set for Product Dimensions >I do feel obliged to point out that it seems the world is moving away >from EDI for exchanging this type of data and instead doing it through >GDSN (1SYNC, GS1, etc.) Shooting the messenger? Michael C. Mattias Tal Systems Inc. Racine WI [email protected] <mailto:mmattias%40talsystems.com> ------------------------------------ ... 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 [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/
