"because most EDI document requirements vary dramatically between customers/suppliers, it is necessary to have a different flat file program format for each and every one"
Could you please clarify something? A different flat file program format for each and every one....what? Each transaction set? Each customer? Each transaction set and customer? --- In [email protected], "Skip" <skip@...> wrote: > > 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! > ------------------------------------ ... 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/
