Return to EDIFACT D96B Messages page.
UN/EDIFACT
DRAFT RECOMMENDATION
Directory definition message
|
This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4.
Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued.
The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags.
|
| Message Type: | DIRDEF |
|---|
| Version: | D |
|---|
| Release: | 96B |
|---|
| Contr. Agency: | UN |
|---|
| Status: | 1 |
|---|
| Revision: | 1 |
|---|
| Date: | 96-07-04 |
|---|
| SOURCE: | UN/ECE Secretariat |
|---|
CONTENTS
Directory definition message
- INTRODUCTION
- SCOPE
- Functional definition
- Field of application
- Principles
- REFERENCES
- TERMS AND DEFINITIONS
- MESSAGE DEFINITION
- Data segment clarification
- Data segment index (alphabetical sequence)
- Message structure
- Segment table
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction
|
This message also occurs in the following versions of this standard:
D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
0. INTRODUCTION
This specification provides the definition of the Directory definition message (DIRDEF) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
1. SCOPE
1.1. Functional Definition
This Directory definition message (DIRDEF) permits the transfer of the contents of a UN/EDIFACT Directory set or parts thereof.
1.2. Field of Application
The Directory definition message may be used for both national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.
1.3. Principles
The Message allows the transmission of a UN/EDIFACT Directory set or parts thereof. A UN/EDIFACT Directory Set comprises:
-Message type directory -Segment directory -Composite data element directory -Simple data element directory -Code list directory
One occurrence of the message can contain only one version of a UN/EDIFACT Directory set or parts thereof.
2. REFERENCES
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1. Data Segment Clarification
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
0010 UNH, Message header
A service segment starting and uniquely identifying a message. The message type code for the Directory definition message is DIRDEF. Note: Directory definition messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of message
A segment to indicate the beginning of the message and to transmit function, type and number of the message. 0030 DII, Directory identification
A segment specifying the identity of the directory set and giving its language and maintenance operation. 0040 DTM, Date/time/period
A segment specifying dates related to the directory set, such as date of approval, date of submission or WP.4 acceptance date. 0050 FTX, Free text
A segment providing free text information related to the directory set. 0060 Segment Group 1: NAD-SG2A group of segments identifying the parties involved in the transaction with associated information. 0070 NAD, Name and address
A segment identifying the parties involved in the transaction, e.g. originator, requestor or secretariat. 0080 Segment Group 2: CTA-COMA group of segments identifying a person or a department and identifying communication type(s) and number(s). 0090 CTA, Contact information
A segment identifying a person or a department for the party specified in the leading NAD segment to whom the communication should be directed. 0100 COM, Communication contact
A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment. 0110 Segment Group 3: MSG-FTX-SG4A group of segments providing a message type directory. 0120 MSG, Message type identification
A segment identifying a message type to be specified. 0130 FTX, Free text
A segment providing textual information related to the message type, namely: message type name, Introduction, Scope, Functional definition, Principles, References and Terms and definitions. 0140 Segment Group 4: SGU-FTX-SG5A group of segments specifying a message type structure and its related functional definition. 0150 SGU, Segment usage details
A segment specifying the usage of a segment in a message type structure. 0160 FTX, Free text
A segment providing textual information about segment usage. This information comprises part of the 'Data segment clarification' section. 0170 Segment Group 5: GRU-FTXA group of segments identifying a segment group and providing details about segment group usage. 0180 GRU, Segment group usage details
A segment specifying the usage of a segment group in a message type structure. 0190 FTX, Free text
A segment providing the textual information about segment group usage. This information comprises part of the 'Data Segment Clarification' section. 0200 Segment Group 6: SEG-FTX-ELUA group of segments providing a segment directory. 0210 SEG, Segment identification
A segment identifying a segment type and specifying its class and maintenance operation. 0220 FTX, Free text
A segment specifying the name and functional definition of a segment type. 0230 ELU, Data element usage details
A segment specifying the contents of data elements in a segment type. 0240 Segment Group 7: CMP-FTX-ELUA group of segments providing a composite data element directory. 0250 CMP, Composite data element identification
A segment identifying a composite data element and specifying its class and maintenance operation. 0260 FTX, Free text
A segment specifying the name and functional definition of a composite data element type. 0270 ELU, Data element usage details
A segment specifying component data elements in a composite data element and its related information. 0280 Segment Group 8: ELM-FTXA group of segments providing a data element directory. 0290 ELM, Simple data element details
A segment identifying a simple data element and giving related information. 0300 FTX, Free text
A segment specifying the name and functional definition of a simple data element. 0310 Segment Group 9: CDS-FTX-SG10A group of segments providing a code list directory. 0320 CDS, Code set identification
A segment specifying a code set. In DIRDEF data element 9434 shall not be used. 0330 FTX, Free text
A segment providing textual information related to the code list. 0340 Segment Group 10: CDV-FTXA group of segments specifying a code value and its functional definition. 0350 CDV, Code value definition
A segment specifying a code value. 0360 FTX, Free text
A segment specifying the name and functional definition of a code value. 0370 UNT, Message trailer
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
4.2. Data segment index (Alphabetical sequence by tag)
|
BGM |
Beginning of message |
|
CDS |
Code set identification |
|
CDV |
Code value definition |
|
CMP |
Composite data element identification |
|
COM |
Communication contact |
|
CTA |
Contact information |
|
DII |
Directory identification |
|
DTM |
Date/time/period |
|
ELM |
Simple data element details |
|
ELU |
Data element usage details |
|
FTX |
Free text |
|
GRU |
Segment group usage details |
|
MSG |
Message type identification |
|
NAD |
Name and address |
|
SEG |
Segment identification |
|
SGU |
Segment usage details |
|
UNH |
Message header |
|
UNT |
Message trailer |
4.3. Message structure
4.3.1. Segment table
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (C) |
| ├─DII Directory identification | ×1 | (M) |
| ├─DTM Date/time/period | ×9 | (C) |
| ├─FTX Free text | ×9 | (C) |
| ├─Segment Group 1 | ×9 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─└─Segment Group 2 | ×9 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×9 | (C) |
| ├─Segment Group 3 | ×9999 | (C) |
| │─├─MSG Message type identification | ×1 | (M) |
| │─├─FTX Free text | ×999 | (C) |
| │─└─Segment Group 4 | ×999 | (C) |
| │───├─SGU Segment usage details | ×1 | (M) |
| │───├─FTX Free text | ×99 | (C) |
| │───└─Segment Group 5 | ×1 | (C) |
| │─────├─GRU Segment group usage details | ×1 | (M) |
| │─────└─FTX Free text | ×99 | (C) |
| ├─Segment Group 6 | ×9999 | (C) |
| │─├─SEG Segment identification | ×1 | (M) |
| │─├─FTX Free text | ×9 | (C) |
| │─└─ELU Data element usage details | ×99 | (C) |
| ├─Segment Group 7 | ×9999 | (C) |
| │─├─CMP Composite data element identification | ×1 | (M) |
| │─├─FTX Free text | ×9 | (C) |
| │─└─ELU Data element usage details | ×99 | (C) |
| ├─Segment Group 8 | ×9999 | (C) |
| │─├─ELM Simple data element details | ×1 | (M) |
| │─└─FTX Free text | ×9 | (C) |
| ├─Segment Group 9 | ×9999 | (C) |
| │─├─CDS Code set identification | ×1 | (M) |
| │─├─FTX Free text | ×9 | (C) |
| │─└─Segment Group 10 | ×9999 | (C) |
| │───├─CDV Code value definition | ×1 | (M) |
| │───└─FTX Free text | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |
Return to EDIFACT D96B Messages page.
|