Return to Stylus Studio EDIFACT home page. Return to Stylus Studio EDIFACT D96A Messages page. Directory definition message
0. INTRODUCTIONThis 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. SCOPE1.1. Functional DefinitionThis Directory definition message (DIRDEF) permits the transfer of the contents of a UN/EDIFACT Directory set or parts thereof. 1.2. Field of ApplicationThe 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. PrinciplesThe 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. REFERENCESSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONSSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Data Segment ClarificationThis section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements. 0010 | UNH, Message headerA 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 messageA segment to indicate the beginning of the message and to transmit function, type and number of the message. 0030 DII, Directory identificationA segment specifying the identity of the directory set and giving its language and maintenance operation. 0040 DTM, Date/time/periodA segment specifying dates related to the directory set, such as date of approval, date of submission or WP.4 acceptance date. 0050 FTX, Free textA 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 addressA 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 informationA 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 contactA 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 identificationA segment identifying a message type to be specified. 0130 FTX, Free textA 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 detailsA segment specifying the usage of a segment in a message type structure. 0160 FTX, Free textA 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 detailsA segment specifying the usage of a segment group in a message type structure. 0190 FTX, Free textA 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 identificationA segment identifying a segment type and specifying its class and maintenance operation. 0220 FTX, Free textA segment specifying the name and functional definition of a segment type. 0230 ELU, Data element usage detailsA 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 identificationA segment identifying a composite data element and specifying its class and maintenance operation. 0260 FTX, Free textA segment specifying the name and functional definition of a composite data element type. 0270 ELU, Data element usage detailsA 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 detailsA segment identifying a simple data element and giving related information. 0300 FTX, Free textA 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 identificationA segment specifying a code set. In DIRDEF data element 9434 shall not be used. 0330 FTX, Free textA 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 definitionA segment specifying a code value. 0360 FTX, Free textA segment specifying the name and functional definition of a code value. 0370 UNT, Message trailerA 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)
4.3. Message structure4.3.1. Segment table
Return to Stylus Studio EDIFACT D96A Messages page. |
![]() |
Site Map | Privacy Policy | Terms of Use | Trademarks |