| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3011.1 | | METSYS::NELSON | David, http://samedi.reo.dec.com/ | Thu Feb 13 1997 13:53 | 9 |
| >3. How can I produce the UNA Segment at the beginning of
> an EDIFACT message.
In the Trading Partner Agreements editor (delimiter tab),
I believe you need to specify the delimiters you plan to
use. Don't leave the fields blank!
I believe this question was asked somewhere else in this
notesfile.
|
| 3011.2 | TPE replies | METSYS::POAD | http://www.digital.com/info/edi | Thu Feb 13 1997 18:08 | 17 |
| Nocolas,
>> 1. I tried to fill the Application Refference field
>> (UNB0026) from the UNB Segment using TPE agreement.
>> I can fill the field but noting is produced in the
>> Output.
When you go back into the TPE is the information you entered still
there? I.e. has the TPE saved it correctly?
>> 3. How can I produce the UNA Segment at the beginning of
>> an EDIFACT message.
You use the TPE agreements screen and change the delimiter characters.
This should create a UNA segment with them in.
Chris
|
| 3011.3 | must be set in the mapping | IJSAPL::DEWIJK | GJ from the Dutchlands | Thu Feb 13 1997 19:31 | 10 |
| Nicolas,
the $USERREF has to be initialized to 'nothing' -> "" (not $UNDEFINED)
I'm not sure wether it was in the initialization section:
$USERREF=""
or at another place eg runtime qualifiers.
It took me a few tries to find the right spot.
|
| 3011.4 | | TAKEOF::BLATTER | Nicolas Blatter @ ZUO | Fri Feb 14 1997 08:00 | 121 |
| Thanks for all the replay
To 1. : the information is still there.
But the intechange TPE looks strange.
Here the official struckture of the UNB Segment
Segment: UNB, Interchange Header
Function: To start, identify and specify an interchange
Ref. Repr. Name Remarks
S001 M SYNTAX IDENTIFIER
0001 a4 M Syntax identifier a3, upper case
Controlling Agency (e.g.
UNO=UN/ECE) and a1 stating
level (e.g. A) (which
together give UNOA)
0002 n1 M Syntax version number Increments 1 for each new
version. Shall be 2 to
indicate this version
___________________________________________________________________
S002 M INTERCHANGE SENDER
0004 an..35 M Sender identification Code or name as specified
in IA
0007 an..4 C Partner identification Used with sender
code qualifier identification code
0008 an..14 C Address for reverse
routing
___________________________________________________________________
S003 M INTERCHANGE RECIPIENT
0010 an..35 M Recipient Identification Code or name as
specified in IA
0007 an..4 C Partner identification Used with recipient
code qualifier identification code
0014 an..14 C Routing address If used, normally coded
sub-address for onward
routing
___________________________________________________________________
S004 M DATE/TIME OF PREPARATION
0017 n6 M Date YYMMDD
0019 n4 M Time HHMM
___________________________________________________________________
0020 an..14 M INTERCHANGE CONTROL Unique reference
REFERENCE assigned by sender
___________________________________________________________________
S005 C RECIPIENTS REFERENCE,
PASSWORD
0022 an..14 M Recipient's reference/ As specified in IA. May
password be password to
recipient's system or to
third party network
0025 an2 C Recipient's reference/ If specified in IA
password qualifier
___________________________________________________________________
0026 an..14 C APPLICATION REFERENCE Optionally message
identification if the
interchange contains
only one type of
message
___________________________________________________________________
0029 a1 C PROCESSING PRIORITY CODE Used if specified in
IA
___________________________________________________________________
0031 n1 C ACKNOWLEDGEMENT REQUEST Set = 1 if sender
requests
acknowledgement, i.e.
UNB and UNZ
segments received
and identified
___________________________________________________________________
0032 an..35 C COMMUNICATIONS AGREEMENT If used, to identify
ID type of communication
agreement controlling
the interchange,
e.g. Customs or ECE
agreement. Code or
name as specified in
IA
___________________________________________________________________
0035 n1 C TEST INDICATOR Set = 1 if the
interchange is a test.
Otherwise not used
used
================================================================
Now if you look, in the TPE we could define the DE 0022,0025,0026,
0032.
If I fill the 0032 then it should look like these:
UNB+UNOA:1+YOU:ZZ+ME:ZZ+970214:0844+0000000000110+++++COMM. AGREEM. ID.'
But you could look by your self TPE is dooing these:
UNB+UNOA:1+YOU:ZZ+ME:ZZ+970214:0854+0000000000110+COMM. AGREE. ID+'
I would say not exactly correct !!
About 2. : I will try !
About 3. : The delimiter in the TPE are automaticaly filled with the
standard separators. I would like to have one UNA with
these standard delimiters, so I do not want to change them.
Any othe idea ??
What s about 4. ???
Nicolas
|
| 3011.5 | Patch kit | METSYS::POAD | http://www.digital.com/info/edi | Fri Feb 14 1997 17:38 | 16 |
| Nicolas,
>> About 3. : The delimiter in the TPE are automaticaly filled with the
>> standard separators. I would like to have one UNA with
>> these standard delimiters, so I do not want to change them
>> Any othe idea ??
There is a patch to the TPE which should be available from our Web site
by Monday, which provides a checkbox which you can use to explicitly
have a UNOA segment created with the defaults if you wish. Full
information is in the patch.
The UNOB segment that the TPE displays may not be accurate. The real
test is to see what actually gets created.
Chris
|
| 3011.6 | | TAKEOF::BLATTER | Nicolas Blatter @ ZUO | Mon Feb 17 1997 15:15 | 9 |
| Chris
many thanks for these quick service !!
I had just a look in the web but could not find anything,
were exactlich should I look.
What s about my other points ??
Nicolas
|
| 3011.7 | Patch there now | METSYS::POAD | http://www.digital.com/info/edi | Mon Feb 17 1997 20:37 | 11 |
| Nicolas,
Sorry, the patch kit wasn't put on the Web as soon as I expected. It's
there now as Patch number 2 for V3.1A at our kits down-load site
"http://samedi.reo.dec.com/edikit.htm".
Others will have to reply to the remaining points... I don't know why
when copying a standard to a new version you loose the UNS segments,
but you can insert them again with the Table Editor.
Chris
|
| 3011.8 | | FLYWAY::BLATTERN | | Tue Feb 18 1997 15:00 | 9 |
|
GJ
your tip works I've put the $USERREF into the initialisation screen.
For what does we have the "User Reference" into the default from the
mapping table attributes ???
Nicolas
|
| 3011.9 | Not working | FLYWAY::BLATTERN | | Wed Feb 19 1997 08:54 | 36 |
| Hi
I've installed the patch, set the "Use default delimiter", cached and
tested (with UNOC in the syntax identifier, that's what I need !!)
Result:
FAILED: Document failed during conversion
In error listing:
DEC/EDI Document Error Listing
Date: Wed Feb 19 09:46:32 1997
Application ID : FACTS-OR
Partner ID : EUGSTER
External Standard : EDIF
External Version : 901
Document Type : ORDRSP1901
Test Indicator : 0
DECEDI__ERREDIFSYNTAX (e), invalid EDIFACT Syntax Level, Syntax
Identifier = UNOC
DECEDI__ERROR (e), unsuccessful completion
DECEDI__FAILED_TO_CONVERT (i), FAILED%Document failed during conversion
I hoped that I could use the standart delimiter and that it would
produce an UNA and an Interchange with UNOC but ...
Any more hints ???
Nicolas
|
| 3011.10 | Uncheck use default delimiters box | METSYS::POAD | http://www.digital.com/info/edi | Wed Feb 19 1997 17:21 | 6 |
| Nicolas,
To get a UNOA segment generated you need to uncheck the 'use default
delimiters' box.
Chris
|