Indeed, this has proven to be quite a challenge with regard to the multitude of
X12-based EDI applications here at Customs and Border Protection. We have
generally adopted the use of the tilde for purposes of satisfying the 4030+
implementations. Can't wait until X12 is forced to wrestle with the 'release
character' ..... oooops, better not go there.
Bud/Customs
Pete Austin <[EMAIL PROTECTED]> wrote:
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
---------------------------------
We have the perfect Group for you. Check out the handy changes to Yahoo! Groups.
[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/
