| Version: | D |
|---|---|
| Release: | 97B |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 97-07-25 |
| SOURCE: | UN/ECE Secretariat |
|
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 |
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.
This Directory definition message (DIRDEF) permits the transfer of the contents of a UN/EDIFACT Directory set or parts thereof.
The Directory definition message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
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.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.
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:
| Data element | 0065 | DIRDEF |
| 0052 | D | |
| 0054 | 97B | |
| 0051 | UN |
A segment to indicate the beginning of the message and to transmit function, type and number of the message.
A segment specifying the identity of the directory set and giving its language and maintenance operation.
A segment specifying dates related to the directory set, such as date of approval, date of submission or WP.4 acceptance date.
A segment providing free text information related to the directory set.
A group of segments identifying the parties involved in the transaction with associated information.
A segment identifying the parties involved in the transaction, e.g. originator, requestor or secretariat.
A group of segments identifying a person or a department and identifying communication type(s) and number(s).
A segment identifying a person or a department for the party specified in the leading NAD segment to whom the communication should be directed.
A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment.
A group of segments providing a message type directory.
A segment identifying a message type to be specified.
A segment providing textual information related to the message type, namely: message type name, Introduction, Scope, Functional definition, Principles, References and Terms and definitions.
This segment is used to indicate the release date of a message, as indicated on the cover page of the boilerplate.
A group of segments specifying a message type structure and its related functional definition.
A segment specifying the usage of a segment in a message type structure.
A segment providing textual information about segment usage. This information comprises part of the 'Data segment clarification' section.
A group of segments identifying a segment group and providing details about segment group usage.
A segment specifying the usage of a segment group in a message type structure.
A segment providing the textual information about segment group usage. This information comprises part of the 'Data Segment Clarification' section.
A group of segments providing a segment directory.
A segment identifying a segment type and specifying its class and maintenance operation.
A segment specifying the name and functional definition of a segment type.
A segment specifying the contents of data elements in a segment type.
To identify the direct relationship between the data and/or information contained in one segment and the data and/or information contained in one or more other segments.
A group of segments providing a composite data element directory.
A segment identifying a composite data element and specifying its class and maintenance operation.
A segment specifying the name and functional definition of a composite data element type.
A segment specifying component data elements in a composite data element and its related information.
A group of segments providing a data element directory.
A segment identifying a simple data element and giving related information.
A segment specifying the name and functional definition of a simple data element.
A group of segments providing a code list directory.
A segment specifying a code set. In DIRDEF data element 9434 shall not be used.
A segment providing textual information related to the code list.
A group of segments specifying a code value and its functional definition.
A segment specifying a code value.
A segment specifying the name and functional definition of a code value.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| 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 | |
| REL | Relationship | |
| SEG | Segment identification | |
| SGU | Segment usage details | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─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) |
| │─├─DTM Date/time/period | ×1 | (M) |
| │─└─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) |
| │─└─REL Relationship | ×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) |