Not to beat a dead horse, but I had to make one comment here, because I've heard this refrain before;
> First off, ONE SHOULD NOT HAVE TO âREADâ the electronic > message except during the initial implementation and > troubleshooting. If you have to worry about reading the raw > transactio, there are serious problems. Bull. How many of us go 'under the covers' (using grep and awk on the unix platforms, or TSO on a mainframe platform) to get some data from an electronic message? I would wager that it's more than you think. Case in point: I have a trading partner who rejected an invoice because of an invoice match issue on their end. The interchange involved contained 100 invoices to them, 99 of which were accepted. They have fixed the data issue and asked me to resubmit the one invoice. The easiest way for me to do it, bar none, is to simply go into the archived data store for the transmittal period, pull up the interchange, and take the one EDI invoice out and send it on its way. We can't regenerate it because there was nothing wrong with it, and even if I stamped my dainty little foot and asked for the regeneration, how wise is it to involve more than just me in what is arguably a 3 minute process **if I have access to the raw data?** Sorry, but that dog don't hunt. Of those 10 hours I spent in raw EDI data this week, less than 1 of them were "serious problems" or "troubleshooting". The rest were just "cost of doing business." I guess I've said enough about this. :) [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> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> 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/
