Randy, Depends on what you mean by "EDI Compliant." From your example, I'll assume, at least that you're actually meaning "X12 Compliant."
I'm also not sure whether you're concerned with the idea of 2 interchanges or 20 spaces between the interchanges. In either case, I don't think there is anything in the X12 standard to define that type of "compliance." The idea of sending interchanges in files versus simply sending a stream of records (a la bisync) is something that the X12 standard doesn't really care about. In general, transmission techniques are beyond the scope of X12 standards. I don't think the 20 spaces is justification for calling your sample file "NOT X12 (EDI) Compliant." There is a general understanding that each segment in a given interchange ends with a separator character and that each segment follows the preceding with no intervening whitespace, however I would argue that the first interchange ended with the terminator character of the first IEA segment and that the second interchange began 20 characters later. The whitespaces between are kind of a no-mans-land, again, not addressed within the X12 standard. About the only thing we can say is that more flexible software would handle it with a minimum of hiccups, whereas other software would error out for supposed, but undefined, non-compliance. My own philosophy with regard to EDI processing has always been to be as fault tolerant of inbound EDI data and as close to the standards specifications as possible for outbound EDI data. Best regards, Bill Chessman Inovis(tm) -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of randy_gentran Sent: Monday, October 27, 2008 4:20 PM To: [email protected] Subject: [EDI-L] EDI complaint or not? One customer sent two interchanges in one file, there are about 20 spaces between those two interchanges. Can we say that transmission was NOT EDI Compliant? Ex: ISA*00*...000000107*0*P*>~....IEA*1*000000107~ (20 spaces) ISA*00*...000000108*0*P*>~....IEA*1*000000108~ see the spaces between the interchanges, can we say that is NOT EDI Compliant? ------------------------------------ ... 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/
