ISO 9735-10:2002
(Main)Electronic data interchange for administration, commerce and transport (EDIFACT) - Application level syntax rules (Syntax version number: 4, Syntax release number: 1) - Part 10: Syntax service directories
Electronic data interchange for administration, commerce and transport (EDIFACT) - Application level syntax rules (Syntax version number: 4, Syntax release number: 1) - Part 10: Syntax service directories
This part of ISO 9735 specifies the syntax service directories of all parts of the ISO 9735 series.
Échange de données informatisé pour l'administration, le commerce et le transport (EDIFACT) — Règles de syntaxe au niveau de l'application (numéro de version de syntaxe: 4, numéro d'édition de syntaxe: 1) — Partie 10: Annuaires de syntaxe
Elektronska menjava podatkov (-računalniška-) v administraciji (upravi), trgovini in transportu (prevozništvu) EDIFACT - Pravila sintakse za uporabniški nivo (izvedbena oblika sintakse: 4, zaporedna št. izdaje 1) Deseti del: sintaksa servisnih direktorijev (skladnja servisnih poddirektorijev)
General Information
Relations
Frequently Asked Questions
ISO 9735-10:2002 is a standard published by the International Organization for Standardization (ISO). Its full title is "Electronic data interchange for administration, commerce and transport (EDIFACT) - Application level syntax rules (Syntax version number: 4, Syntax release number: 1) - Part 10: Syntax service directories". This standard covers: This part of ISO 9735 specifies the syntax service directories of all parts of the ISO 9735 series.
This part of ISO 9735 specifies the syntax service directories of all parts of the ISO 9735 series.
ISO 9735-10:2002 is classified under the following ICS (International Classification for Standards) categories: 35.240.60 - IT applications in transport; 35.240.63 - IT applications in trade. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO 9735-10:2002 has the following relationships with other standards: It is inter standard links to ISO/TS 16401-2:2012, ISO 9735-10:2014. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase ISO 9735-10:2002 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ISO standards.
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 9735-10
First edition
2002-07-01
Electronic data interchange for
administration, commerce and transport
(EDIFACT) — Application level syntax rules
(Syntax version number: 4, Syntax release
number: 1) —
Part 10:
Syntax service directories
Échange de données informatisé pour l'administration, le commerce et le
transport (EDIFACT) — Règles de syntaxe au niveau de l'application
(numéro de version de syntaxe: 4, numéro d'édition de syntaxe: 1) —
Partie 10: Annuaires de syntaxe
Reference number
©
ISO 2002
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2002
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO 2002 – All rights reserved
Contents Page
Foreword.iv
Introduction.v
1 Scope .1
2 Conformance.1
3 Normative references.1
4 Terms and definitions .2
5 Syntax service directories .3
5.1 Service segment directory.3
5.2 Service composite data element directory .25
5.3 Service simple data element directory.35
6 Syntax service code list directory .58
Annex A (informative) ‘Snapshot’ of the syntax service code list directory.59
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO
member bodies). The work of preparing International Standards is normally carried out through ISO technical
committees. Each member body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, governmental and non-governmental, in
liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
The main task of technical committees is to prepare International Standards. Draft International Standards adopted
by the technical committees are circulated to the member bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this part of ISO 9735 may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 9735-10 was prepared by Technical Committee ISO/TC 154, Processes, data elements and documents in
commerce, industry and administration in collaboration with UN/CEFACT through the Joint Syntax Working Group
(JSWG).
For maintenance reasons of the Syntax service directories this part was extracted and updated from each of the
relevant annex parts of the ISO 9735 series, first edition, published in 1998 and 1999.
ISO 9735 consists of the following parts, under the general title Electronic data interchange for administration,
commerce and transport (EDIFACT) — Application level syntax rules (Syntax version number: 4, Syntax release
number: 1):
— Part 1: Syntax rules common to all parts
— Part 2: Syntax rules specific to batch EDI
— Part 3: Syntax rules specific to interactive EDI
— Part 4: Syntax and service report message for batch EDI (message type — CONTRL)
— Part 5: Security rules for batch EDI (authenticity, integrity and non-repudiation of origin)
— Part 6: Secure authentication and acknowledgement message (message type — AUTACK)
— Part 7: Security rules for batch EDI (confidentiality)
— Part 8: Associated data in EDI
— Part 9: Security key and certificate management message (message type — KEYMAN)
— Part 10: Syntax service directories
Further parts may be added in the future.
iv © ISO 2002 – All rights reserved
Introduction
This part of ISO 9735 includes the rules at the application level for the structuring of data in the interchange of
electronic messages in an open environment, based on the requirements of either batch or interactive processing.
These rules have been agreed by the United Nations Economic Commission for Europe (UN/ECE) as syntax rules
for Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) and are part of the United
Nations Trade Data Interchange Directory (UNTDID) which also includes both batch and interactive Message
Design Guidelines.
This part of ISO 9735 may be used in any application, but messages using these rules may only be referred to as
EDIFACT messages if they comply with other guidelines, rules and directories in the UNTDID. For UN/EDIFACT,
batch messages shall comply with the message design rules for batch usage. These rules are maintained in the
UNTDID.
Communications specifications and protocols are outside the scope of this part of ISO 9735.
This is a new part, which has been added to ISO 9735. It consolidates a redraft of corresponding sections in the
first edition of the ISO 9735 series published in 1998 and 1999. In addition a ‘snapshot’ of the syntax service code
list directory is amended in order to illustrate the usage of the coded data elements.
INTERNATIONAL STANDARD ISO 9735-10:2002(E)
Electronic data interchange for administration, commerce and
transport (EDIFACT) — Application level syntax rules (Syntax
version number: 4, Syntax release number: 1) —
Part 10:
Syntax service directories
1 Scope
This part of ISO 9735 specifies the syntax service directories of all parts of the ISO 9735 series.
2 Conformance
Whereas this part shall use a version number of “4” in the mandatory data element 0002 (Syntax version number),
and shall use a release number of “01” in the conditional data element 0076 (Syntax release number), each of
which appear in the segment UNB (Interchange header), interchanges continuing to use the syntax defined in the
earlier published versions shall use the following Syntax version numbers, in order to differentiate them from each
other and from this part:
ISO 9735:1988: Syntax version number: 1
ISO 9735:1988 (amended and reprinted in 1990): Syntax version number: 2
ISO 9735:1988 and its Amendment 1:1992: Syntax version number: 3
ISO 9735:1998: Syntax version number: 4
Conformance to a standard means that all of its requirements, including all options, are supported. If all options are
not supported, any claim of conformance shall include a statement which identifies those options to which
conformance is claimed.
Data that is interchanged is in conformance if the structure and representation of the data conform to the syntax
rules specified in this part of ISO 9735.
Devices supporting this part of ISO 9735 are in conformance when they are capable of creating and/or interpreting
the data structured and represented in conformance with the standard.
Conformance to this part shall include conformance to parts 1 to 9 of ISO 9735.
When identified in this part of ISO 9735, provisions defined in related standards shall form part of the conformance
criteria.
3 Normative references
The following normative documents contain provisions which, through reference in this text, constitute provisions of
this part of ISO 9735. For dated references, subsequent amendments to, or revisions of, any of these publications
do not apply. However, parties to agreements based on this part of ISO 9735 are encouraged to investigate the
possibility of applying the most recent editions of the normative documents indicated below. For undated
references, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain
registers of currently valid International Standards.
ISO 9735-1:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 1: Syntax rules
common to all parts
ISO 9735-2:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 2: Syntax rules specific
to batch EDI
ISO 9735-3:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 3: Syntax rules specific
to interactive EDI
ISO 9735-4:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 4: Syntax and service
report message for batch EDI (message type — CONTRL)
ISO 9735-5:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 5: Security rules for
batch EDI (authenticity, integrity and non-repudiation of origin)
ISO 9735-6:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 6: Secure
authentication and acknowledgement message (message type — AUTACK)
ISO 9735-7:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 7: Security rules for
batch EDI (confidentiality)
ISO 9735-8:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 8: Associated data in
EDI
ISO 9735-9:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 9: Security key and
certificate management message (message type — KEYMAN)
4 Terms and definitions
For the purposes of this part of ISO 9735, the terms and definitions given in ISO 9735-1 apply.
2 © ISO 2002 – All rights reserved
5 Syntax service directories
5.1 Service segment directory
5.1.1 Service segment specification legend:
Function The function of the segment
POS The sequential position number of the stand-alone data element or composite data element in the
segment table
TAG The tags for all service segments contained in the segment directory shall start with the letter “U”. The
tags of all service composite data elements start with the letter “S”, and the tags of all service simple
data elements start with the figure “0”.
Name Name of a COMPOSITE DATA ELEMENT in capital letters
Name of a STAND-ALONE DATA ELEMENT in capital letters
Name of a component data element in small letters
S The status of the stand-alone data element or composite data element in the segment, or of the
components in the composite (where M = Mandatory and C = Conditional)
R The maximum number of occurrences of a stand-alone data element or composite data element in the
segment
Repr. Data value representation of the stand-alone data element or component data elements in the
composite:
a alphabetic characters
n numeric characters
an alphanumeric characters
a3 3 alphabetic characters, fixed length
n3 3 numeric characters, fixed length
an3 3 alphanumeric characters, fixed length
a.3 up to 3 alphabetic characters
n.3 up to 3 numeric characters
an.3 up to 3 alphanumeric characters
5.1.2 Dependency note identifiers
Code Name
D1 One and only one
D2 All or none
D3 One or more
D4 One or none
D5 If first, then all
D6 If first, then at least one more
D7 If first, then none of the others
See ISO 9735-1:2002, 11.5, for the definition of the dependency note identifiers.
5.1.3 Index of service segments by tag
Change indicators (in comparison with parts 1 to 9 of ISO 9735 published
in 1998/99)
a plus sign (+) for an addition
an asterisk (*) for an amendment to structure
a hash sign (#) for changes to names
a vertical bar (|) for changes to text for descriptions,
notes and functions
a minus sign (-) for a deletion
an X sign (X) for marked for deletion
Tag Name
UCD Data element error indication
UCF Group response
UCI Interchange response
UCM Message/package response
UCS Segment error indication
UGH Anti-collision segment group header
UGT Anti-collision segment group trailer
UIB Interactive interchange header
UIH Interactive message header
*| UIR Interactive status
UIT Interactive message trailer
UIZ Interactive interchange trailer
UNB Interchange header
UNE Group trailer
UNG Group header
UNH Message header
UNO Object header
UNP Object trailer
UNS Section control
UNT Message trailer
UNZ Interchange trailer
USA Security algorithm
USB Secured data identification
USC Certificate
USD Data encryption header
USE Security message relation
USF Key management function
USH Security header
USL Security list status
USR Security result
UST Security trailer
USU Data encryption trailer
USX Security references
USY Security on references
4 © ISO 2002 – All rights reserved
5.1.4 Index of service segments by name
Change indicators (in comparison with parts 1 to 9 of ISO 9735 published
in 1998/99)
a plus sign (+) for an addition
an asterisk (*) for an amendment to structure
a hash sign (#) for changes to names
a vertical bar (|) for changes to text for descriptions,
notes and functions
a minus sign (-) for a deletion
an X sign (X) for marked for deletion
Tag Name
UGH Anti-collision segment group header
UGT Anti-collision segment group trailer
USC Certificate
UCD Data element error indication
USD Data encryption header
USU Data encryption trailer
UNG Group header
UCF Group response
UNE Group trailer
UIB Interactive interchange header
UIZ Interactive interchange trailer
UIH Interactive message header
UIT Interactive message trailer
*| UIR Interactive status
UNB Interchange header
UCI Interchange response
UNZ Interchange trailer
USF Key management function
UNH Message header
UNT Message trailer
UCM Message/package response
UNO Object header
UNP Object trailer
UNS Section control
USB Secured data identification
USA Security algorithm
USH Security header
USL Security list status
USE Security message relation
USY Security on references
USX Security references
USR Security result
UST Security trailer
UCS Segment error indication
5.1.5 Service segment specifications
Change indicators (in comparison with parts 1 to 9 of ISO 9735 published
in 1998/99)
a plus sign (+) for an addition
an asterisk (*) for an amendment to structure
a hash sign (#) for changes to names
a vertical bar (|) for changes to text for descriptions,
notes and functions
a minus sign (-) for a deletion
an X sign (X) for marked for deletion
------------------------------------------------------------------------------
UCD DATA ELEMENT ERROR INDICATION
Function: To identify an erroneous stand-alone, composite or component
data element, and to identify the nature of the error.
Pos TAG Name S R Repr. Notes
010 0085 SYNTAX ERROR, CODED M 1 an.3
020 S011 DATA ELEMENT IDENTIFICATION M 1
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
------------------------------------------------------------------------------
UCF GROUP RESPONSE
Function: To identify a group in the subject interchange and to indicate
acknowledgement or rejection (action taken) of the UNG and UNE
segments, and to identify any error related to these segments.
It can also identify errors related to the USA, USC, USD, USH,
USR, UST, or USU security segments when they appear at the
group level. Depending on the action code, it may also
indicate the action taken on the messages and packages within
that group.
Pos TAG Name S R Repr. Notes
010 0048 GROUP REFERENCE NUMBER M 1 an.14
020 S006 APPLICATION SENDER IDENTIFICATION C 1 7
0040 Application sender identification M an.35
0007 Identification code qualifier C an.4
030 S007 APPLICATION RECIPIENT IDENTIFICATION C 1 7
0044 Application recipient identification M an.35
0007 Identification code qualifier C an.4
040 0083 ACTION, CODED M 1 an.3
050 0085 SYNTAX ERROR, CODED C 1 an.3 1,2,3,
060 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 1,2,3,
4,5
070 S011 DATA ELEMENT IDENTIFICATION C 1 2
6 © ISO 2002 – All rights reserved
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
080 0534 SECURITY REFERENCE NUMBER C 1 an.14 3,4,6
090 0138 SECURITY SEGMENT POSITION C 1 n.6 3,4,6
DEPENDENCY NOTES:
1. D5(060, 050) If first, then all
2. D5(070, 060, 050) If first, then all
3. D5(080, 060, 050, 090) If first, then all
4. D5(090, 080, 060, 050) If first, then all
OTHER NOTES:
5. 0135, may only contain the values UNG, UNE, USA, USC, USD, USH, USR, UST,
or USU.
6. This data element shall be present when reporting an error in a security
segment.
7. This data element shall be present if it was present in the subject
interchange.
------------------------------------------------------------------------------
UCI INTERCHANGE RESPONSE
Function: To identify the subject interchange, to indicate interchange
receipt, to indicate acknowledgement or rejection (action
taken) of the UNA, UNB and UNZ segments, and to identify any
error related to these segments. It can also identify errors
related to the USA, USC, USD, USH, USR, UST, or USU security
segments when they appear at the interchange level. Depending
on the action code, it may also indicate the action taken on
the groups, messages, and packages within that interchange.
Pos TAG Name S R Repr. Notes
010 0020 INTERCHANGE CONTROL REFERENCE M 1 an.14
020 S002 INTERCHANGE SENDER M 1
0004 Interchange sender identification M an.35
0007 Identification code qualifier C an.4
0008 Interchange sender internal
identification C an.35
0042 Interchange sender internal
sub-identification C an.35
030 S003 INTERCHANGE RECIPIENT M 1
0010 Interchange recipient identification M an.35
0007 Identification code qualifier C an.4
0014 Interchange recipient internal
identification C an.35
0046 Interchange recipient internal
sub-identification C an.35
040 0083 ACTION, CODED M 1 an.3
050 0085 SYNTAX ERROR, CODED C 1 an.3 1,2,3,
060 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 1,2,3,
4,5
070 S011 DATA ELEMENT IDENTIFICATION C 1 2
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
080 0534 SECURITY REFERENCE NUMBER C 1 an.14 3,4,6
090 0138 SECURITY SEGMENT POSITION C 1 n.6 3,4,6
DEPENDENCY NOTES:
1. D5(060, 050) If first, then all
2. D5(070, 060, 050) If first, then all
3. D5(080, 060, 050, 090) If first, then all
4. D5(090, 080, 060, 050) If first, then all
OTHER NOTES:
5. 0135, may only contain the values UNA, UNB, UNZ, USA, USC, USD, USH, USR,
UST, or USU.
6. This data element shall be present when reporting an error in a security
segment.
------------------------------------------------------------------------------
UCM MESSAGE/PACKAGE RESPONSE
Function: To identify a message or package in the subject interchange,
and to indicate that message's or package's acknowledgement or
rejection (action taken), and to identify any error related to
the UNH, UNT, UNO, and UNP segments. It can also identify
errors related to the USA, USC, USD, USH, USR, UST, or USU
security segments when they appear at the message or package
level.
Pos TAG Name S R Repr. Notes
010 0062 MESSAGE REFERENCE NUMBER C 1 an.14 1,2
020 S009 MESSAGE IDENTIFIER C 1 2
0065 Message type M an.6
0052 Message version number M an.3
0054 Message release number M an.3
0051 Controlling agency, coded M an.3
0057 Association assigned code C an.6
0110 Code list directory version number C an.6
0113 Message type sub-function identification C an.6
030 0083 ACTION, CODED M 1 an.3
040 0085 SYNTAX ERROR, CODED C 1 an.3 4,5,6,
050 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 4,5,6,
8 © ISO 2002 – All rights reserved
7,8
060 S011 DATA ELEMENT IDENTIFICATION C 1 5
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
070 0800 PACKAGE REFERENCE NUMBER C 1 an.35 1,3
080 S020 REFERENCE IDENTIFICATION C 99 3
0813 Reference qualifier M an.3
0802 Reference identification number M an.35
090 0534 SECURITY REFERENCE NUMBER C 1 an.14 6,7,9
100 0138 SECURITY SEGMENT POSITION C 1 n.6 6,7,9
DEPENDENCY NOTES:
1. D1(010, 070) One and only one
2. D2(010, 020) All or none
3. D2(070, 080) All or none
4. D5(050, 040) If first, then all
5. D5(060, 050, 040) If first, then all
6. D5(090, 050, 040, 100) If first, then all
7. D5(100, 090, 050, 040) If first, then all
OTHER NOTES:
8. 0135, may only contain the values UNH, UNT, UNO, UNP, USA, USC, USD, USH,
USR, UST, or USU.
9. This data element shall be present when reporting an error in a security
segment.
------------------------------------------------------------------------------
UCS SEGMENT ERROR INDICATION
Function: To identify either a segment containing an error or a missing
segment, and to identify any error related to the complete
segment.
Pos TAG Name S R Repr. Notes
010 0096 SEGMENT POSITION IN MESSAGE BODY M 1 n.6
020 0085 SYNTAX ERROR, CODED C 1 an.3 1
NOTES:
1. 0085, shall contain a value only if the error pertains to the segment
identified by data element 0096.
------------------------------------------------------------------------------
UGH ANTI-COLLISION SEGMENT GROUP HEADER
Function: To head, identify and specify an anti-collision segment group.
Pos TAG Name S R Repr. Notes
010 0087 ANTI-COLLISION SEGMENT GROUP IDENTIFICATION M 1 an.4 1
NOTES:
1. 0087, the value shall be the segment group number of the UGH/UGT segment
group as stated in the message specification. It shall be identical to the
value in 0087 in the corresponding UGT segment.
------------------------------------------------------------------------------
UGT ANTI-COLLISION SEGMENT GROUP TRAILER
Function: To end and check the completeness of an anti-collision segment
group.
Pos TAG Name S R Repr. Notes
010 0087 ANTI-COLLISION SEGMENT GROUP IDENTIFICATION M 1 an.4 1
NOTES:
1. 0087, the value shall be the segment group number of the UGH/UGT segment
group as stated in the message specification. It shall be identical to the
value in 0087 in the corresponding UGH segment.
------------------------------------------------------------------------------
UIB INTERACTIVE INTERCHANGE HEADER
Function: To head and identify an interchange.
Pos TAG Name S R Repr. Notes
010 S001 SYNTAX IDENTIFIER M 1 3
0001 Syntax identifier M a4
0002 Syntax version number M an1
0080 Service code list directory version
number C an.6
0133 Character encoding, coded C an.3
0076 Syntax release number C an2
020 S302 DIALOGUE REFERENCE C 1 1,2,4,
5,8
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
030 S303 TRANSACTION REFERENCE C 1 1,8
0306 Transaction control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
040 S018 SCENARIO IDENTIFICATION C 1
0127 Scenario identification M an.14
0128 Scenario version number C an.3
0130 Scenario release number C an.3
0051 Controlling agency, coded C an.3
050 S305 DIALOGUE IDENTIFICATION C 1 2
0311 Dialogue identification M an.14
0342 Dialogue version number C an.3
0344 Dialogue release number C an.3
10 © ISO 2002 – All rights reserved
0051 Controlling agency, coded C an.3
060 S002 INTERCHANGE SENDER C 1 5
0004 Interchange sender identification M an.35
0007 Identification code qualifier C an.4
0008 Interchange sender internal
identification C an.35
0042 Interchange sender internal
sub-identification C an.35
070 S003 INTERCHANGE RECIPIENT C 1
0010 Interchange recipient identification M an.35
0007 Identification code qualifier C an.4
0014 Interchange recipient internal
identification C an.35
0046 Interchange recipient internal
sub-identification C an.35
080 S300 DATE AND/OR TIME OF INITIATION C 1
0338 Event date C n.8
0314 Event time C an.15
0336 Time offset C n4
090 0325 DUPLICATE INDICATOR C 1 a1 6
100 0035 TEST INDICATOR C 1 n1 7
DEPENDENCY NOTES:
1. D5(030, 020) If first, then all
2. D5(050, 020) If first, then all
OTHER NOTES:
3. S001/0002, shall be '4' to indicate this version of the syntax.
4. S302/0304, when provided by the responder, shall be returned by the
initiator throughout the dialogue.
5. S002/0004, may be same as S302/0303 for initiator of transaction.
6. 0325, only used if the interchange is a duplicate transfer.
7. 0035, set by the initiator if the dialogue is a test. Applies to every
subsequent message and service segment in the dialogue. Otherwise not
used.
8. Dialogue and transaction control can be accomplished through the dialogue
(S302) and transaction (S303) references. Optionally, if another means of
control is chosen, these two composite data elements need not be
utilised.
------------------------------------------------------------------------------
UIH INTERACTIVE MESSAGE HEADER
Function: To head, identify and specify a message.
Pos TAG Name S R Repr. Notes
010 S306 INTERACTIVE MESSAGE IDENTIFIER M 1
0065 Message type M an.6
0052 Message version number M an.3
0054 Message release number M an.3
0113 Message type sub-function identification C an.6
0051 Controlling agency, coded C an.3
0057 Association assigned code C an.6
020 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1,5
030 S302 DIALOGUE REFERENCE C 1 2,4,5
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
040 S301 STATUS OF TRANSFER - INTERACTIVE C 1
0320 Sender sequence number C n.6
0323 Transfer position, coded C a1
0325 Duplicate Indicator C a1
050 S300 DATE AND/OR TIME OF INITIATION C 1
0338 Event date C n.8
0314 Event time C an.15
0336 Time offset C n4
060 0035 TEST INDICATOR C 1 n1 3
NOTES:
1. The value in 0340 shall be unique within the interchange (except for a
duplicate transfer).
2. The value(s) in S302 shall be identical to the value(s) in S302 in the
preceding UIB.
3. 0035, when used, test applies to the message only.
4. Dialogue control can be accomplished through the dialogue reference
(S302). Optionally, if another means of control is chosen, this composite
data element need not be utilised.
5. A combination of 0340 and S302 may be used to identify uniquely a message.
------------------------------------------------------------------------------
*| UIR INTERACTIVE STATUS
Function: To report the status of the dialogue.
+ Note: To avoid endless loops, the UIR segment is not used to respond
to a UIR received with syntax errors.
Pos TAG Name S R Repr. Notes
010 0331 REPORT FUNCTION, CODED M 1 an.3
020 S307 STATUS INFORMATION C 9
0333 Status, coded C an.3
0332 Status C an.70
0335 Language, coded C an.3
030 S302 DIALOGUE REFERENCE C 1
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
040 S300 DATE AND/OR TIME OF INITIATION C 1
0338 Event date C n.8
0314 Event time C an.15
12 © ISO 2002 – All rights reserved
0336 Time offset C n4
050 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1,4
060 0800 PACKAGE REFERENCE NUMBER C 1 an.35 1,5
070 + 0085 SYNTAX ERROR, CODED C 1 an.3 2,3
080 + 0096 SEGMENT POSITION IN MESSAGE BODY C 1 n.6 2,3
090 + S011 DATA ELEMENT IDENTIFICATION C 1 3
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
DEPENDENCY NOTES:
1. D1(050, 060) One and only one
2.+ D5(080, 070) If first, then all
3.+ D5(090, 070, 080) If first, then all
OTHER NOTES:
4. 0340, the value shall be identical to the value in 0340 in the UIH of a
message received by the sender of the UIR within the same dialogue.
5. 0800, the value shall be identical to the value in 0800 in the UNO
received by the sender of the UIR within the same dialogue.
------------------------------------------------------------------------------
UIT INTERACTIVE MESSAGE TRAILER
Function: To end and check the completeness of a message.
Pos TAG Name S R Repr. Notes
010 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1
020 0074 NUMBER OF SEGMENTS IN A MESSAGE C 1 n.10
NOTES:
1. 0340, the value shall be identical to the value in 0340 in the
corresponding UIH segment.
------------------------------------------------------------------------------
UIZ INTERACTIVE INTERCHANGE TRAILER
Function: To end and check the completeness of an interchange.
Pos TAG Name S R Repr. Notes
010 S302 DIALOGUE REFERENCE C 1 1
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
020 0036 INTERCHANGE CONTROL COUNT C 1 n.6
030 0325 DUPLICATE INDICATOR C 1 a1 2
NOTES:
1. S302, the value shall be identical to the value in the responder's
dialogue reference in S302 in the UIB segment.
2. 0325, only used if the interchange is a duplicate transfer.
------------------------------------------------------------------------------
UNB INTERCHANGE HEADER
Function: To identify an interchange.
Pos TAG Name S R Repr. Notes
010 S001 SYNTAX IDENTIFIER M 1 1
0001 Syntax identifier M a4
0002 Syntax version number M an1
0080 Service code list directory version
number C an.6
0133 Character encoding, coded C an.3
0076 Syntax release number C an2
020 S002 INTERCHANGE SENDER M 1 2
0004 Interchange sender identification M an.35
0007 Identification code qualifier C an.4
0008 Interchange sender internal
identification C an.35
0042 Interchange sender internal
sub-identification C an.35
030 S003 INTERCHANGE RECIPIENT M 1 2
0010 Interchange recipient identification M an.35
0007 Identification code qualifier C an.4
0014 Interchange recipient internal
identification C an.35
0046 Interchange recipient internal
sub-identification C an.35
040 S004 DATE AND TIME OF PREPARATION M 1
0017 Date M n8
0019 Time M n4
050 0020 INTERCHANGE CONTROL REFERENCE M 1 an.14 2
060 S005 RECIPIENT REFERENCE/PASSWORD DETAILS C 1
0022 Recipient reference/password M an.14
0025 Recipient reference/password qualifier C an2
070 0026 APPLICATION REFERENCE C 1 an.14
080 0029 PROCESSING PRIORITY CODE C 1 a1
090 0031 ACKNOWLEDGEMENT REQUEST C 1 n1
100 0032 INTERCHANGE AGREEMENT IDENTIFIER C 1 an.35
110 0035 TEST INDICATOR C 1 n1
NOTES:
1. S001/0002, shall be '4' to indicate this version of the syntax.
2. The combination of the values carried in data elements S002, S003 and 0020
shall be used to identify uniquely the interchange, for the purpose of
acknowledgement.
14 © ISO 2002 – All rights reserved
------------------------------------------------------------------------------
UNE GROUP TRAILER
Function: To end and check the completeness of a group.
Pos TAG Name S R Repr. Notes
010 0060 GROUP CONTROL COUNT M 1 n.6
020 0048 GROUP REFERENCE NUMBER M 1 an.14 1
NOTE
...
SLOVENSKI OSIST ISO 9735-10:2004
PREDSTANDARD
maj 2004
Elektronska menjava podatkov (-računalniška-) v administraciji (upravi),
trgovini in transportu (prevozništvu) EDIFACT - Pravila sintakse za
uporabniški nivo (izvedbena oblika sintakse: 4, zaporedna št. izdaje 1) Deseti
del: sintaksa servisnih direktorijev (skladnja servisnih poddirektorijev)
Electronic data interchange for administration, commerce and transport
(EDIFACT) - Application level syntax rules (Syntax version number: 4, Syntax
release number: 1) - Part 10: Syntax service directories
ICS 35.240.60 Referenčna številka
© Standard je založil in izdal Slovenski inštitut za standardizacijo. Razmnoževanje ali kopiranje celote ali delov tega dokumenta ni dovoljeno
INTERNATIONAL ISO
STANDARD 9735-10
First edition
2002-07-01
Electronic data interchange for
administration, commerce and transport
(EDIFACT) — Application level syntax rules
(Syntax version number: 4, Syntax release
number: 1) —
Part 10:
Syntax service directories
Échange de données informatisé pour l'administration, le commerce et le
transport (EDIFACT) — Règles de syntaxe au niveau de l'application
(numéro de version de syntaxe: 4, numéro d'édition de syntaxe: 1) —
Partie 10: Annuaires de syntaxe
Reference number
©
ISO 2002
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2002
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO 2002 – All rights reserved
Contents Page
Foreword.iv
Introduction.v
1 Scope .1
2 Conformance.1
3 Normative references.1
4 Terms and definitions .2
5 Syntax service directories .3
5.1 Service segment directory.3
5.2 Service composite data element directory .25
5.3 Service simple data element directory.35
6 Syntax service code list directory .58
Annex A (informative) ‘Snapshot’ of the syntax service code list directory.59
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO
member bodies). The work of preparing International Standards is normally carried out through ISO technical
committees. Each member body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, governmental and non-governmental, in
liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
The main task of technical committees is to prepare International Standards. Draft International Standards adopted
by the technical committees are circulated to the member bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this part of ISO 9735 may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 9735-10 was prepared by Technical Committee ISO/TC 154, Processes, data elements and documents in
commerce, industry and administration in collaboration with UN/CEFACT through the Joint Syntax Working Group
(JSWG).
For maintenance reasons of the Syntax service directories this part was extracted and updated from each of the
relevant annex parts of the ISO 9735 series, first edition, published in 1998 and 1999.
ISO 9735 consists of the following parts, under the general title Electronic data interchange for administration,
commerce and transport (EDIFACT) — Application level syntax rules (Syntax version number: 4, Syntax release
number: 1):
— Part 1: Syntax rules common to all parts
— Part 2: Syntax rules specific to batch EDI
— Part 3: Syntax rules specific to interactive EDI
— Part 4: Syntax and service report message for batch EDI (message type — CONTRL)
— Part 5: Security rules for batch EDI (authenticity, integrity and non-repudiation of origin)
— Part 6: Secure authentication and acknowledgement message (message type — AUTACK)
— Part 7: Security rules for batch EDI (confidentiality)
— Part 8: Associated data in EDI
— Part 9: Security key and certificate management message (message type — KEYMAN)
— Part 10: Syntax service directories
Further parts may be added in the future.
iv © ISO 2002 – All rights reserved
Introduction
This part of ISO 9735 includes the rules at the application level for the structuring of data in the interchange of
electronic messages in an open environment, based on the requirements of either batch or interactive processing.
These rules have been agreed by the United Nations Economic Commission for Europe (UN/ECE) as syntax rules
for Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT) and are part of the United
Nations Trade Data Interchange Directory (UNTDID) which also includes both batch and interactive Message
Design Guidelines.
This part of ISO 9735 may be used in any application, but messages using these rules may only be referred to as
EDIFACT messages if they comply with other guidelines, rules and directories in the UNTDID. For UN/EDIFACT,
batch messages shall comply with the message design rules for batch usage. These rules are maintained in the
UNTDID.
Communications specifications and protocols are outside the scope of this part of ISO 9735.
This is a new part, which has been added to ISO 9735. It consolidates a redraft of corresponding sections in the
first edition of the ISO 9735 series published in 1998 and 1999. In addition a ‘snapshot’ of the syntax service code
list directory is amended in order to illustrate the usage of the coded data elements.
INTERNATIONAL STANDARD ISO 9735-10:2002(E)
Electronic data interchange for administration, commerce and
transport (EDIFACT) — Application level syntax rules (Syntax
version number: 4, Syntax release number: 1) —
Part 10:
Syntax service directories
1 Scope
This part of ISO 9735 specifies the syntax service directories of all parts of the ISO 9735 series.
2 Conformance
Whereas this part shall use a version number of “4” in the mandatory data element 0002 (Syntax version number),
and shall use a release number of “01” in the conditional data element 0076 (Syntax release number), each of
which appear in the segment UNB (Interchange header), interchanges continuing to use the syntax defined in the
earlier published versions shall use the following Syntax version numbers, in order to differentiate them from each
other and from this part:
ISO 9735:1988: Syntax version number: 1
ISO 9735:1988 (amended and reprinted in 1990): Syntax version number: 2
ISO 9735:1988 and its Amendment 1:1992: Syntax version number: 3
ISO 9735:1998: Syntax version number: 4
Conformance to a standard means that all of its requirements, including all options, are supported. If all options are
not supported, any claim of conformance shall include a statement which identifies those options to which
conformance is claimed.
Data that is interchanged is in conformance if the structure and representation of the data conform to the syntax
rules specified in this part of ISO 9735.
Devices supporting this part of ISO 9735 are in conformance when they are capable of creating and/or interpreting
the data structured and represented in conformance with the standard.
Conformance to this part shall include conformance to parts 1 to 9 of ISO 9735.
When identified in this part of ISO 9735, provisions defined in related standards shall form part of the conformance
criteria.
3 Normative references
The following normative documents contain provisions which, through reference in this text, constitute provisions of
this part of ISO 9735. For dated references, subsequent amendments to, or revisions of, any of these publications
do not apply. However, parties to agreements based on this part of ISO 9735 are encouraged to investigate the
possibility of applying the most recent editions of the normative documents indicated below. For undated
references, the latest edition of the normative document referred to applies. Members of ISO and IEC maintain
registers of currently valid International Standards.
ISO 9735-1:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 1: Syntax rules
common to all parts
ISO 9735-2:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 2: Syntax rules specific
to batch EDI
ISO 9735-3:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 3: Syntax rules specific
to interactive EDI
ISO 9735-4:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 4: Syntax and service
report message for batch EDI (message type — CONTRL)
ISO 9735-5:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 5: Security rules for
batch EDI (authenticity, integrity and non-repudiation of origin)
ISO 9735-6:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 6: Secure
authentication and acknowledgement message (message type — AUTACK)
ISO 9735-7:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 7: Security rules for
batch EDI (confidentiality)
ISO 9735-8:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 8: Associated data in
EDI
ISO 9735-9:2002, Electronic data interchange for administration, commerce and transport (EDIFACT) —
Application level syntax rules (Syntax version number: 4, Syntax release number: 1) — Part 9: Security key and
certificate management message (message type — KEYMAN)
4 Terms and definitions
For the purposes of this part of ISO 9735, the terms and definitions given in ISO 9735-1 apply.
2 © ISO 2002 – All rights reserved
5 Syntax service directories
5.1 Service segment directory
5.1.1 Service segment specification legend:
Function The function of the segment
POS The sequential position number of the stand-alone data element or composite data element in the
segment table
TAG The tags for all service segments contained in the segment directory shall start with the letter “U”. The
tags of all service composite data elements start with the letter “S”, and the tags of all service simple
data elements start with the figure “0”.
Name Name of a COMPOSITE DATA ELEMENT in capital letters
Name of a STAND-ALONE DATA ELEMENT in capital letters
Name of a component data element in small letters
S The status of the stand-alone data element or composite data element in the segment, or of the
components in the composite (where M = Mandatory and C = Conditional)
R The maximum number of occurrences of a stand-alone data element or composite data element in the
segment
Repr. Data value representation of the stand-alone data element or component data elements in the
composite:
a alphabetic characters
n numeric characters
an alphanumeric characters
a3 3 alphabetic characters, fixed length
n3 3 numeric characters, fixed length
an3 3 alphanumeric characters, fixed length
a.3 up to 3 alphabetic characters
n.3 up to 3 numeric characters
an.3 up to 3 alphanumeric characters
5.1.2 Dependency note identifiers
Code Name
D1 One and only one
D2 All or none
D3 One or more
D4 One or none
D5 If first, then all
D6 If first, then at least one more
D7 If first, then none of the others
See ISO 9735-1:2002, 11.5, for the definition of the dependency note identifiers.
5.1.3 Index of service segments by tag
Change indicators (in comparison with parts 1 to 9 of ISO 9735 published
in 1998/99)
a plus sign (+) for an addition
an asterisk (*) for an amendment to structure
a hash sign (#) for changes to names
a vertical bar (|) for changes to text for descriptions,
notes and functions
a minus sign (-) for a deletion
an X sign (X) for marked for deletion
Tag Name
UCD Data element error indication
UCF Group response
UCI Interchange response
UCM Message/package response
UCS Segment error indication
UGH Anti-collision segment group header
UGT Anti-collision segment group trailer
UIB Interactive interchange header
UIH Interactive message header
*| UIR Interactive status
UIT Interactive message trailer
UIZ Interactive interchange trailer
UNB Interchange header
UNE Group trailer
UNG Group header
UNH Message header
UNO Object header
UNP Object trailer
UNS Section control
UNT Message trailer
UNZ Interchange trailer
USA Security algorithm
USB Secured data identification
USC Certificate
USD Data encryption header
USE Security message relation
USF Key management function
USH Security header
USL Security list status
USR Security result
UST Security trailer
USU Data encryption trailer
USX Security references
USY Security on references
4 © ISO 2002 – All rights reserved
5.1.4 Index of service segments by name
Change indicators (in comparison with parts 1 to 9 of ISO 9735 published
in 1998/99)
a plus sign (+) for an addition
an asterisk (*) for an amendment to structure
a hash sign (#) for changes to names
a vertical bar (|) for changes to text for descriptions,
notes and functions
a minus sign (-) for a deletion
an X sign (X) for marked for deletion
Tag Name
UGH Anti-collision segment group header
UGT Anti-collision segment group trailer
USC Certificate
UCD Data element error indication
USD Data encryption header
USU Data encryption trailer
UNG Group header
UCF Group response
UNE Group trailer
UIB Interactive interchange header
UIZ Interactive interchange trailer
UIH Interactive message header
UIT Interactive message trailer
*| UIR Interactive status
UNB Interchange header
UCI Interchange response
UNZ Interchange trailer
USF Key management function
UNH Message header
UNT Message trailer
UCM Message/package response
UNO Object header
UNP Object trailer
UNS Section control
USB Secured data identification
USA Security algorithm
USH Security header
USL Security list status
USE Security message relation
USY Security on references
USX Security references
USR Security result
UST Security trailer
UCS Segment error indication
5.1.5 Service segment specifications
Change indicators (in comparison with parts 1 to 9 of ISO 9735 published
in 1998/99)
a plus sign (+) for an addition
an asterisk (*) for an amendment to structure
a hash sign (#) for changes to names
a vertical bar (|) for changes to text for descriptions,
notes and functions
a minus sign (-) for a deletion
an X sign (X) for marked for deletion
------------------------------------------------------------------------------
UCD DATA ELEMENT ERROR INDICATION
Function: To identify an erroneous stand-alone, composite or component
data element, and to identify the nature of the error.
Pos TAG Name S R Repr. Notes
010 0085 SYNTAX ERROR, CODED M 1 an.3
020 S011 DATA ELEMENT IDENTIFICATION M 1
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
------------------------------------------------------------------------------
UCF GROUP RESPONSE
Function: To identify a group in the subject interchange and to indicate
acknowledgement or rejection (action taken) of the UNG and UNE
segments, and to identify any error related to these segments.
It can also identify errors related to the USA, USC, USD, USH,
USR, UST, or USU security segments when they appear at the
group level. Depending on the action code, it may also
indicate the action taken on the messages and packages within
that group.
Pos TAG Name S R Repr. Notes
010 0048 GROUP REFERENCE NUMBER M 1 an.14
020 S006 APPLICATION SENDER IDENTIFICATION C 1 7
0040 Application sender identification M an.35
0007 Identification code qualifier C an.4
030 S007 APPLICATION RECIPIENT IDENTIFICATION C 1 7
0044 Application recipient identification M an.35
0007 Identification code qualifier C an.4
040 0083 ACTION, CODED M 1 an.3
050 0085 SYNTAX ERROR, CODED C 1 an.3 1,2,3,
060 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 1,2,3,
4,5
070 S011 DATA ELEMENT IDENTIFICATION C 1 2
6 © ISO 2002 – All rights reserved
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
080 0534 SECURITY REFERENCE NUMBER C 1 an.14 3,4,6
090 0138 SECURITY SEGMENT POSITION C 1 n.6 3,4,6
DEPENDENCY NOTES:
1. D5(060, 050) If first, then all
2. D5(070, 060, 050) If first, then all
3. D5(080, 060, 050, 090) If first, then all
4. D5(090, 080, 060, 050) If first, then all
OTHER NOTES:
5. 0135, may only contain the values UNG, UNE, USA, USC, USD, USH, USR, UST,
or USU.
6. This data element shall be present when reporting an error in a security
segment.
7. This data element shall be present if it was present in the subject
interchange.
------------------------------------------------------------------------------
UCI INTERCHANGE RESPONSE
Function: To identify the subject interchange, to indicate interchange
receipt, to indicate acknowledgement or rejection (action
taken) of the UNA, UNB and UNZ segments, and to identify any
error related to these segments. It can also identify errors
related to the USA, USC, USD, USH, USR, UST, or USU security
segments when they appear at the interchange level. Depending
on the action code, it may also indicate the action taken on
the groups, messages, and packages within that interchange.
Pos TAG Name S R Repr. Notes
010 0020 INTERCHANGE CONTROL REFERENCE M 1 an.14
020 S002 INTERCHANGE SENDER M 1
0004 Interchange sender identification M an.35
0007 Identification code qualifier C an.4
0008 Interchange sender internal
identification C an.35
0042 Interchange sender internal
sub-identification C an.35
030 S003 INTERCHANGE RECIPIENT M 1
0010 Interchange recipient identification M an.35
0007 Identification code qualifier C an.4
0014 Interchange recipient internal
identification C an.35
0046 Interchange recipient internal
sub-identification C an.35
040 0083 ACTION, CODED M 1 an.3
050 0085 SYNTAX ERROR, CODED C 1 an.3 1,2,3,
060 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 1,2,3,
4,5
070 S011 DATA ELEMENT IDENTIFICATION C 1 2
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
080 0534 SECURITY REFERENCE NUMBER C 1 an.14 3,4,6
090 0138 SECURITY SEGMENT POSITION C 1 n.6 3,4,6
DEPENDENCY NOTES:
1. D5(060, 050) If first, then all
2. D5(070, 060, 050) If first, then all
3. D5(080, 060, 050, 090) If first, then all
4. D5(090, 080, 060, 050) If first, then all
OTHER NOTES:
5. 0135, may only contain the values UNA, UNB, UNZ, USA, USC, USD, USH, USR,
UST, or USU.
6. This data element shall be present when reporting an error in a security
segment.
------------------------------------------------------------------------------
UCM MESSAGE/PACKAGE RESPONSE
Function: To identify a message or package in the subject interchange,
and to indicate that message's or package's acknowledgement or
rejection (action taken), and to identify any error related to
the UNH, UNT, UNO, and UNP segments. It can also identify
errors related to the USA, USC, USD, USH, USR, UST, or USU
security segments when they appear at the message or package
level.
Pos TAG Name S R Repr. Notes
010 0062 MESSAGE REFERENCE NUMBER C 1 an.14 1,2
020 S009 MESSAGE IDENTIFIER C 1 2
0065 Message type M an.6
0052 Message version number M an.3
0054 Message release number M an.3
0051 Controlling agency, coded M an.3
0057 Association assigned code C an.6
0110 Code list directory version number C an.6
0113 Message type sub-function identification C an.6
030 0083 ACTION, CODED M 1 an.3
040 0085 SYNTAX ERROR, CODED C 1 an.3 4,5,6,
050 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 4,5,6,
8 © ISO 2002 – All rights reserved
7,8
060 S011 DATA ELEMENT IDENTIFICATION C 1 5
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
070 0800 PACKAGE REFERENCE NUMBER C 1 an.35 1,3
080 S020 REFERENCE IDENTIFICATION C 99 3
0813 Reference qualifier M an.3
0802 Reference identification number M an.35
090 0534 SECURITY REFERENCE NUMBER C 1 an.14 6,7,9
100 0138 SECURITY SEGMENT POSITION C 1 n.6 6,7,9
DEPENDENCY NOTES:
1. D1(010, 070) One and only one
2. D2(010, 020) All or none
3. D2(070, 080) All or none
4. D5(050, 040) If first, then all
5. D5(060, 050, 040) If first, then all
6. D5(090, 050, 040, 100) If first, then all
7. D5(100, 090, 050, 040) If first, then all
OTHER NOTES:
8. 0135, may only contain the values UNH, UNT, UNO, UNP, USA, USC, USD, USH,
USR, UST, or USU.
9. This data element shall be present when reporting an error in a security
segment.
------------------------------------------------------------------------------
UCS SEGMENT ERROR INDICATION
Function: To identify either a segment containing an error or a missing
segment, and to identify any error related to the complete
segment.
Pos TAG Name S R Repr. Notes
010 0096 SEGMENT POSITION IN MESSAGE BODY M 1 n.6
020 0085 SYNTAX ERROR, CODED C 1 an.3 1
NOTES:
1. 0085, shall contain a value only if the error pertains to the segment
identified by data element 0096.
------------------------------------------------------------------------------
UGH ANTI-COLLISION SEGMENT GROUP HEADER
Function: To head, identify and specify an anti-collision segment group.
Pos TAG Name S R Repr. Notes
010 0087 ANTI-COLLISION SEGMENT GROUP IDENTIFICATION M 1 an.4 1
NOTES:
1. 0087, the value shall be the segment group number of the UGH/UGT segment
group as stated in the message specification. It shall be identical to the
value in 0087 in the corresponding UGT segment.
------------------------------------------------------------------------------
UGT ANTI-COLLISION SEGMENT GROUP TRAILER
Function: To end and check the completeness of an anti-collision segment
group.
Pos TAG Name S R Repr. Notes
010 0087 ANTI-COLLISION SEGMENT GROUP IDENTIFICATION M 1 an.4 1
NOTES:
1. 0087, the value shall be the segment group number of the UGH/UGT segment
group as stated in the message specification. It shall be identical to the
value in 0087 in the corresponding UGH segment.
------------------------------------------------------------------------------
UIB INTERACTIVE INTERCHANGE HEADER
Function: To head and identify an interchange.
Pos TAG Name S R Repr. Notes
010 S001 SYNTAX IDENTIFIER M 1 3
0001 Syntax identifier M a4
0002 Syntax version number M an1
0080 Service code list directory version
number C an.6
0133 Character encoding, coded C an.3
0076 Syntax release number C an2
020 S302 DIALOGUE REFERENCE C 1 1,2,4,
5,8
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
030 S303 TRANSACTION REFERENCE C 1 1,8
0306 Transaction control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
040 S018 SCENARIO IDENTIFICATION C 1
0127 Scenario identification M an.14
0128 Scenario version number C an.3
0130 Scenario release number C an.3
0051 Controlling agency, coded C an.3
050 S305 DIALOGUE IDENTIFICATION C 1 2
0311 Dialogue identification M an.14
0342 Dialogue version number C an.3
0344 Dialogue release number C an.3
10 © ISO 2002 – All rights reserved
0051 Controlling agency, coded C an.3
060 S002 INTERCHANGE SENDER C 1 5
0004 Interchange sender identification M an.35
0007 Identification code qualifier C an.4
0008 Interchange sender internal
identification C an.35
0042 Interchange sender internal
sub-identification C an.35
070 S003 INTERCHANGE RECIPIENT C 1
0010 Interchange recipient identification M an.35
0007 Identification code qualifier C an.4
0014 Interchange recipient internal
identification C an.35
0046 Interchange recipient internal
sub-identification C an.35
080 S300 DATE AND/OR TIME OF INITIATION C 1
0338 Event date C n.8
0314 Event time C an.15
0336 Time offset C n4
090 0325 DUPLICATE INDICATOR C 1 a1 6
100 0035 TEST INDICATOR C 1 n1 7
DEPENDENCY NOTES:
1. D5(030, 020) If first, then all
2. D5(050, 020) If first, then all
OTHER NOTES:
3. S001/0002, shall be '4' to indicate this version of the syntax.
4. S302/0304, when provided by the responder, shall be returned by the
initiator throughout the dialogue.
5. S002/0004, may be same as S302/0303 for initiator of transaction.
6. 0325, only used if the interchange is a duplicate transfer.
7. 0035, set by the initiator if the dialogue is a test. Applies to every
subsequent message and service segment in the dialogue. Otherwise not
used.
8. Dialogue and transaction control can be accomplished through the dialogue
(S302) and transaction (S303) references. Optionally, if another means of
control is chosen, these two composite data elements need not be
utilised.
------------------------------------------------------------------------------
UIH INTERACTIVE MESSAGE HEADER
Function: To head, identify and specify a message.
Pos TAG Name S R Repr. Notes
010 S306 INTERACTIVE MESSAGE IDENTIFIER M 1
0065 Message type M an.6
0052 Message version number M an.3
0054 Message release number M an.3
0113 Message type sub-function identification C an.6
0051 Controlling agency, coded C an.3
0057 Association assigned code C an.6
020 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1,5
030 S302 DIALOGUE REFERENCE C 1 2,4,5
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
040 S301 STATUS OF TRANSFER - INTERACTIVE C 1
0320 Sender sequence number C n.6
0323 Transfer position, coded C a1
0325 Duplicate Indicator C a1
050 S300 DATE AND/OR TIME OF INITIATION C 1
0338 Event date C n.8
0314 Event time C an.15
0336 Time offset C n4
060 0035 TEST INDICATOR C 1 n1 3
NOTES:
1. The value in 0340 shall be unique within the interchange (except for a
duplicate transfer).
2. The value(s) in S302 shall be identical to the value(s) in S302 in the
preceding UIB.
3. 0035, when used, test applies to the message only.
4. Dialogue control can be accomplished through the dialogue reference
(S302). Optionally, if another means of control is chosen, this composite
data element need not be utilised.
5. A combination of 0340 and S302 may be used to identify uniquely a message.
------------------------------------------------------------------------------
*| UIR INTERACTIVE STATUS
Function: To report the status of the dialogue.
+ Note: To avoid endless loops, the UIR segment is not used to respond
to a UIR received with syntax errors.
Pos TAG Name S R Repr. Notes
010 0331 REPORT FUNCTION, CODED M 1 an.3
020 S307 STATUS INFORMATION C 9
0333 Status, coded C an.3
0332 Status C an.70
0335 Language, coded C an.3
030 S302 DIALOGUE REFERENCE C 1
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
040 S300 DATE AND/OR TIME OF INITIATION C 1
0338 Event date C n.8
0314 Event time C an.15
12 © ISO 2002 – All rights reserved
0336 Time offset C n4
050 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1,4
060 0800 PACKAGE REFERENCE NUMBER C 1 an.35 1,5
070 + 0085 SYNTAX ERROR, CODED C 1 an.3 2,3
080 + 0096 SEGMENT POSITION IN MESSAGE BODY C 1 n.6 2,3
090 + S011 DATA ELEMENT IDENTIFICATION C 1 3
0098 Erroneous data element position in
segment M n.3
0104 Erroneous component data element
position C n.3
0136 Erroneous data element occurrence C n.6
DEPENDENCY NOTES:
1. D1(050, 060) One and only one
2.+ D5(080, 070) If first, then all
3.+ D5(090, 070, 080) If first, then all
OTHER NOTES:
4. 0340, the value shall be identical to the value in 0340 in the UIH of a
message received by the sender of the UIR within the same dialogue.
5. 0800, the value shall be identical to the value in 0800 in the UNO
received by the sender of the UIR within the same dialogue.
------------------------------------------------------------------------------
UIT INTERACTIVE MESSAGE TRAILER
Function: To end and check the completeness of a message.
Pos TAG Name S R Repr. Notes
010 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1
020 0074 NUMBER OF SEGMENTS IN A MESSAGE C 1 n.10
NOTES:
1. 0340, the value shall be identical to the value in 0340 in the
corresponding UIH segment.
------------------------------------------------------------------------------
UIZ INTERACTIVE INTERCHANGE TRAILER
Function: To end and check the completeness of an interchange.
Pos TAG Name S R Repr. Notes
010 S302 DIALOGUE REFERENCE C 1 1
0300 Initiator control reference M an.35
0303 Initiator reference identification C an.35
0051 Controlling agency, coded C an.3
0304 Responder control reference C an.35
020 0036 INTERCHANGE CONTROL COUNT C 1 n.6
030 0325 DUPLICATE INDICATOR C 1 a1 2
NOTES:
1. S302, the value shall be identical to the value in the responder's
dialogue reference in S302 in the UIB segment.
2. 0325, only used if the interchange is a duplicate transfer.
------------------------------------------------------------------------------
UNB INTERCHANGE HEADER
Function: To identify an interchange.
Pos TAG Name S R Repr. Notes
010 S001 SYNTAX IDENTIFIER M 1 1
0001 Syntax identifier M a4
0002 Syntax version number M an1
0080 Service code list directory version
number C an.6
0133 Character encoding, coded C an.3
0076 Syntax release number C an2
020 S002 INTERCHANGE SENDER M 1 2
0004 Interchange sender identification M an.35
0007 Identification code qualifier C an.4
0008 Interchange sender internal
identification C an.35
0042 Interchange sender internal
sub-identification C an.35
030 S003 INTERCHANGE RECIPIENT M 1 2
0010 Interchange recipient identification M an.35
0007 Identification code qualifier C an.4
0014 Interchange recipient internal
identification C an.35
0046 Interchange recipient internal
sub-identification C an.35
040 S004 DATE AND TIME OF PREPARATION M 1
0017 Date M n8
0019 Time M n4
050 0020 INTERCHANGE CONTROL REFERENCE M 1 an.14 2
060 S005 RECIPIENT REFERENCE/PASSWORD DETAILS C 1
0022 Recipient reference/password M an.14
0025 Recipient reference/password qualifier C an2
070 0026 APPLICATION REFERENCE C 1 an.14
080 0029 PROCESSING PRIORITY CODE C 1 a1
090 0031 ACKNOWLEDGEMENT REQUEST C 1 n1
100 0032 INTERCHANGE AGREEMENT IDENTIFIER
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...