Whups. Bad info alert: Alice, you said ISA11. I read ISA16, the 'Component Element Separator'. My apologies.
In CURRENT versions ISA11 is the 'Interchange Control Standard Identifier', and should be set to "U" for the "US EDI Community of ASC, X12, TDCC, and UCS) The ISA16 is the "Component Element Separator" and the guide states, "....this value must be different than the data element separator and the segment terminator" ================ Now, in version 4030 the following is true: The X12 standards were modified to allow for repeating data elements. When the repeating data element construct is used in a segment, these repeating data elements must be delimited by a repeating data element separator character, very similar to the component element separator, and also the data element separator. Since each of these three constructs are different, each must be delimited by a different separator character. The data element separator character is specified in the first character position following the string ISA in the ISA control segment. The component element separator is specified in ISA16-I15 data element. As a result of adding the repeating data element to the X12 standards, it became necessary to be able to specify the repeating data element separator character in the ISA segment as well. In order to minimize the impact to the currently installed base of X12 standards users and since ISA11-I10 Interchange Control Standards Identifer had long since fallen into non-use, the ISA11 data element was replaced with I65 Repeating Separator data element so that this third type of element separator character could be specified in the ISA control segment. This modification to the X12.5 Interchange Control Standard and the ISA segment is reflected in the newer version of the ISA. So, in simple terms, the X12 standards committee replaced an un-used data element in the ISA segment, ISA11-I10 with another new data element the the ISA11 position, I65. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Pete Austin Sent: Friday, November 03, 2006 3:26 PM To: Alice Raia; [email protected] Subject: RE: [EDI-L] ISA11 in v4030 Forward - "Repetition Separator" Alice, The ISA11 is like the 4th character in the ISA. The I/G's use the term 'delimiter' and 'separater' interchangeably. None of the following may be permitted to be in the data. Data element delimiter / separater Segment delimiter / separator Sub-element (repetition) delimiter / separator It does not matter if you are not using repeating fields in the X12 data itself. Once the character has been declared in the ISA, it is prohibited from appearing in the data. Your received X12 is violating X12 standards. Hope all is well, Pete -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alice Raia Sent: Friday, November 03, 2006 3:05 PM To: [email protected] Subject: [EDI-L] ISA11 in v4030 Forward - "Repitition Separator" All - I need a sanity check on the ISA11 in version 4030 forward. This element is defined as the "repetition separator": "The repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator." The way I read the above, since this field is defined as a DELIMITER, it should never be set to a value that may actually occur in the EDI data. Is this how others understand this element ? My translator is taking an inbound 850/4030 with a "U" defined in the ISA11 and removing all instances of "U" in the EDI data when it parses the EDI. This is causing major problems in that our maps check for PO1 qualifiers of "UP" and "UK" and make decisions based on those values. Post parsing, those values are simply "P" and "K". Any feedback would be greatly appreciated. Thanks, Alice Raia ... 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 ... 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 ... 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/
