I can't speak specifically about Axapta, but generally .... Keep the EDI work (mapping, translating, maybe communications) in the EDI software. Use flat files to import/export with your ERP. Use your ERP's import/export to manage flat-files or roll a quick program in your language of choice. Do not use any ODBC in EDI s/w to communicate with ERP. Advantages? Can change EDI or ERP s/w easily (future-proof, including SOA). No reliance on all systems being available to perform a single function. Easy auditing. Easy maintenance - everything is simple and where it should be. Easy mapping - no convoluted SQL logic embedded in EDI s/w. Geographic independence. -Paul www.icefan.ca
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Becker, Adam Sent: Thursday, September 07, 2006 2: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. <http://www.norcorp.com> 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] [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/
