I believe following two points also contribute towards choosing flat files over DB.
1) Performance of mapping mapping/EDI applications is always better while writing directly to files systems as compared to writing to database tables. Small EDI systems may not feel the difference but with increase in data one easily feel the performance lag. 2) Also, using flat files makes it easy to exchange the data between various systems/servers. Giving access to your database is considered a little insecure way as opposed to exchange just a few files. On Thu, Jan 27, 2011 at 11:20 PM, Ken Etter <[email protected]> wrote: > > > Actually most of the EDI translator products out there allow you to feed > and > pull data directly to/from DB tables. > > Not sure any investment would be lost by switching or moving to another EDI > > product down the line. Yes, mapping would need to be done with the new EDI > app > but I would think the existing DB structure would remain the same... > > Ken > [email protected] <edispec%40yahoo.com> > > ________________________________ > From: "Shannon, Bruce" > <[email protected]<bruce.shannon%40homehardware.ca> > > > To: Skip <[email protected] <skip%40msc-inc.net>>; > "[email protected]<EDI-L%40yahoogroups.com>" > <[email protected] <EDI-L%40yahoogroups.com>> > Sent: Thu, January 27, 2011 12:36:56 PM > Subject: RE: [EDI-L] Flat File vs XML => What about Using your data base? > > > > We've actually chosen to use Inbound Staging Tables in the Inovis TLE > product > for the 855 and 856 documents we are > currently working on. > > Outbound PO's and Inbound Invoices were developed with flat files. > > I left the choice up to our technical architects and they preferred the DB > option because of the control they can have in > the integration framework. > > Time will tell if we made the correct decision. > > The risk I identified to our folks was if we ever chose to move away from > TLE, > yes, I can hear the groans already, was that > this interface would need to be reworked as the tables and columns would > need to > be updated. Something we wouldn't need > to do in a flat file interface. They thought the work involved would be > worth > it. > > Have a great day everyone. > > Bruce Shannon > Vendor E-Commerce Coordinator > Home Hardware Stores Limited > 519-664-4997 > > ________________________________ > From: [email protected] <EDI-L%40yahoogroups.com> [mailto: > [email protected] <EDI-L%40yahoogroups.com>] On Behalf Of Skip > Sent: Thursday, January 27, 2011 10:06 AM > To: [email protected] <EDI-L%40yahoogroups.com> > 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 > > This e-mail may contain privileged, private, proprietary or confidential > information which is intended only for the intended recipient. If you are > not > the intended recipient, or the person responsible for delivering this > message to > the intended recipient, you are notified that any dissemination, > distribution or > copying of this communication is strictly prohibited. If you have received > this > communication in error, please reply with the notation "Received in Error" > in > the subject line and delete the e-mail from your computer. > > Ce courriel renferme des renseignements privilégiés, privés, exclusifs ou > confidentiels et est destiné uniquement à lusage de la personne à laquelle > il > est adressé. Sil ne vous est pas destiné ou si vous navez pas la > responsabilité de le remettre à son destinataire, sachez que toute > diffusion, > distribution ou reproduction en est strictement interdite. Si vous avez > reçu ce > courriel par erreur, veuillez en informer lauteur, en indiquant dans le > champ > «Objet :» la mention «Courriel reçu par erreur», et le supprimer > immédiatement. > > [Non-text portions of this message have been removed] > > [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: [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/
