<% Response.CharSet="utf-8" %> UN/EDIFACT D97A Message RDRMES - Raw data reporting message Return to Stylus Studio EDIFACT D97A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Raw data reporting message

Version:D
Release:97A
Contr. Agency:UN
Revision:1
Date:96-12-13
SOURCE:Joint Rapporteurs Message Design Group JM8

CONTENTS
Raw data reporting message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Data segment clarification
    2. Data segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, 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

0. INTRODUCTION

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.


1. SCOPE


1.1. Functional Definition

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.


1.2. Field of Application

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.


1.3. Principles

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:


2. REFERENCES

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Data Segment Clarification

This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.

0010 UNH, Message header

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 element0065RDRMES
0052D
005497A
0051UN

0020 BGM, Beginning of message

A segment specifying the functional use (e.g. sub-set) of the Raw data reporting message and identifying the message.

0030 DTM, Date/time/period

A segment identifying dates, times, or periods which are relevant to the whole message.

0040 Segment Group 1: NAD-RFF-FTX-SG2

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.

0050 NAD, Name and address

A segment to identify the relevant parties.

0060 RFF, Reference

A segment to specify a reference that the respondent wishes to communicate to the collector.

0070 FTX, Free text

A segment to provide free form or coded text information.

0080 Segment Group 2: CTA-COM

A group of segments identifying a contact within the identified organization and communication number (e.g. telephone number, fax number).

0090 CTA, Contact information

A segment to identify a person or a department to whom communication should be directed.

0100 COM, Communication contact

A segment to identify a communication number of a department or a person to whom communication should be directed.

0110 Segment Group 3: IDE-SG4-SG6

A group of segments identifying a questionnaire, the responding organization, the questions in the questionnaire and the responses to the questions.

0120 IDE, Identity

A segment identifying a questionnaire.

0130 Segment Group 4: NAD-RFF-FTX-SG5

A group of segments identifying the responding organization to a questionnaire, the contact details, and administrative data relevant to the organization.

0140 NAD, Name and address

A segment identifying the responding organization.

0150 RFF, Reference

A segment to specify a reference that the responding organization wishes to communicate to the collector.

0160 FTX, Free text

A segment to provide free form or coded text information.

0170 Segment Group 5: CTA-COM

A group of segments identifying a contact within, or representing, the responding organization and communication number (e.g. telephone number, fax number).

0180 CTA, Contact information

A segment to identify a person or a department to whom communication should be directed.

0190 COM, Communication contact

A segment to identify a communication number of a department or a person to whom communication should be directed.

0200 Segment Group 6: SCD-ARR-RFF-DTM-FTX-SG7

A group of segments which specify a question in a questionnaire and the data given in response.

0210 SCD, Structure component definition

A segment to specify the identity of a question (e.g. in a questionnaire).

0220 ARR, Array information

A segment containing the data in response to a question.

0230 RFF, Reference

A segment to specify a reference relevant to the response.

0240 DTM, Date/time/period

A segment identifying dates, times, or periods relevant to the response.

0250 FTX, Free text

A segment to provide free form or coded text information relevant to the response.

0260 Segment Group 7: NAD-RFF-FTX-SG8

A group of segments that identify an organization, contact information and administrative information given in response to a question.

0270 NAD, Name and address

A segment specifying the identity of an organization which is given in response to a question.

0280 RFF, Reference

A segment to specify a reference relevant to the organization.

0290 FTX, Free text

A segment to provide free form or coded text information.

0300 Segment Group 8: CTA-COM

A group of segments identifying a contact within the identified organization and communication number (e.g. telephone number, fax number).

0310 CTA, Contact information

A segment to identify a person or a department to whom communication should be directed.

0320 COM, Communication contact

A segment to identify a communication number of a department or a person to whom communication should be directed.

0330 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.


4.2. Data segment index (Alphabetical sequence by tag)

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

4.3. Message structure


4.3.1. Segment table

├─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 ×1 (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)

Return to Stylus Studio EDIFACT D97A Messages page.