DIRDEF Directory definition

TBG16 Entry Point

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.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. 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 21A 0051 UN

  2. A segment to indicate the beginning of the message and to transmit function, type and number of the message.

  3. A segment specifying the identity of the directory set and giving its language and maintenance operation.

  4. A segment specifying dates related to the directory set, such as date of approval, date of submission or WP.4 acceptance date.

  5. A segment providing free text information related to the directory set.

  6. Segment group 1
    Repeat 9

    1. A segment identifying the parties involved in the transaction, e.g. originator, requestor or secretariat.

    2. Segment group 2
      Repeat 9

      1. A segment identifying a person or a department for the party specified in the leading NAD segment to whom the communication should be directed.

      2. A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment.

  7. Segment group 3
    Repeat 9999

    1. A segment identifying a message type to be specified.

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

    3. A segment providing textual information related to the message type, namely: message type name, Introduction, Scope, Functional definition, Principles, References and Terms and definitions.

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

    5. Segment group 4
      Repeat 999

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

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

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

      4. Segment group 5
        Repeat 1

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

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

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

    6. Segment group 6
      Repeat 99

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

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

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

      4. A segment to provide the change indicators at the note level.

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

  8. Segment group 7
    Repeat 9999

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

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

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

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

    5. Segment group 8
      Repeat 99

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

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

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

      4. A segment to provide the change indicators at the note level.

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

  9. Segment group 9
    Repeat 9999

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

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

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

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

    5. Segment group 10
      Repeat 99

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

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

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

      4. A segment to provide the change indicators at the note level.

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

  10. Segment group 11
    Repeat 9999

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

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

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

  11. Segment group 12
    Repeat 9999

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

    2. A segment providing textual information related to the code list.

    3. Segment group 13
      Repeat 9999

      1. A segment specifying a code value.

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

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

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

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.