DMRDEF Data maintenance request definition

TBG16 Entry Point

This Data maintenance request definition message (DMRDEF) permits the transfer of a data maintenance request action among parties involved in the preparation, processing, assessment, resolution and directory production processes.

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 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 0052 D 0054 15A 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.

  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 reference directory set used in creating the DMR.

  4. A 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.

  5. A 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.

  6. A 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.

  7. A segment identifying associated documentation, including document reference and document type.

  8. Segment group 1
    Repeat 99

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

    2. A segment identifying the DMR originator's address information.

    3. Segment group 2
      Repeat 9

      1. A segment identifying a person or a department for the party specified in the leading PNA 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.

  9. Segment group 3
    Repeat 1

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

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

    3. A 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.

    4. Segment group 4
      Repeat 999

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

      2. A segment to indicate what modifications the DMR will make to the clarification text for the segment.

      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 to indicate what modifications the DMR will make to the segment group's clarification text.

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

    5. Segment group 6
      Repeat 99

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

      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 note applies.

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

      5. A segment to provide free text for a position relative note.

  10. Segment group 7
    Repeat 9999

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

    2. A segment used to indicate what modifications the DMR will make to the segment.

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

    4. A 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.

    5. Segment group 8
      Repeat 99

      1. A segment to provide the footnote identification for a dependency note or other note to be applied against one or more elements of a segment.

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

      3. A segment to provide the position number(s) for composites and/or simple data elements to which a note applies.

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

      5. A segment to provide free text for a position relative note.

  11. 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 indicate what modifications the DMR will make to the composite.

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

    5. Segment group 10
      Repeat 99

      1. A segment to provide the footnote identification for a dependency note or other note to be applied against one or more elements of a composite.

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

      3. A segment to provide the position number(s) for simple data elements to which a note applies.

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

      5. A segment to provide free text for a position relative note.

  12. Segment group 11
    Repeat 9999

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

    2. A segment used to indicate what modifications the DMR will make to the simple data element.

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

  13. Segment group 12
    Repeat 9999

    1. A segment specifying a code set.

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

    3. Segment group 13
      Repeat 9999

      1. A segment specifying a code value. In DMRDEF use the associated free text segment to provide the code value's name.

      2. A segment used to indicate what modifications the DMR will make to the code.

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

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