Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D99B Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Directory definition message

Version:D
Release:99B
Contr. Agency:UN
Revision:4
Date:1999-09-11
SOURCE:UN/ECE Secretariat

CONTENTS
Directory definition message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
    2. Segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, 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 or American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 Directory set or parts thereof.


1.2. Field of Application

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.


1.3. Principles

The Message allows the transmission of a UN/EDIFACT or X12 Directory set, or parts thereof. A UN/EDIFACT or ANSI ASC X12 Directory Set comprises:

-Message type or Transaction Set 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 or ANSI ASC X12 Directory set, or parts thereof.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Segment Clarification

This section should be read in conjunction with the segment table which indicates 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:

Data element0065DIRDEF
0052D
005499B
0051UN

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-SG2

A 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-COM

A 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-ATT-FTX-DTM-SG4-SG6

A group of segments providing a message type directory.

0120 MSG, Message type identification

A segment identifying a message type to be specified.

0130 ATT, Attribute

A segment used to specify an attribute related to a message type. It may indicate whether the message is a batch or an interactive message, or may indicate the specific type of maintenance applied to the message in the current release of the message type directory.

0140 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.

0150 DTM, Date/time/period

This segment is used to indicate the release date of a message, as indicated on the cover page of the boilerplate.

0160 Segment Group 4: SGU-ATT-FTX-SG5

A group of segments specifying a message type structure and its related functional definition.

0170 SGU, Segment usage details

A segment specifying the usage of a segment in a message type structure.

0180 ATT, Attribute

A segment used to specify an attribute related to the usage of a segment in a message type structure. It may indicate the specific type of maintenance applied to the segment within the message structure in the current release of the message type directory.

0190 FTX, Free text

A segment providing textual information about segment usage. This information comprises part of the 'Data segment clarification' section.

0200 Segment Group 5: GRU-ATT-FTX

A group of segments identifying a segment group and providing details about segment group usage.

0210 GRU, Segment group usage details

A segment specifying the usage of a segment group in a message type structure.

0220 ATT, Attribute

A segment used to specify an attribute related to the usage of a segment group in a message type structure. It may indicate the specific type of maintenance applied to the segment group within the message structure in the current release of the message type directory.

0230 FTX, Free text

A segment providing the textual information about segment group usage. This information comprises part of the 'Data Segment Clarification' section.

0240 Segment Group 6: FNT-REL-GIR-FTX

A group of segments used to specify dependency notes or other notes about the usage of segments and/or segment groups in a message type structure.

0250 FNT, Footnote

A segment to provide the footnote identification for a dependency note or other note that is applicable to one or more segments and/or segment groups in the message type structure.

0260 REL, Relationship

A segment to provide the type of dependency relationship, where one exists.

0270 GIR, Related identification numbers

A segment to provide the position number(s) for segments and/or segment groups to which a dependency note or other note applies.

0280 FTX, Free text

A segment to provide a free text description of the dependency note or other note.

0290 Segment Group 7: SEG-ATT-FTX-ELU-SG8

A group of segments providing a segment directory.

0300 SEG, Segment identification

A segment identifying a segment type and specifying its class and maintenance operation.

0310 ATT, Attribute

A segment used to specify an attribute related to a segment type. It may indicate whether the segment is a batch or an interactive segment, or may indicate the specific type of maintenance applied to the segment in the current release of the segment directory.

0320 FTX, Free text

A segment specifying the name and functional definition of a segment type.

0330 ELU, Data element usage details

A segment specifying the contents of data elements in a segment type.

0340 Segment Group 8: FNT-REL-GIR-FTX

A group of segments used to specify dependency notes or other notes about the usage of data elements in a segment type.

0350 FNT, Footnote

A segment to provide the footnote identification for a dependency note or other note that is applicable to one or more data elements in a segment type.

0360 REL, Relationship

A segment to provide the type of dependency relationship, where one exists.

0370 GIR, Related identification numbers

A segment to provide the position number(s) for a data element to which a dependency note or other note applies.

0380 FTX, Free text

A segment to provide a free text description of the dependency note or other note.

0390 Segment Group 9: CMP-ATT-FTX-ELU-SG10

A group of segments providing a composite data element directory.

0400 CMP, Composite data element identification

A segment identifying a composite data element and specifying its class and maintenance operation.

0410 ATT, Attribute

A segment used to specify an attribute related to a composite data element type. It may indicate whether the composite data element is a batch or an interactive composite data element, or may indicate the specific type of maintenance applied to the composite data element in the current release of the composite data element directory.

0420 FTX, Free text

A segment specifying the name and functional definition of a composite data element type.

0430 ELU, Data element usage details

A segment specifying component data elements in a composite data element and its related information.

0440 Segment Group 10: FNT-REL-GIR-FTX

A group of segments used to specify dependency notes or other notes about the usage of component data elements in a composite data element type.

0450 FNT, Footnote

A segment to provide the footnote identification for a dependency note or other note that is applicable to one or more component data elements in a composite data element type.

0460 REL, Relationship

A segment to provide the type of dependency relationship, where one exists.

0470 GIR, Related identification numbers

A segment to provide the position number(s) for a data element to which a dependency note or other note applies.

0480 FTX, Free text

A segment to provide a free text description of the dependency note or other note.

0490 Segment Group 11: ELM-ATT-FTX

A group of segments providing a data element directory.

0500 ELM, Simple data element details

A segment identifying a simple data element and giving related information.

0510 ATT, Attribute

A segment used to specify an attribute related to a simple data element type. It may indicate whether the data element is a batch, or an interactive, or both a batch and an interactive simple data element. It may indicate the specific type of maintenance applied to the data element in the current release of the simple data element directory.

0520 FTX, Free text

A segment specifying the name and functional definition of a simple data element.

0530 Segment Group 12: CDS-FTX-SG13

A group of segments providing a code list directory.

0540 CDS, Code set identification

A segment specifying a code set. In DIRDEF data element 9434 shall not be used.

0550 FTX, Free text

A segment providing textual information related to the code list.

0560 Segment Group 13: CDV-ATT-FTX

A group of segments specifying a code value and its functional definition.

0570 CDV, Code value definition

A segment specifying a code value.

0580 ATT, Attribute

A segment used to specify an attribute related to a code value. It may indicate the specific type of maintenance applied to the code value in the current release of the code list directory.

0590 FTX, Free text

A segment specifying the name and functional definition of a code value.

0600 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.


4.2. Segment index (Alphabetical sequence by tag)

ATT Attribute
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
FNT Footnote
FTX Free text
GIR Related identification numbers
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

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)
├─ATT Attribute ×99 (C)
├─FTX Free text ×999 (C)
├─DTM Date/time/period ×1 (M)
├─Segment Group 4 ×999 (C)
├─SGU Segment usage details ×1 (M)
├─ATT Attribute ×9 (C)
├─FTX Free text ×99 (C)
└─Segment Group 5 ×1 (C)
──├─GRU Segment group usage details ×1 (M)
──├─ATT Attribute ×9 (C)
──└─FTX Free text ×99 (C)
└─Segment Group 6 ×99 (C)
──├─FNT Footnote ×1 (M)
──├─REL Relationship ×1 (C)
──├─GIR Related identification numbers ×9 (C)
──└─FTX Free text ×9 (C)
├─Segment Group 7 ×9999 (C)
├─SEG Segment identification ×1 (M)
├─ATT Attribute ×9 (C)
├─FTX Free text ×9 (C)
├─ELU Data element usage details ×99 (C)
└─Segment Group 8 ×99 (C)
──├─FNT Footnote ×1 (M)
──├─REL Relationship ×1 (C)
──├─GIR Related identification numbers ×9 (C)
──└─FTX Free text ×9 (C)
├─Segment Group 9 ×9999 (C)
├─CMP Composite data element identification ×1 (M)
├─ATT Attribute ×9 (C)
├─FTX Free text ×9 (C)
├─ELU Data element usage details ×99 (C)
└─Segment Group 10 ×99 (C)
──├─FNT Footnote ×1 (M)
──├─REL Relationship ×1 (C)
──├─GIR Related identification numbers ×9 (C)
──└─FTX Free text ×9 (C)
├─Segment Group 11 ×9999 (C)
├─ELM Simple data element details ×1 (M)
├─ATT Attribute ×9 (C)
└─FTX Free text ×9 (C)
├─Segment Group 12 ×9999 (C)
├─CDS Code set identification ×1 (M)
├─FTX Free text ×9 (C)
└─Segment Group 13 ×9999 (C)
──├─CDV Code value definition ×1 (M)
──├─ATT Attribute ×9 (C)
──└─FTX Free text ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D99B Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.