© 2018 ProgM

Nachricht DMRDEF: D

NameDMRDEF
VersionD
Release18A
BeschreibungData maintenance request definition message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A service segment starting and uniquely identifying a message. The message type code for the Data maintenance request definition message is DMRDEF. Note: Data maintenance request definition messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 DMRDEF 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 reference directory set used in creating the DMR.Mandatory
DTM0A segment specifying date information, e.g., the date the submitter forwarded the DMR, preparation date, technical assessment review date, final approval date, etc. Date information is to be provided in CCYYMMDD format.Mandatory
FTX0A segment specifying text information outlining the business requirement for this DMR. This segment may also be used by the originating technical assessment group to convey any explanations or comments which should accompany the DMR through the international assessment process. Other assessment groups will comment on a DMR via the DMSTAT message.Mandatory
RFF0A segment identifying the type of and reference log number of this request, as well as any related DMRs. In order to ensure proper identification of related DMRs, this segment shall identify, if existing, any parent and child DMRs one level above or below the current level. This segment shall not identify grand-parents and grand-children at any level. (Although a related DMR may have multiple parent DMRs and/or multiple child DMRs, the parent and child DMRs for these related DMRs will not be identified in the current DMR.) A related DMR(s) at the highest level, will have no parent DMR(s). A related DMR(s) at the lowest level will have no child DMR(s). The actual DMR reference log number type may be: Original submitter, Entry point assessment log number, Central secretariat log number, or International assessment log number. The related reference log number type may be: Original submitter, parent DMR Original submitter, child DMR Entry point assessment log number, parent DMR Entry point assessment log number, child DMR Central secretariat log number, parent DMR Central secretariat log number, child DMR International assessment log number, parent DMR International assessment log number, child DMR Also, the submitter must identify a message design group with which the DMR should be associated. This message design group will be consulted by technical assessment for functional evaluations.Optional
EFI0A segment identifying associated documentation, including document reference and document type.Optional
SG10SG1Optional
PNA1A segment identifying the originator of the Data maintenance request, e.g., the DMR submitter, Secretariat, etc. At least one occurrence is required to identify the submitter's organization name. When forwarding a DMR to the central secretariat the sender must identify which entry point is forwarding the DMR.Mandatory
ADR1A segment identifying the DMR originator's address information.Optional
SG21SG2Optional
CTA2A segment identifying a person or a department for the party specified in the leading PNA 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 if the message is for use with the batch or interactive message directories. It also may indicate what modifications the DMR will make to the message.Optional
FTX1A segment providing textual information related to the message type, namely: Message type name, Introduction, Scope, Functional definition, Field of application, Principles, References, Terms and definitions, Standard terms and definitions, and Message terms and conditions.Optional
SG41SG4Optional
SGU2A segment specifying the usage of a segment in a message type structure. The segment names for component segments are to be defined in the segment identification segment group. The segment names are provided once for each segment tag in the message and are the basis for all occurrences of the segment name in the message boilerplate.Mandatory
ATT2A segment to indicate what modifications the DMR will make to the clarification text for the segment.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 to indicate what modifications the DMR will make to the segment group's clarification text.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 to be applied against one or more segments and/or segment groups of a message.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 note applies.Optional
ATT2A segment to provide the change indicators at the note level.Optional
FTX2A segment to provide free text for a position relative note.Optional
SG70SG7Optional
SEG1A segment identifying a segment type and specifying its class and maintenance operation.Mandatory
ATT1A segment used to indicate what modifications the DMR will make to the segment.Optional
FTX1A segment specifying the name and functional definition of a segment type.Optional
ELU1A segment specifying the simple and/or component data elements in a segment type. The component element names are to be defined in either the composite data element identification segment group or the simple data element identification segment group, as appropriate for the component structure. The component element names are provided once for each component element tag in the segment and are the basis for all occurrences of the component element name in the segment structure.Optional
SG81SG8Optional
FNT2A segment to provide the footnote identification for a dependency note or other note to be applied against one or more elements of a segment.Mandatory
REL2A segment to provide the type of dependency relationship, where one exists.Optional
GIR2A segment to provide the position number(s) for composites and/or simple data elements to which a note applies.Optional
ATT2A segment to provide the change indicators at the note level.Optional
FTX2A segment to provide free text for a position relative note.Optional
SG90SG9Optional
CMP1A segment identifying a composite data element and specifying its class and maintenance operation.Mandatory
ATT1A segment used to indicate what modifications the DMR will make to the composite.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. The simple data element names are to be given in the simple data element identification segment group. The simple data element names are provided once for each simple data element tag in the composite and are the basis for all occurrences of the simple data element name in the composite structure.Optional
SG101SG10Optional
FNT2A segment to provide the footnote identification for a dependency note or other note to be applied against one or more elements of a composite.Mandatory
REL2A segment to provide the type of dependency relationship, where one exists.Optional
GIR2A segment to provide the position number(s) for simple data elements to which a note applies.Optional
ATT2A segment to provide the change indicators at the note level.Optional
FTX2A segment to provide free text for a position relative note.Optional
SG110SG11Optional
ELM1A segment identifying a simple data element and giving related information.Mandatory
ATT1A segment used to indicate what modifications the DMR will make to the simple data element.Optional
FTX1A segment specifying the name and functional definition of a simple data element.Optional
SG120SG12Optional
CDS1A segment specifying a code set.Mandatory
FTX1A segment providing textual information related to the code list.Optional
SG131SG13Optional
CDV2A segment specifying a code value. In DMRDEF use the associated free text segment to provide the code value's name.Mandatory
ATT2A segment used to indicate what modifications the DMR will make to the code.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