| Version: | D |
|---|---|
| Release: | 99B |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 1999-09-11 |
| SOURCE: | Joint Rapporteurs Message Design Group JM8 |
|
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 |
|
This message also occurs in the following versions of this standard: D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Raw data reporting message (RDRMES) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A Raw data reporting message (RDRMES) is sent in response to predefined and identified questions. Raw data are collected by numerous offices in the public and private sectors. Much of the data is predefined and repetitious. The data are often codified such that their description has been pre-set and meets the criteria of the collector.
The Raw data reporting 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.
The Raw data reporting message supports the transmission of multiple responses to one or more questionnaires, each uniquely identified.
Concepts-definitions:
Raw data: The respondent's answers to the collector's questionnaire.
Respondent: The organization for which raw data are provided. Raw data may be sent by the responding organization or an agent acting on behalf of the responding organization.
Collector: The organization to which raw data are provided. Raw data may be received by the collecting organization or an agent acting on behalf of the collecting agency.
Questionnaire: A set of questions, with collector-assigned identifiers, addressed to a respondent.
RESPONDENT +-------------------------------------------------------------+ | +----------------------+ +-------------------------+ | | + Responding Agent + << -- + Responding Organization + | | +----------------------+ +-------------------------+ | +-------------------------------------------------------------+
\|/ \|/
COLLECTOR
+-------------------------------------------------------------+ | +---------------------+ +-------------------------+ | | + Collecting Agent + -- >> + Collecting Organization + | | +---------------------+ +-------------------------+ | +-------------------------------------------------------------+
Message Composition-
the message is comprised of two parts:
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Raw data reporting message is RDRMES.
Note: Raw data reporting messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | RDRMES |
| 0052 | D | |
| 0054 | 99B | |
| 0051 | UN |
A segment specifying the functional use (e.g. sub-set) of the Raw data reporting message and identifying the message.
A segment identifying dates, times, or periods which are relevant to the whole message.
A group of segments identifying the name and address of the relevant parties, along with additional information related to the interchanging partners, such as references, contacts and communication numbers.
A segment to identify the relevant parties.
A segment to specify a reference that the respondent wishes to communicate to the collector.
A segment to provide free form or coded text information.
A group of segments identifying a contact within the identified organization and communication number (e.g. telephone number, fax number).
A segment to identify a person or a department to whom communication should be directed.
A segment to identify a communication number of a department or a person to whom communication should be directed.
A group of segments identifying a questionnaire, the responding organization, the questions in the questionnaire and the responses to the questions.
A segment identifying a questionnaire.
A group of segments identifying the responding organization to a questionnaire, the contact details, and administrative data relevant to the organization.
A segment identifying the responding organization.
A segment to specify a reference that the responding organization wishes to communicate to the collector.
A segment to provide free form or coded text information.
A group of segments identifying a contact within, or representing, the responding organization and communication number (e.g. telephone number, fax number).
A segment to identify a person or a department to whom communication should be directed.
A segment to identify a communication number of a department or a person to whom communication should be directed.
A group of segments which specify a question in a questionnaire and the data given in response.
A segment to specify the identity of a question (e.g. in a questionnaire).
A segment containing the data in response to a question.
A segment to specify a reference relevant to the response.
A segment identifying dates, times, or periods relevant to the response.
A segment to provide free form or coded text information relevant to the response.
A group of segments that identify an organization, contact information and administrative information given in response to a question.
A segment specifying the identity of an organization which is given in response to a question.
A segment to specify a reference relevant to the organization.
A segment to provide free form or coded text information.
A group of segments identifying a contact within the identified organization and communication number (e.g. telephone number, fax number).
A segment to identify a person or a department to whom communication should be directed.
A segment to identify a communication number of a department or a person to whom communication should be directed.
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.
| ARR | Array information | |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| FTX | Free text | |
| IDE | Identity | |
| NAD | Name and address | |
| RFF | Reference | |
| SCD | Structure component definition | |
| UNH | Message header | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×5 | (C) |
| ├─Segment Group 1 | ×9 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─RFF Reference | ×9 | (C) |
| │─├─FTX Free text | ×9 | (C) |
| │─└─Segment Group 2 | ×9 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×9 | (C) |
| ├─Segment Group 3 | ×9999 | (M) |
| │─├─IDE Identity | ×1 | (M) |
| │─├─Segment Group 4 | ×1 | (C) |
| │─│─├─NAD Name and address | ×1 | (M) |
| │─│─├─RFF Reference | ×9 | (C) |
| │─│─├─FTX Free text | ×9 | (C) |
| │─│─└─Segment Group 5 | ×9 | (C) |
| │─│───├─CTA Contact information | ×1 | (M) |
| │─│───└─COM Communication contact | ×9 | (C) |
| │─└─Segment Group 6 | ×99999 | (M) |
| │───├─SCD Structure component definition | ×1 | (M) |
| │───├─ARR Array information | ×99999 | (C) |
| │───├─RFF Reference | ×99 | (C) |
| │───├─DTM Date/time/period | ×9 | (C) |
| │───├─FTX Free text | ×99 | (C) |
| │───└─Segment Group 7 | ×99999 | (C) |
| │─────├─NAD Name and address | ×1 | (M) |
| │─────├─RFF Reference | ×9 | (C) |
| │─────├─FTX Free text | ×9 | (C) |
| │─────└─Segment Group 8 | ×9 | (C) |
| │───────├─CTA Contact information | ×1 | (M) |
| │───────└─COM Communication contact | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |