I have sites that use both DB Tables and 'Flat Files' as sources to their maps. I guess its split down the middle 50/50.
Although 'archaic' and old 'fashioned' the Flat File approach works better IMO within an EDI environment. Especially when troubleshooting an issue. When executing a map that calls out to the database to query what needs to get sent, all you really see is the *results* of the executed map. The maps call to the database returns what it needs to run but the end-user does not 'see' within their EDI document tracking system what data was 'fed' into the map. All they see are the results. They may also get notified as to what may have gone wrong ie: Invalid value in segment XYZ." but the source data to that map is not readily available. As well, since they don't have a trace of what was used as input, they assume all is well at the DB end and they picked up all data to be sent. On the other hand, when using flat files as input to the map, the data files contain exactly what data was used to execute what map. These files (in one way or another) are usually archived or time-stamped or brought into the EDI system a site uses. When a particular map 'bombs', the data used for that map is easily and quickly available. You know exactly what was used and when. So this simplifies troubleshooting big time! Should you want to reprocess a batch or a file, a simple cut/edit/paste is all that is required and you're good to go. The DB Access approach usually requires recreating the exact data at the specific point in time in order to reprocess. Given the choice, I much prefer the 'flat file' approach. K.I.S.S. My 2 cents worth. John Fiorino EDI Integration Specialist CompuSys Solutions (450)669-5506 Mobile: (514)592-7144 _____ From: [email protected] [mailto:[email protected]] On Behalf Of Skip Sent: Friday, May 27, 2011 2:53 PM To: [email protected] Subject: [EDI-L] JD Edwards and EDI - Data Base v.s. 'Flat Files' I have had recent interest in the subject of JD Edwards EDI and use of Flat Files v.s. Data Base Tables. To me it is idiotic to use Flat Files for much of anything any longer. But it is amazing how this primitive approach in today's Data Base Systems environment continues to be used; even promoted and presented in Webinar Presentations. Amazing isn't it. Anyway, I've put together a sort of white paper on the matter. Love to hear some comments from my 'peers' <smile>! http://www.ediguy.net/documents/jde_edi.html Cheers, Skip Stein The EDI Guy! [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/
