|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
ISA16 - sub element delimiter
Tom:
Nice explanation. How would you distinguish which sub-element you want
to use - in your example, how would you 'pull' only the 4321 and not the
BM?
REF*PK*1234**BM>4321~
Sincerely,
MATTHEW P. KILEY
Work: (512) 723 - 5261
-----Original Message-----
From: Tom Brandt [mailto:
Sent: Friday, March 12, 2004 2:32 PM
To: John Fiorino;
Subject: Re: [EDI-L] ISA16 - sub element delimiter
A sub-element separator separates sub-elements in a compound element.
These
are used extensively in EDIFACT, but not so much in X12. For example,
the
REF segment has for elements (funny your customer should have a problem
with the REF):
REF01 - Ref ID qualifier (element ID 128)
REF02 - Ref ID (element ID 127)
REF03 - Description (element ID 352)
REF04 - Ref ID (element ID C040)
The last element is a compound element which contains 6 subelements - 3
pairs of Ref ID Qualifiers and Ref IDs.
The element separator separates REF01, REF02, REF03 and REF04, and the
subelement separator separates the subelements in REF04. If the element
separator is "*", the subelement separator is ">", and segment
terminator
is "~", the REF can look like:
REF*PK*1234**BM>4321~
The usage of the subelement separator by your customer's trading partner
is
completely incorrect, as the REF02 is not a compound element.
At 03:16 PM 3/12/2004, John Fiorino wrote:
>Hi all,
>
>Can someone please explain what the ISA16 - SUB ELEMENT DELIMITER is
for?
>
>I got a call today from one of my customers today and they had a rather
>"animated" discussion today with one of their partners about the
purpose
>behind this segment.
>
>They (my customer) are sending a test 810 invoice out to one of their
new
>partners. They have sent the same 810 to a dozen or so other partners
and
>never had a complaint. In order to satisfy their business needs, they
send
>out multiple REF segments that basically contain a text field. It is
really
>mutually defined. The ref01 is ZZ and the ref02 contains a string that
is
>about 80 chars long that contains customs brokers data. The data is a
text
>field and for some unknown reason ("that's the way it's always been
done")
>the text contains a "|" (vertical bar) within this text. For example:
>
>REF*ZZ*this is| an example| of a string | that is sent | in the ref02
>
>The "|" serves as a kind of delimiter for the text itself - not a true
EDI
>delimiter. They do this so their partners can import these strings into
a
>spreadsheet to print. In other words the | works like a comma in a
comma
>delimited string.
>
>Now the issue that their new partner brings up is that the ISA16 should
>contain this bar | as the sub-element delimiter since according to them
it
>is used as the string delimiter within the REF02.
>
>Does this make any sense? Are they (the new partner) right in assuming
that
>the | is now the sub-element delimiter?
--
Tom Brandt
Northtech Systems, Inc.
130 S. 1st Street, Suite 220
Ann Arbor, MI 48104-1343
http://www.northtech.com/
.
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 Sponsor
ADVERTISEMENT
<http://rd.yahoo.com/SIG=12cs5s202/M=276465.4309739.5546025.1261774/D=eg
roupweb/S=1705005582:HM/EXP=1079210076/A=1854144/R=2/id=noscript/SIG=11q
sqm7r6/*http://autos.yahoo.com?refsrc=onnetwork/ads/Q4/lrec/snow>
<http://us.adserver.yahoo.com/l?M=276465.4309739.5546025.1261774/D=egrou
pweb/S=:HM/A=1854144/rand=473160513>
_____
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:
<mailto:
* Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .
[Non-text portions of this message have been removed]
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
