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

RE: ISA16 - sub element delimiter; Extra info....

From: "Richer, Robert" <robric@...>
Date: Fri Mar 12, 2004  10:11 pm
Subject: RE: [EDI-L] ISA16 - sub element delimiter; Extra info....
Bonjour John,

I'm the customer of your customer....

Let me bring some extra information so we have both sides of the story.

If you look in their guidelines, they specify at page 1 that they will send
"~" as sub-element separator.

If you look in their guidelines at the samples of the data they are
transmitting, they decide to use the REF03 element in a non-standard way to
carry multiple type of custom data using the "~" as a "data
separator/sub-element separator". I agree that REF03 is not supposed to
contains sub-elements but since they were using that segment as it was
supporting sub-elements, I have adjusted my REF03 definition in my EDI
software to match their special way of using this segment because they were
already using it with other Trading Partners. So I build my map based on
this and it worked fine when I tested it with them. Now for a reason that I
don't know, they decide to change their sub-element separator on the ISA
segment without changing the ones in the REF segments. By doing this, my
EDI translation software is no longer recognizing the "ex-element-separator"
in the REF segment.

The only thing I asked your customer is to use the same character in the
ISA16 then the one use in the REF segment so my modifications that I made
for them can continue to work. I'm sure that you will understand that I'm
not interrested in redoing my map because of that change.

If more information are needed, please do not hesitate.....

Oups! Please allow me to tell you that I do not share your opinion from
your last email where you wrote:

From the answers I've gotten, my customer is correct in what they send
(regardless of whether they should simply strip it out to make their partner
happy).
In this case they are not sending the 80 character string in the REF04 so
what they have done is valid EDI. Their partner is wrong.



Thanks & have all a great weekend,
Robert Richer
Spécialiste EDI
EDI Specialist
IPEX Inc.
3 Place du Commerce
Île-des-Soeurs
Verdun (Québec)
H3E 1H7

Tél.: (514) 769-2200 ext.: 233
1-800-363-2620
Fax: (514) 769-0096
Email: WWW:www.ipexinc.com





-----Original Message-----
From: John Fiorino [mailto: Sent: March 12, 2004 15: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).
<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
<http://groups.yahoo.com/group/EDI-L>




Yahoo! Groups Sponsor

ADVERTISEMENT

<http://rd.yahoo.com/SIG=12c2mdk66/M=266841.4700596.5858952.1261774/D=egroup
web/S=1705005582:HM/EXP=1079209047/A=2026346/R=0/SIG=12473cbsu/*http://www.l
ifescapeinc.com/picasa/landing.php?capid=314&caId=2343> click here

<http://us.adserver.yahoo.com/l?M=266841.4700596.5858952.1261774/D=egroupweb
/S=:HM/A=2026346/rand=194184508>


_____

Yahoo! Groups Links


* To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/ <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]




 
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.