Service simple data element directory by tag 

  EDIFACT 

Syntax Version 3

  

Change indicators

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

Repr

Syntax identifier

Coded identification of the agency controlling a syntax and syntax level used in an interchange.

Notes:
1. a3, upper case, Controlling Agency (e.g. UNO=UN/ECE) and a1 stating level (e.g. A) (which together give UNOA).

a4

Syntax version number

Version number of the syntax identified in the syntax identifier (0001)

Notes:
1. Increments 1 for each version.

n1

Sender identification

Name or coded representation of the sender of a data interchange.

Notes:
1. Code or name as specified in IA.

an..35

Partner identification code qualifier

Qualifier referring to the source of codes for the identifiers of interchanging partners.

Notes:
1. Used with sender/recipient identification code.

an..4

Address for reverse routing

Address specified by the sender of an interchange to be included by the recipient in the response interchanges to facilitate internal routing.

an..14

Recipient identification

Name or coded representation of the recipient of a data interchange.

Notes:
1. Code or name as specified in IA.

an..35

Service segment tag, coded

Code identifying a segment.

a3

Routing address

Address specified by the recipient of an interchange to be included by the sender and used by the recipient for routing of received interchanges inside his organization.

Notes:
1. If used, normally coded sub-address for onward routing.

an..14

Date of preparation

Local date when an interchange or a functional group was prepared.

Notes:
1. YYMMDD

n6

Time of preparation

Local time of day when an interchange or a functional group was prepared.

Notes:
1. HHMM

n4

Interchange control reference

Unique reference assigned by the sender to an interchange.

Notes:
1. Shall be identical in UNB and UNZ.

an..14

Recipient's reference/password

Unique reference assigned by the recipient to the data interchange or a password to the recipient's system or to a third party network as specified in the partners interchange agreement.

Notes:
1. As specified in IA. May be password to recipient's system or to third party network.

an..14

Recipient's reference/password qualifier

Qualifier for the recipient's reference or password.

Notes:
1. Used if specified in IA.

an2

Application reference

Identification of the application area assigned by the sender, to which the messages in the interchange relate e.g. the message identifier if all the messages in the interchange are of the same type.

Notes:
1. Optionally message identification if the message interchange contains only one type of message.

an..14

Processing priority code

Code determined by the sender requesting processing priority for the interchange.

Notes:
1. Used if specified in IA.

a1

Acknowledgement request

Code determined by the sender for acknowledgement of the interchange.

Notes:
1. Set = 1 if sender requests acknowledgement, i.e. UNB and UNZ segments received and identified.

n1

Communications agreement ID

Identification by name or code of the type of agreement under which the interchange takes place.

Notes:
1. If used, to identify type of communication agreement controlling the interchange, e.g. Customs or ECE agreement. Code or name as specified in IA.

an..35

Test indicator

Indication that the interchange is a test.

Notes:
1. Set = 1 if the interchange is a test. Otherwise not used.

n1

Interchange control count

The count either of the number of messages or, if used, of the number of functional groups in an interchange. One of these counts shall appear.

n..6

Functional group identification

Identification of the one type of message in a functional group.

an..6

Sender identification

Code or name identifying the division, department etc. within the originating sender's organization.

an..35

Recipient's identification

Code or name identifying the division, department etc. within the recipient's organization for which the group of messages is intended.

an..35

Functional group reference number

Unique reference number assigned by the sender's division, department etc.

Notes:
1. Shall be identical in UNG and UNE.

an..14

Controlling agency

Code to identify the agency controlling the specification, maintenance and publication of the message type.

an..2

Message version number

Version number of a message type.

Notes:
1. Version number of the message type. If UNG is used, 0052 version number of the message type in the functional group shall be identical.

an..3

Message release number

Release number within the current message type version number (0052).

Notes:
1. The representation of 0054 was specified as n..3 in version 1 of ISO 9735.

an..3

Association assigned code

A code assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message.

an..6

Application password

Password to the recipient's division, department or sectional system (if required).

an..14

Number of messages

A count of the number of messages in a functional group.

n..6

Message reference number

Unique message reference assigned by the sender.

Notes:
1. Shall be identical in UNH and UNT.

an..14

Message type

Code identifying a type of message and assigned by its controlling agency.

Notes:
1. Type of message being transmitted.

an..6

Common access reference

Reference serving as a key to relate all subsequent transfers of data to the same business case or file.

Notes:
1. Key to relate all subsequent transfers of data to the same business case or file. Within the 35 characters the IA may specify component elements.

an..35

Sequence of transfers

Number assigned by the sender indicating the numerical sequence of one or more transfers.

Notes:
1. Starts at 1 and is incremented by 1 for each transfer.

n..2

First and last transfer

Indication used for the first and last message in a sequence of the same type of message relating to the same topic.

Notes:
1. Must be present if more than one transfer is foreseen.

a1

Number of segments in the message

Control count of number of segments in a message.

Notes:
1. Control count including UNH and UNT.

n..6

Text reference code

Qualifies and identifies the purpose and function of the segment if indicated in the message specification.

an3

Free form text

Not machine-processable information.

an..70

Section identification

Separates sections in a message.

a1

Action, coded

A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange.

an..3

Syntax error, coded

A code indicating the syntax error detected.

an..3

Segment position in message

The numerical count position of a specific segment that is within the actual received message. The numbering starts with, and includes, the UNH segment as segment number 1. To identify a segment that contains an error, this is the numerical count position of that segment. To report that a segment is missing, this is the numerical count position of the last segment that was processed before the position where the missing segment was expected to be. A missing segment group is denoted by identifying the first segment in the group as missing.

n..6

Erroneous data element position in segment

The numerical count position of the simple or composite data element in error. The segment code and each following simple or composite data element defined in the segment description shall cause the count to be incremented. The segment tag has position number 1.

n..3

Erroneous component data element position

The numerical count position of the component data element in error. Each component data element position defined in the composite data element description shall cause the count to be incremented. The count starts at 1.

n..3

Date 

23.06.2021