United Nations Directories
for Electronic Data Interchange for
Administration, Commerce and Transport



 UN/EDIFACT

Message Type : DMRDEF Version : D Release : 14A Contr. Agency: UN Revision : 2 Date : 2014-04-30 SOURCE: TBG16 Entry Point CONTENTS Data maintenance request definition message 0. INTRODUCTION 1. SCOPE 1.1 Functional definition 1.2 Field of application 1.3 Principles 2. REFERENCES 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions 4. MESSAGE DEFINITION 4.1 Segment clarification 4.2 Segment index (alphabetical sequence by tag) 4.3 Message structure 4.3.1 Segment table --------------------------------------------------------------------------- For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction --------------------------------------------------------------------------- 0. INTRODUCTION This specification provides the definition of the Data maintenance request definition message (DMRDEF) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE 1.1 Functional definition 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. 1.2 Field of application The Data maintenance request definition message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. 1.3 Principles The message permits the transmission of a Data Maintenance Request (DMR). The message may be exchanged at the regional or national level between the DMR submitter and the secretariat that acts as the entry point for DMR submissions to the submitter's technical assessment group. It may also be exchanged at an international level among the secretariats for the assessment function as well as those participating in the production of the directories. At the regional or national level the first DMRDEF sent for a given DMR will be from the submitter to the entry point secretariat utilizing the submitter's own reference number. On an international level the first DMRDEF sent for a given DMR will be from the entry point secretariat to the central secretariat utilizing the entry point secretariat's own unique reference (Log) number. All DMRDEF messages initiated after registration at the entry point secretariat will use the entry point secretariat Log numbers. All DMRDEF messages initiated after registration at the international level will use the central secretariat's Log number. The Data maintenance status report/query(DMSTAT) message will be used to notify all applicable parties of the latest log number assignments and other necessary status information. The DMRDEF message shall contain only a single Data maintenance request. For submissions of messages that allow the inclusion of substructure maintenance requirements in the same DMR, the segment identification segment group, the composite data element identification segment group, the simple data element segment group, and the code set identification segment group are to be used to provide the modified substructure relative to the message's boilerplate. A structure defined below the message level, as part of a Message submission, must include a change indicator in the associated attribute segment of the structure to indicate that the structure is being detailed as a proposed modification in association with the message. The reference segment shall identify all related parent and child DMRs one level above and one level below the current level. DMRs which change an existing entry must provide a complete replacement entry with the changed parts identified via the change indicators. All changes to message structure must also include all resultant changes to boilerplate text. Use of the default service characters is required and the Interchange header shall specify character set level C. Proper use of the DMRDEF message within supporting applications assumes the availability and use of the EDI standard in conjunction with originator data entry mechanisms in order to ensure the accurate association of data maintenance actions with the standard. 2. REFERENCES See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION 4.1 Segment clarification This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements. 00010 UNH, Message header 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 14A 0051 UN 00020 BGM, Beginning of message A segment to indicate the beginning of the message and to transmit function, type and number of the message. 00030 DII, Directory identification A segment specifying the identity of the reference directory set used in creating the DMR. 00040 DTM, Date/time/period 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. 00050 FTX, Free text 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. 00060 RFF, Reference 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. 00070 EFI, External file link identification A segment identifying associated documentation, including document reference and document type. 00080 Segment group 1: PNA-ADR-SG2 A group of segments identifying the party(ies) filing the Data maintenance request. In case of a jointly submitted DMR all parties shall be identified. 00090 PNA, Party identification 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. 00100 ADR, Address A segment identifying the DMR originator's address information. 00110 Segment group 2: CTA-COM A group of segments identifying the DMR originator's communication type(s) and number(s). 00120 CTA, Contact information A segment identifying a person or a department for the party specified in the leading PNA segment to whom the communication should be directed. 00130 COM, Communication contact A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment. 00140 Segment group 3: MSG-ATT-FTX-SG4-SG6 A group of segments providing a message type directory. 00150 MSG, Message type identification A segment identifying a message type to be specified. 00160 ATT, Attribute A segment used to specify if the message is for use with the batch or interactive message directori