[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

RE: ISA16 - sub element delimiter

From: hparks@...
Date: Fri Mar 12, 2004  10:56 pm
Subject: RE: [EDI-L] ISA16 - sub element delimiter
It helps to go back to the original question. The thread seems to have been
a bit confused.

The answer is no, your customer should not put the "|" character as the
subelement separator, since neither the REF02 or REF03 elements are
composite elements. The actual results of making that change would vary by
translator, I imagine; some translators would ignore the presence of the
separator in the element because they would not look for it, some would
notice the error. The "|" is, in fact, acting as a separator but only in a
business sense. It should concern the translator no more than a comma or
period in a long block of text.

Howard Parks
1 Peter 4:10

-----Original Message-----
From: John Fiorino [mailto: Sent: Friday, March 12, 2004 2:17 PM
To: Subject: [EDI-L] ISA16 - sub element delimiter


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?

Any input would be appreciated.

John Fiorino
CompuSys Solutions
Softshare Application Systems Integrator
(514)592-7144 / (450)669-5506


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.619 / Virus Database: 398 - Release Date: 3/10/2004


[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>
Access the list online at: http://groups.yahoo.com/group/EDI-L

Yahoo! Groups Links







 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.