Depending on the ERP's design some databases contain the actual restraints so when you try to insert the row it will reject you.
I like the concept of writting to staging tables, and then run your load program enforcing your business logic as needed. KenCox(EDI) wrote: > Another pitfall is that writing directly to the database may bypass > application edits allowing bad or incomplete data into the system. For > example, in SAP you wouldn't write external data directly to the > underlying Oracle database tables, you would use the SAP function > modules which share the same edits as someone entering data by > keyboard into the system. > > Ken > > ----- Original Message ----- > From: Tyrone Lumley > To: Travis Truax ; [email protected] <mailto:EDI-L%40yahoogroups.com> > Sent: Thursday, September 07, 2006 8:45 PM > Subject: RE: [EDI-L] ERP EDI raw data import/export concerns > > I use ODBC all the time, the only problems I've had with ODBC are: > > 1. When using FoxPro, ODBC doesn't recognize deleted records in the > linked table.(Foz pro has a mark for deletion tag ODBC doesn't > recognize). You first have to "pack" the FoxPro table. > > 2. If you've forgot to set a primary key in the back end database (SQL > Server, for example) and have duplicate records, ODBC doen't like it. > You may not ne able to delete or change records from the ODBC table. > > I guess the appropriate way of doing things (using VB or VBA) would to > be to declare and initialize a connection object, and use it's > properties and methods to add/remove/update your data. I've done this > also. It takes a second to establish the connection object, but it's a > little faster afterwards. > > Travis Truax <[EMAIL PROTECTED] > <mailto:travis.truax%40hannascandles.com>> wrote: > In our situation, the accounting (not really ERP) system's own integration > functionality is 100% worse than any problems ODBC has to offer. Plus > there's a whole other pile of manual steps to accomplish something > that odbc > does in seconds. > > Travis- > > -----Original Message----- > From: Paul McTeigue [mailto:[EMAIL PROTECTED] > <mailto:paul_mcteigue%40msn.com>] > Sent: Thursday, September 07, 2006 5:38 PM > To: [email protected] <mailto:EDI-L%40yahoogroups.com> > Subject: RE: [EDI-L] ERP EDI raw data import/export concerns > > < Do not use any ODBC in EDI s/w to communicate with ERP.> > > <<I would not go that far. I've used ODBC connections to ERP systems > during > both inbound and outbound EDI mapping and I like it a lot. > Different strokes for different folks.>> > > As soon as you use ODBC, you have the following potential problems: > - ERP is down. > - Database page is locked for an update. > - User, password changes. > - Permissions issues. > - Convoluted SQL syntax shoe-horned into EDI software reducing > maintainability, which is the holy grail of any s/w system. > > If there is an ODBC problem, and it will happen, does your EDI system > gracefully handle it, without expert intervention? > > -Paul > www.icefan.ca > > -----Original Message----- > From: [email protected] <mailto:EDI-L%40yahoogroups.com> > [mailto:[email protected] <mailto:EDI-L%40yahoogroups.com>] On > Behalf Of > Michael Mattias > Sent: Thursday, September 07, 2006 6:05 PM > To: [email protected] <mailto:EDI-L%40yahoogroups.com> > Subject: Re: [EDI-L] ERP EDI raw data import/export concerns > > > I can't speak specifically about Axapta, but generally .... > > > > 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. > > > Advantages? > > Can change EDI or ERP s/w easily (future-proof, including SOA). > > Agreed 100%, if ERP system changes and you are writing directly to it, you > have to change the EDI side, which is usually the harder > side to maintain. If you use a "common" flat file or flat-like interface, > the only time you have to change the EDI side is when the > EDI changes. > > But for... > > Do not use any ODBC in EDI s/w to communicate with ERP. > > I would not go that far. I've used ODBC connections to ERP systems during > both inbound and outbound EDI mapping and I like it a lot. > Different strokes for different folks. > > Michael C. Mattias > Tal Systems Inc. > Racine WI > [EMAIL PROTECTED] <mailto:mmattias%40talsystems.com> .com > > [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 > > --------------------------------- > Stay in the know. Pulse on the new Yahoo.com. Check it out. > > [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: 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/
