| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3012.1 | | METSYS::THOMPSON | | Fri Feb 14 1997 10:06 | 11 |
| Nicolas,
the way the code is right now :
1. If the first segment in the interchange is a UNB, then the characters must
be UNOA or UNOB
2. If the first segment is UNA then UNOA, UNOB, UNOC, ... are acceptable
as long as the agreement says so.
Mark
|
| 3012.2 | | TAKEOF::BLATTER | Nicolas Blatter @ ZUO | Fri Feb 14 1997 12:08 | 10 |
| Mark
That s what I would like but the document goes
in FAILTURE here what the log says:
ERREDIFSYNTAX(e), invalid EDIFACT Syntax Level, Syntax Identifier=
So where can I set it up that it works ?
Nicolas
|
| 3012.3 | You can't set it up. Not supported | METSYS::NELSON | David, http://samedi.reo.dec.com/ | Fri Feb 14 1997 13:38 | 14 |
| The EDIFACT Converter only supports Syntax level A
and B. Any other value will generate the ERREDIFSYNTAX
error.
I assume you want to send to your Trading Partner
interchanges that have UNOC in the UNB segment. If that
is true, then it is not currently possible. The Converter
uses the syntax level indicator to determine which type of
delimters to use when building EDIFACT messages; Level A or
Level B.
If you want to receive interchanges from your Trading
Partner that have UNOC in the UNB segment, then,
as you know, it is possible.
|
| 3012.4 | | TAKEOF::BLATTER | Nicolas Blatter @ ZUO | Fri Feb 14 1997 13:40 | 6 |
| That s not so nice ...
These will give me a lot of problems !!!
Any Idea wenn these will change
Nicolas
|
| 3012.5 | | FLYWAY::BLATTERN | | Tue Feb 18 1997 14:32 | 6 |
| David
what's about your Hints and Tips Number 36 ???
It doesn't work !!!
Nicolas
|
| 3012.6 | | FLYWAY::BLATTERN | | Tue Feb 18 1997 14:57 | 10 |
| David
I'm sorry it works but you realy have to change a segment delimiter,
as i have to use the standards ones I will ahve to try with the new
patch.
How can I do it with incomming also if I turn of the character set
validation dec/edi it is not acepting UNOC.
Nicolas
|
| 3012.7 | | SYSTEM::NELSON | David, http://samedi.reo.dec.com/ | Tue Feb 18 1997 16:19 | 6 |
|
>How can I do it with incomming also if I turn of the character set
>validation dec/edi it is not acepting UNOC.
Where did it fail? In the TTFS? Any error messages?
|
| 3012.8 | | METSYS::THOMPSON | | Tue Feb 18 1997 18:21 | 21 |
| Nicolas,
the current state of play here is:
1. For inbound transmissions
- you need the UNOC in the profile
- the first segment has to be a UNA
2. For outbound you have have non-standard separators (actually we only
key off segterm).
There is a patch such that you can set whatever characters you want
and we will generate a UNA.
Are you saying that you can't achieve as much as this?
Or perhaps you are asking for new functions such that you can use UNOC
without a UNA?
Thanks
Mark
|
| 3012.9 | What I need | FLYWAY::BLATTERN | | Wed Feb 19 1997 08:58 | 13 |
| Mark,
see also 3011.9
What my custome needs is these:
A partner is sending ORDERS with syntax UNOC and no UNA segment, my
customer would like to get end convert these data and send back an
ORDRSP also with UNOC syntax, it would be no proble to send also a UNA
segment but with standard delimiters.
Hope these help
Nicolas
|
| 3012.10 | | METSYS::THOMPSON | | Thu Feb 20 1997 11:49 | 13 |
| Nicolas,
Accepting UNOC without UNA should really be an IPMT. However I'll enter
a bug for you. If it's urgent you may want to enter an ipmt.
With the the cc patch you can send UNOC + UNA. I believe Chris Poad has
noted how to do this in that other note.
Cheers
Mark
|
| 3012.11 | UNOC support without UNA plus ISO-latin character validation | ATYISA::LEBRUN | | Mon Mar 03 1997 18:56 | 16 |
| At times we've to support DEC/EDI european projects we need the
ability to send characters in the UNOC alphabet without a UNA
generated !!! It's the case over here anyway
It's not clear in Marks'response than a cc patch (which one ?)
will correct the problem: I suppose it'll be without "character
set validation" ???
Could you tell us when:
1- Feasability and plan to support the ISO-latin UNOC alphabet
necessary to support Spanish and German users ?
2- Will it work both ways ?
|
| 3012.12 | | METSYS::POAD | http://www.digital.com/info/edi | Tue Mar 04 1997 11:25 | 7 |
| Jean-Marie,
The CC patch is the one you already know about. Patch no. 2 for V3.1A
on our Web site for the Profile Editor. Clarifies default and
non-default delimiter chars.
Chris
|
| 3012.13 | It works | TAKEOF::BLATTER | Nicolas Blatter @ ZUO | Wed Mar 05 1997 08:45 | 7 |
| Hi
with the patch it is possible to produce UNOC document with
standard UNA delimiters.
It works fine !!!
Nicolas
|