Personally, I'm a flat file kind of guy. Someone else mentioned the desirability of having the EDI subsystem and the ERP be "loosely coupled". This can ease upgrades (of either the ERP or of the EDI document version or even of the EDI system) as well as providing more flexibility should a business decision be made to replace the ERP (or the EDI subsystem).
Ken ----- Original Message ----- From: Travis Truax To: 'Becker, Adam' ; [email protected] Sent: Thursday, September 07, 2006 4:59 PM Subject: RE: [EDI-L] ERP EDI raw data import/export concerns Comment on Gentran:Server ODBC: I use it. It works - But my opinion is that it's a 'house of cards'. By that I mean you can break your map with the slightest of changes. And debugging what is going on with your map can be rough. Travis- -----Original Message----- From: Becker, Adam [mailto:[EMAIL PROTECTED] Sent: Thursday, September 07, 2006 1:03 PM To: [email protected] Subject: [EDI-L] ERP EDI raw data import/export concerns Hello all, We're preparing to make some major changes to our EDI system, and our ERP (Axapta) consultants are insisting we purchase a module (that they're writing) which will import all EDI directly into Axapta and export EDI documents, with all mapping and such taking place in the ERP. I'm basically wondering if any of you guys bring raw EDI directly into your ERP / have it generate outbound raw data, and how that works for you. I really am just having a hard time giving my stamp of approval when the time tested much more robust Gentran:Server won't cost much more and can ODBC right into Axapta's tables. Also any comments on Gentran:Server and ODBC mappings would also be much appreciated. Thanks!!! Regards, Adam Becker EDI Administrator Northern Engraving Corp. P: +1 608.269.6911 x439 F: +1 608.269.9632 http://www.norcorp.com This email message and any attachments are for the sole use of the intended recipient(s). This email and any attachments may contain confidential, privileged or otherwise protected information, including legal protection under the Health Insurance Portability and Accountability Act (HIPAA). If you are not the above named intended recipient, you are hereby notified that any use, disclosure, printing, copying, or distribution of this email or attachments is strictly prohibited and may subject you to criminal and/or civil penalties. If you have received this email in error, please immediately notify the sender by telephone or reply email and destroy this email [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 [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: 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/
