Oh the horror stories I recall dealing with home grown systems. Make that control number not the exact number of digits and you will waste HOURS trying to figure out why the document won't process. A real EDI system would just never make that error so you won't be expecting it. I've never met a homegrown system that did not cause twice the work for me, the recipient. To insist on custom flat file exchange is at least a more honest representation of what will be exchanged.
My company deals with a 3pl that doesn't do EDI and they, before I started working here, coded everything custom. I shook my head and asked time and again why you would do that. Now they are going back and adding in all this acknowledgement functionality - a good hundred hours of coding plus reports, etc - for something that is automatic in EDI. They've spent 4 X the time and money doing it custom and they still don't have anything as good as real EDI. Plus now they are married to this 3pl because of all the custom code. Bad idea. Just saying...there is a reason why EDI pays and there is a good reason why you leave the parsing to the pro translators. There are plenty of new problems in the world of business to solve besides these. On Wed, Aug 27, 2008 at 12:09 PM, Susan Stecklair <[EMAIL PROTECTED]> wrote: > Hi G -- > > I'm curious how well your functional ack process is working, now that > you have the file parsing so well under control. > > Seriously, I am currently implementing a "Off the Shelf" EDI software > solution at a client site to replace their home grown EDI messages > written in PERL. And, yes, they currently are unable to send out FA's, > or perform the reconciliation. They had enough issues with the home > grown PERL that the CIO refused to implement any more messages until > they purchased a real system. The PERL consultant is gone, and the CIO > himself must troubleshoot the scripts when they have an issue. I bet > they now wish they went this route originally as all the $$'s & work by > the original consultant is a throw away. > > Years ago, one of my bosses - a major leader in EIDX -- refused to > implement anyone with a home grown EDI system, because we were burnt > spending time debugging their programs and educating them. > > I agree with Art. My 2 cents. > > Susan > > -- > > / Excellence in eCommerce Integration and Products since 1993/ > > Regards, > > Susan Stecklair, MBA > President > *Phone: * 408.996.7492 web: www.ecommerce-inc.com > <http://www.ecommerce-inc.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 <*> 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/
