Michael Let me disagree. EDI was designed to allow companies to communicate data in a standard format using standard codes, elements, segments and transaction sets. It was designed completely independent of the method of communication between the two partners. That, in part, is why it works as well today using AS1/2/3, ftp, etc, as it did in the old days using any Async protocol or Bisync protocol including 2870 or 3780.
It is the communication method chosen, plus how EDI is implemented by the trading partners, that causes any delay, intended or not. Most Transportation companies have implemented real time EDI. Tenders have to be accepted or declined immediately and status messages must be sent out real time for example. Healthcare is the same way. Other industries as well (see www.x12.org <http://www.x12.org> and click on HSA-RTA conference for some presentation material). But many systems are batch (invoicing is a good example, where you want to audit before you transmit). Nothing wrong with batch by the way. Doug Doug Anderson (Chair, Transportation Subcommittee ANSI ASC X12) Vice President Sales Support Kleinschmidt Inc. 847-405-7457 http://www.kleinschmidt.com <http://www.kleinschmidt.com/> -----Original Message----- From: Michael Mattias/LS [mailto:[email protected]] Sent: Wednesday, December 31, 2008 8:00 AM To: [email protected] Subject: Re: [EDI-L] Time Stamp in EDI Messages >> After spending time analyzing the transmission delay reported by one >> of our business - any reason - why was time zone not considered part >> of EDI message format - am I missing anything very basic here? > > You are missing something basic here. Trasnmission of time zone info is > supported in DTM segments. (Maybe more segments, too). > > You need it in your business document, you send it. No muss, no fuss, no > bother. BTW... EDI was never designed to be a 'real time' communications venue.... so some 'delay' is not only normal, it should be EXPECTED. True, today with the existence of the Internet you can pretty much get 'real time' performance, but 'twas not ever thus. It used to be just to get two computers to exchange info in batch mode took one high priest and two altar boys plus the sacrifice of three goats and one virgin. Michael C. Mattias Tal Systems Inc. Racine WI mmatt...@talsystems <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 <*> 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/
