|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: ISA16 - sub element delimiter; Extra info....
Bonjour John,
I notice that you went thru a lot of trouble not mentioning or referring to
me & I appreciated it. This is very professionnal. It was hard for me not
to reply without mentioning my own name....& I have no problem with this
anyway...
Regarding the usage of the ISA16, considering that in your customer's
documentation it is specified that the ~ would be used as the sub-element
separator and that they use the REF03 to carry may fields using the ~ as a
separator, I think it was logical to understand that they used the REF03 as
an element having sub-elements or at lease simulating it. Even if I knew it
was not standard (EDI) I have adjusted my EDI software to allow this twist
for them. Again, allow me not to share your opinion when you say "The many
members of this group simply answered the question. Your reason to change
the value of the isa16 to accommodate the REF03 element is incorrect. It is
not standard. Nor right." I'm not sure we can say it is all right or all
wrong. When the other members answered the original email, they had only
one side of the story... Based on the information contained in the
guidelines I took the appropriate actions to process the information
transmitted. Now the rules of the game have been changed in the middle of
the game. That's why I'm asking to have it back as it was.
Regarding "I agree that what is being sent in the REF03 is also not a very
'elegant' way of sending the data but that's the way they have it set up
with many other sites and have yet to have a complaint or a request to
change it." I agree that it's not elegant. Regarding complaints I have no
info to validate this and no intention to do so.
Regarding "As far as the tilde ~ that you refer to goes, they are NOT
sending a ~ as a sub-element delimiter in the REF03. They are sending a |.
From what I saw, it seems that your VAN or translator is changing the | in
the REF03 to a ~ on it's own and causing you problems" You are right. On
their documents they say they would be using a tilde and in their document
they were using the same character in the REF segment. Yes my VAN does
change these characters as per my specifications but this is not what is
causing the problem(I'm receiving thousands of transactions per year without
problems) since the VAN will change all the segment terminators,
element/sub-element separators the same way...but if your customer had
continue to use the same characters than before on the ISA16 & REF
segments...I would not be here writing all this.
An finally "As you know, they will accommodate you and change the
sub-element delimiter as you requested even though it is not right. Hope
that helps you out." I'm glad to know that they will make the change. If
they want to avoid this kind of problem in the future, they should update
their EDI guidelines and make them clearer. I think based on all the
information that I provided I'm right to ask for this change...
Have 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 17:38 PM
To: Richer, Robert;
Subject: RE: [EDI-L] ISA16 - sub element delimiter; Extra info....
Hello Robert,
First of all, as you may have noticed throughout the posts, I went thru the
trouble of NOT mentioning or referring to you personally in ANY way.
I did not know the purpose of the ISA16 element, since I've never come
across a situation where I needed to know, and that is why I posted my
question to the group.
The replies I got from the group merely confirm that what you want to use
the ISA16 segment for is incorrect according to the standards. My customer
(and no, I did not set up the mappings) contacted me to find out what the
importance and use of the ISA16 was and whether what you wanted to use it
for was justified. So I posted the question.
The many members of this group simply answered the question. Your reason to
change the value of the isa16 to accommodate the REF03 element is incorrect.
It is not standard. Nor right.
The REF03 is a string field and not a composite so it remains that the value
within the ISA16 that you ask for is not relevant. I agree that what is
being sent in the REF03 is also not a very 'elegant' way of sending the data
but that's the way they have it set up with many other sites and have yet to
have a complaint or a request to change it.
As far as the tilde ~ that you refer to goes, they are NOT sending a ~ as a
sub-element delimiter in the REF03. They are sending a |. From what I saw,
it seems that your VAN or translator is changing the | in the REF03 to a ~
on it's own and causing you problems.
As you know, they will accommodate you and change the sub-element delimiter
as you requested even though it is not right. Hope that helps you out.
Feel free to contact me off-line should you want to discuss this further.
John Fiorino
CompuSys Solutions
Softshare Application Systems Integrator
(514)592-7144 / (450)669-5506
[Non-text portions of this message have been removed]
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
