Hi Skip,
The biggest disadvantage I have seen of using database integration directly is "support". Our EDI product supports direct database integration and some customers use it; but when there is a problem at customer end, the support staff needs to look at the customer (Live) system instead of getting a mapping kit from the customer and running it through the EDI file to identify the problem. Besides, the problem could be as a result of some bugs in the staging database triggers and procedures written to execute the SQLs which may have resulted in the problem. Hence the ownership of the problem becomes an issue. The end result is that the support cost to the customer increases. It's better in my opinion to have a text file interface (like SAP IDOCS) to the ERP/database system which is requires only one time text file loader and writer to be written. This will keep the coupling between the EDI system and ERP very loose (always a good idea wherever possible). Note - The EDI vendor will probably love to have a database integration customer as the customer becomes more captive! Hope this answers. Regards, Ajay Ajay K Sanghi Managing Director ________________________________________________________________ EDiSPHERE Software Private Limited | 215, Congress Nagar, Nagpur 440012 | India Tel: +91 712 246 3314 | Cell: +91 982 391 9760 | USA: +1 408.649.5635 (VOIP) Email: <mailto:[email protected]> [email protected] | Skype: ajayksanghi | Website: <http://www.edisphere.com/> http://www.edisphere.com From: [email protected] [mailto:[email protected]] On Behalf Of Skip Sent: Thursday, January 27, 2011 8:36 PM To: [email protected] Subject: [EDI-L] Flat File vs XML => What about Using your data base? There is a thread going on about the pro/con of using XML or flat file. What about using data base tables guys? Not like this is new science, common.... use the technology we have! I get so upset when I see flat file interfaces with so many ERP, and other systems. People take perfectly good EDI documents, map them into a 'flat file' or translate them to XML then write code interfaces to get the information/data into the data base that the application system uses. Why or why do so many folks make more work. Any decent translator marketed in the past 10 years will allow you to map directly into and out from most commercial data bases in existence today. Use the tables as they more closely mirror and structurally resemble EDI groupings. It is EASIER guys. Ok, back to work. As it is not Friday, I'll shut up. Cheers, Skip Stein [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/
