© 2018 ProgM

Nachricht DIRDEF: D

NameDIRDEF
VersionD
Release18A
BeschreibungDirectory definition message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A 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 D A UNMandatory
BGM0A segment to indicate the beginning of the message and to transmit function, type and number of the message.Mandatory
DII0A segment specifying the identity of the directory set and giving its language and maintenance operation.Mandatory
DTM0A segment specifying dates related to the directory set, such as date of approval, date of submission or WP.4 acceptance date.Optional
FTX0A segment providing free text information related to the directory set.Optional
SG10SG1Optional
NAD1A segment identifying the parties involved in the transaction, e.g. originator, requestor or secretariat.Mandatory
SG21SG2Mandatory
CTA2A segment identifying a person or a department for the party specified in the leading NAD segment to whom the communication should be directed.Mandatory
COM2A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment.Optional
SG30SG3Optional
MSG1A segment identifying a message type to be specified.Mandatory
ATT1A 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.Optional
FTX1A segment providing textual information related to the message type, namely: message type name, Introduction, Scope, Functional definition, Principles, References and Terms and definitions.Optional
DTM1This segment is used to indicate the release date of a message, as indicated on the cover page of the boilerplate.Mandatory
SG41SG4Mandatory
SGU2A segment specifying the usage of a segment in a message type structure.Mandatory
ATT2A 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.Optional
FTX2A segment providing textual information about segment usage. This information comprises part of the 'Data segment clarification' section.Optional
SG52SG5Optional
GRU3A segment specifying the usage of a segment group in a message type structure.Mandatory
ATT3A 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.Optional
FTX3A segment providing the textual information about segment group usage. This information comprises part of the 'Data Segment Clarification' section.Optional
SG61SG6Optional
FNT2A 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.Mandatory
REL2A segment to provide the type of dependency relationship, where one exists.Optional
GIR2A segment to provide the position number(s) for segments and/or segment groups to which a dependency note or other note applies.Optional
ATT2A segment to provide the change indicators at the note level.Optional
FTX2A segment to provide a free text description of the dependency note or other note.Optional
SG70SG7Optional
SEG1A segment identifying a segment type and specifying its class and maintenance operation.Mandatory
ATT1A 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.Optional
FTX1A segment specifying the name and functional definition of a segment type.Optional
ELU1A segment specifying the contents of data elements in a segment type.Optional
SG81SG8Optional
FNT2A 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.Mandatory
REL2A segment to provide the type of dependency relationship, where one exists.Optional
GIR2A segment to provide the position number(s) for a data element to which a dependency note or other note applies.Optional
ATT2A segment to provide the change indicators at the note level.Optional
FTX2A segment to provide a free text description of the dependency note or other note.Optional
SG90SG9Optional
CMP1A segment identifying a composite data element and specifying its class and maintenance operation.Mandatory
ATT1A 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.Optional
FTX1A segment specifying the name and functional definition of a composite data element type.Optional
ELU1A segment specifying component data elements in a composite data element and its related information.Optional
SG101SG10Optional
FNT2A 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.Mandatory
REL2A segment to provide the type of dependency relationship, where one exists.Optional
GIR2A segment to provide the position number(s) for a data element to which a dependency note or other note applies.Optional
ATT2A segment to provide the change indicators at the note level.Optional
FTX2A segment to provide a free text description of the dependency note or other note.Optional
SG110SG11Optional
ELM1A segment identifying a simple data element and giving related information.Mandatory
ATT1A 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.Optional
FTX1A segment specifying the name and functional definition of a simple data element.Optional
SG120SG12Optional
CDS1A segment specifying a code set. In DIRDEF data element 9434 shall not be used.Mandatory
FTX1A segment providing textual information related to the code list.Optional
SG131SG13Optional
CDV2A segment specifying a code value.Mandatory
ATT2A 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.Optional
FTX2A segment specifying the name and functional definition of a code value.Optional
UNT0A 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.Mandatory