ISO 9735-10:2022

INTERNATIONAL ISO
STANDARD 9735-10
Third edition
2022-07
Electronic data interchange for
administration, commerce and
transport (EDIFACT) — Application
level syntax rules —
Part 10:
Syntax service directories (Syntax
version number: 4, Syntax release
number: 3)
Échange de données informatisé pour l'administration, le commerce
et le transport (EDIFACT) — Règles de syntaxe au niveau de
l'application —
Partie 10: Annuaires de syntaxe (numéro de version de syntaxe: 4,
numéro d'édition de syntaxe: 3)
Reference number
© ISO 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Conformance . 2
5 Syntax service directories .2
5.1 Service segment directory . 2
5.1.1 Service segment specification legend . 2
5.1.2 Dependency note identifiers . 3
5.1.3 Index of service segments by tag . 3
5.1.4 Index of service segments by name . 4
5.1.5 Service segment specifications . 6
5.2 Service composite data element directory . 27
5.2.1 Service composite data element specification legend . 27
5.2.2 Dependency note identifiers . 27
5.2.3 Index of service composite data elements by tag .28
5.2.4 Index of service composite data elements by name .29
5.2.5 Service composite data element specifications .30
5.3 Service simple data element directory . 37
5.3.1 General . 37
5.3.2 Service simple data element specification legend . 37
5.3.3 Index of service simple data elements by tag .38
5.3.4 Index of service simple data elements by name . 41
5.3.5 Service simple data element specifications.44
6 Syntax service code list directory .61
Annex A (informative) Overview of the syntax service code list directory .62
Bibliography .73
iii
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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/
iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 154, Processes, data elements and
documents in commerce, industry and administration, in collaboration with UN/EC (Joint syntax working
group).
This third edition cancels and replaces the second edition (ISO 9735-10:2014), which has been
technically revised.
The main changes are as follows:
— Annex A no longer lists all codes but refers to an external source.
A list of all parts in the ISO 9735 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
This document 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 document can be used in any application; but messages using these rules can only be referred to
as EDIFACT messages if they comply with other guidelines, rules and directories in the UNTDID. For
UN/EDIFACT, batch messages 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 document.
v
INTERNATIONAL STANDARD ISO 9735-10:2022(E)
Electronic data interchange for administration, commerce
and transport (EDIFACT) — Application level syntax
rules —
Part 10:
Syntax service directories (Syntax version number: 4,
Syntax release number: 3)
1 Scope
This document specifies the syntax service directories of all parts in the ISO 9735 series.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 9735-1, 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, 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, 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, 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, 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, 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, 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, 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, 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)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 9735-1 apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 Conformance
Whereas this document shall use a version number of “4” in the mandatory data element 0002 (Syntax
version number), and shall use a release number of “02” in the conditional data element 0076 (Syntax
release number), each of which appears 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 document:
— ISO 9735:1988: Syntax version number: 1
— ISO 9735:1988 (amended and reprinted in 1990): Syntax version number: 2
— ISO 9735:1988 and ISO 9735:1988/Amd 1:1992: Syntax version number: 3
— ISO 9735:1998 (all parts): 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 to identify 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 document.
Devices supporting this document are in conformance when they can create and/or interpret the data
structured and represented in conformance with this document.
Conformance to this document shall include conformance to ISO 9735-1, ISO 9735-2, ISO 9735-3,
ISO 9735-4, ISO 9735-5, ISO 9735-6, ISO 9735-7, ISO 9735-8 and ISO 9735-9.
When identified in this document, provisions defined in related standards shall form part of the
conformance criteria.
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 (compared with the previous edition of this document):
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
5.1.4 Index of service segments by name
Change indicators (compared with the previous edition of this document):
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 (compared with the previous edition of this document):
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

Details of the service segments are specified in Table 1 to Table 34.
Table 1 — Details of UCD DATA ELEMENT ERROR INDICATION segment
UCD DATA ELEMENT ERROR INDICATION segment
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/Remarks
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
Table 2 — Details of UCF GROUP RESPONSE segment
UCF GROUP RESPONSE segment
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. De-
pending 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/Remarks
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
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 REMARKS:
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.
Table 2 (continued)
UCF GROUP RESPONSE segment
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. De-
pending 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/Remarks
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,4
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 REMARKS:
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.
Table 3 — Details of UCI INTERCHANGE RESPONSE segment:
UCI INTERCHANGE RESPONSE segment:
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 ap-
pear 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/Remarks
010 0020 INTERCHANGE CONTROL REFERENCE M 1 an.14
020 S002 INTERCHANGE SENDER M 1
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 REMARKS:
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.
Table 3 (continued)
UCI INTERCHANGE RESPONSE segment:
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 ap-
pear 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/Remarks
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,4
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 REMARKS:
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.
Table 4 — Details of UCM MESSAGE/PACKAGE RESPONSE segment
UCM MESSAGE/PACKAGE RESPONSE segment
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/Remarks
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,7
050 0135 SERVICE SEGMENT TAG, CODED C 1 an.3 4,5,6,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 REMARKS:
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.
Table 5 — Details of UCS SEGMENT ERROR INDICATION segment
UCS SEGMENT ERROR INDICATION segment
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/Remarks
010 0096 SEGMENT POSITION IN MESSAGE BODY M 1 n.6
020 0085 SYNTAX ERROR, CODED C 1 an.3 1
REMARKS:
1 0085, shall contain a value only if the error pertains to the segment identified by data element 0096.
Table 6 — Details of UGH ANTI-COLLISION SEGMENT GROUP HEADER segment
UGH ANTI-COLLISION SEGMENT GROUP HEADER segment
Function: To head, identify and specify an anti-collision segment group.
Pos TAG Name S R Repr. Notes/Remarks
010 0087 ANTI-COLLISION SEGMENT GROUP IDENTIFICATION M 1 an.4 1
REMARKS:
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.
Table 7 — Details of UGT ANTI-COLLISION SEGMENT GROUP TRAILER segment
UGT ANTI-COLLISION SEGMENT GROUP TRAILER segment
Function: To end and check the completeness of an anti-collision segment group.
Pos TAG Name S R Repr. Notes/Remarks
010 0087 ANTI-COLLISION SEGMENT GROUP IDENTIFICATION M 1 an.4 1
REMARKS:
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.
Table 8 — Details of UIB INTERACTIVE INTERCHANGE HEADER segment
UIB INTERACTIVE INTERCHANGE HEADER segment
Function: To head and identify an interchange.
Pos TAG Name S R Repr. Notes/Remarks
010 S001 SYNTAX IDENTIFIER M 1 3
0001 Syntax identifier M a4
0002 Syntax version number M an1
DEPENDENCY NOTES:
1 D5(030, 020) If first, then all.
2 D5(050, 020) If first, then all.
OTHER REMARKS:
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 utilized.
Table 8 (continued)
UIB INTERACTIVE INTERCHANGE HEADER segment
Function: To head and identify an interchange.
Pos TAG Name S R Repr. Notes/Remarks
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
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
DEPENDENCY NOTES:
1 D5(030, 020) If first, then all.
2 D5(050, 020) If first, then all.
OTHER REMARKS:
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 utilized.
Table 8 (continued)
UIB INTERACTIVE INTERCHANGE HEADER segment
Function: To head and identify an interchange.
Pos TAG Name S R Repr. Notes/Remarks
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 REMARKS:
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 utilized.
Table 9 — Details of UIH INTERACTIVE MESSAGE HEADER segment
UIH INTERACTIVE MESSAGE HEADER segment
Function: To head, identify and specify a message.
Pos TAG Name S R Repr. Notes/Remarks
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
REMARKS:
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 utilized.
5 A combination of 0340 and S302 may be used to identify uniquely a message.
Table 9 (continued)
UIH INTERACTIVE MESSAGE HEADER segment
Function: To head, identify and specify a message.
Pos TAG Name S R Repr. Notes/Remarks
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
REMARKS:
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 utilized.
5 A combination of 0340 and S302 may be used to identify uniquely a message.
Table 10 — Details of UIR INTERACTIVE STATUS segment
UIR INTERACTIVE STATUS segment
Function: To report the status of the dialogue.
Pos TAG Name S R Repr. Notes/Remarks
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
GENERAL REMARK:
To avoid endless loops, the UIR segment is not used to respond to a UIR received with syntax errors.
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 REMARKS:
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.
Table 10 (continued)
UIR INTERACTIVE STATUS segment
Function: To report the status of the dialogue.
Pos TAG Name S R Repr. Notes/Remarks
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
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
GENERAL REMARK:
To avoid endless loops, the UIR segment is not used to respond to a UIR received with syntax errors.
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 REMARKS:
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.
Table 11 — Details of UIT INTERACTIVE MESSAGE TRAILER segment
UIT INTERACTIVE MESSAGE TRAILER segment
Function: To end and check the completeness of a message.
Pos TAG Name S R Repr. Notes/Remarks
010 0340 INTERACTIVE MESSAGE REFERENCE NUMBER C 1 an.35 1
020 0074 NUMBER OF SEGMENTS IN A MESSAGE C 1 n.10
REMARKS:
1 0340, the value shall be identical to the value in 0340 in the corresponding UIH segment.
Table 12 — Details of UIZ INTERACTIVE INTERCHANGE TRAILER segment
UIZ INTERACTIVE INTERCHANGE TRAILER segment
Function: To end and check the completeness of an interchange.
Pos TAG Name S R Repr. Notes/Remarks
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
REMARKS:
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.
Table 13 — Details of UNB INTERCHANGE HEADER segment
UNB INTERCHANGE HEADER segment
Function: To identify an interchange.
Pos TAG Name S R Repr. Notes/Remarks
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
REMARKS:
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.
Table 13 (continued)
UNB INTERCHANGE HEADER segment
Function: To identify an interchange.
Pos TAG Name S R Repr. Notes/Remarks
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
REMARKS:
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.
Table 14 — Details of UNE GROUP TRAILER segment
UNE GROUP TRAILER segment
Function: To end and check the completeness of a group.
Pos TAG Name S R Repr. Notes/Remarks
010 0060 GROUP CONTROL COUNT M 1 n.6
020 0048 GROUP REFERENCE NUMBER M 1 an.14 1
REMARKS:
1 0048, the value shall be identical to the value in 0048 in the corresponding UNG segment.
Table 15 — Details of UNG GROUP HEADER segment
UNG GROUP HEADER segment
Function: To head, identify and specify a group of messages and/or packages, which may be used for internal
routing and which may contain one or more message types and/or packages.
Pos TAG Name S R Repr. Notes/Remarks
010 X 0038 MESSAGE GROUP IDENTIFICATION C 1 an.6 1,2,4
020 S006 APPLICATION SENDER IDENTIFICATION C 1 5
0040 Application sender identification M an.35
0007 Identification code qualifier C an.4
030 S007 APPLICATION RECIPIENT IDENTIFICATION C 1 5
0044 Application recipient identification M an.35
0007 Identification code qualifier C an.4
DEPENDENCY NOTES:
1 D2(010, 060, 070) All or none.
OTHER REMARKS:
2 This data element is only used if the following conditions apply:
i) the group contains messages only, and
ii) the messages are of a single message type.
3 S004, if S004 is not present in UNG, the date and time of preparation is the same as indicated for the interchange in
S004 in UNB.
4 This data element will be deleted from the UNG segment in the next version of the standard. Therefore, its use in UNG is
not recommended.
5 The combination of the values carried in data elements S006, S007 and 0048 shall be used to identify uniquely the
group within its interchange, for the purpose of acknowledgement.
Table 15 (continued)
UNG GROUP HEADER segment
Function: To head, identify and specify a group of messages and/or packages, which may be used for internal
routing and which may contain one or more message types and/or packages.
Pos TAG Name S R Repr. Notes/Remarks
...