Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D99A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Metered services consumption report message

Version:D
Release:99A
Contr. Agency:UN
Revision:1
Date:99-01-14
SOURCE:Western European EDIFACT Board - MD1

CONTENTS
Metered services consumption report 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
      1. Header section
      2. Detail section
      3. Summary section
    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:
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 Metered services consumption report message (MSCONS) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

A metered services consumption report is a communication between trading parties, or their agents, providing consumption and where associated technical, information at a location(s) for a product(s) or service(s) where the supply is recorded using a meter(s).


1.2. Field of Application

The Metered services consumption report 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

  • At least one delivery party (premise) shall be identified per message.
  • Each metered services consumption report will define the period of time for which the details contained are valid.
  • A metered services consumption report may be used to provide consumption information which may directly relate to other business functions, e.g. invoicing or process control.
  • A metered services consumption report may be sent by the buyer or the seller to the other party.
  • Metered services consumption report will be provided for premises as defined by trading partners.
  • Locations, products and, or services, and meters shall be identified where ever possible within the report using codes to facilitate automatic processing.
  • The metered services consumption report may be transmitted at any time and may be related directly to either a delivery(ies) and, or an invoice(s).
  • A metered services consumption report when used to support the financial information contained in an invoice may only relate to one invoice.
  • A metered services consumption report when used to indicate consumption or qualitative information may relate to one or many delivery parties (premises).

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 indicates mandatory, conditional and repeating requirements.

The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message:

  • Where a choice of code or text is given only the code element should be used wherever possible.
  • Conditional data that is not required in the message should not be included.
  • Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of a group.
  • Free text information within the message should be avoided as this inhibits automatic processing. It is only used when additional information that cannot be accommodated within the other segments is required.

4.1.1. Header section

Information to be provided in the Header section:

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Metered services consumption report message is MSCONS.

Note: Metered services consumption report messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065MSCONS
0052D
005499A
0051UN

0020 BGM, Beginning of message

A segment by which the sender must uniquely identify the metered services consumption report.

0030 DTM, Date/time/period

A segment specifying the dates, and when relevant, the times related to the whole message. The segment must be specified at least once to specify the message date as allocated by the sender.

0040 Segment Group 1: RFF-DTM

A group of segments for specifying any references and their dates valid for the whole report.

0050 RFF, Reference

A segment for the inclusion of any references related to the complete report, e.g. invoice number, contract number.

0060 DTM, Date/time/period

A segment specifying the date and where necessary the time of the reference detailed in the preceding RFF segment.

0070 Segment Group 2: NAD-SG3-SG4

A group of segments identifying the parties involved in the transaction, reference numbers associated with the parties, and any contact points and numbers.

0080 NAD, Name and address

A segment to identify the party name and address, either by coded identification or in clear form. It is recommended that were possible only the coded form of the party identification should be specified, e.g. the buyer and seller are known to each other, thus only the coded identification is required.

0090 Segment Group 3: RFF-DTM

A group of segments for specifying any references relating to the party identified in the NAD segment.

0100 RFF, Reference

A segment for inclusion of any references related to the current party, e.g. fiscal number, government reference number, etc.

0110 DTM, Date/time/period

A segment specifying the date and where necessary the time of the reference detailed in the preceding RFF segment.

0120 Segment Group 4: CTA-COM

A group of segments identifying the contact person or department for trading party and specifying the communication channel and number.

0130 CTA, Contact information

A segment to identify a person or department and their function, to whom communication should be directed.

0140 COM, Communication contact

A segment specifying the communication channel and number for the specified contact.


4.1.2. Detail section

Information to be provided in the Detail section:

0150 UNS, Section control

A segment placed at the start of the detail section to avoid segment collision.

0160 Segment Group 5: NAD-SG6

A group of segments identifying the delivery party (premise) and the meter for which consumption is being reported.

0170 NAD, Name and address

A segment to identify the delivery party (premise) for which the following consumption information is being provided. It is recommended that where possible codes be used to identify the delivery party to facilitate the automatic processing.

0180 Segment Group 6: LOC-DTM-SG7-SG8-SG9

A group of segments identifying the meter being reported, the date of the meter read, associated references, the physical characteristics of the meter, and the product or service for which consumption information is reported.

0190 LOC, Place/location identification

A segment to allow the identification of the meter to which the consumption information relates. It is recommended that where possible codes be used to identify the delivery party to facilitate automatic processing.

0200 DTM, Date/time/period

A segment to specify dates associated with the reading of the meter.

0210 Segment Group 7: RFF-DTM

A group of segments for specifying any references and associated dates valid for the meter identified in the LOC segment.

0220 RFF, Reference

A segment identifying any references related to the meter identified in the LOC segment (e.g. serial number).

0230 DTM, Date/time/period

A segment to specify any dates associated with the currently referenced document.

0240 Segment Group 8: CCI-DTM

A group of segments used to provide characteristic information and associated dates for the current meter.

0250 CCI, Characteristic/class id

A segment to describe the characteristics of the currently identified meter (e.g. sealed meter, banded meter).

0260 DTM, Date/time/period

A segment specifying the date and where necessary the time related to the previously identified meter characteristics (e.g. installation date, connection date, meter banding date).

0270 Segment Group 9: LIN-PIA-IMD-PRI-NAD-MOA-SG10-SG11

A group of segments providing details of the metered products or services, quantities, characteristics, and any associated dates.

0280 LIN, Line item

A segment identifying the metered product or service for which consumption information is being provided.

0290 PIA, Additional product id

A segment providing additional identification to the product or service specified in the LIN segment (e.g. buyer's or supplier's product codes).

0300 IMD, Item description

A segment for describing the metered product or service being reported. This segment should only be used for metered products or services that cannot be fully identified by an article number.

0310 PRI, Price details

A segment providing the unit price of the currently identified product or service.

0320 NAD, Name and address

A segment to identify parties related to the supply of the service (e.g. party telephoned) or related to the party who supplied the service (e.g. a petrol filling station).

0330 MOA, Monetary amount

A segment to specify the total cost of the product or service currently being reported upon, e.g. the total cost of local telephone calls.

0340 Segment Group 10: QTY-DTM

A group of segments providing details of the meter read, consumption, correction quantities, and associated dates.

0350 QTY, Quantity

A segment identifying the consumption details, e.g. opening meter read, consumption, adjustments (correction).

0360 DTM, Date/time/period

A segment to specify dates related to the previously specified consumption information.

0370 Segment Group 11: CCI-MEA-DTM

A group of segments providing characteristic details, measurements, and dates related to the details for the currently identified line item.

0380 CCI, Characteristic/class id

A segment used to describe the characteristics of the currently identified product or service (e.g. calorific values, chlorine content).

0390 MEA, Measurements

A segment enabling the indication of measurements related to the characteristics identified in the preceding CCI segment.

0400 DTM, Date/time/period

A segment to specify dates related to the previously specified characteristic information.


4.1.3. Summary section

Information to be provided in the Summary section:

0410 CNT, Control total

A segment by which control totals may be sent by the sender for checking by the receiver.

0420 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)

BGM Beginning of message
CCI Characteristic/class id
CNT Control total
COM Communication contact
CTA Contact information
DTM Date/time/period
IMD Item description
LIN Line item
LOC Place/location identification
MEA Measurements
MOA Monetary amount
NAD Name and address
PIA Additional product id
PRI Price details
QTY Quantity
RFF Reference
UNH Message header
UNS Section control
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 ×9 (M)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×99 (C)
├─NAD Name and address ×1 (M)
├─Segment Group 3 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
└─Segment Group 4 ×9 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×9 (C)
├─UNS Section control ×1 (M)
├─Segment Group 5 ×99999 (M)
├─NAD Name and address ×1 (M)
└─Segment Group 6 ×99999 (M)
──├─LOC Place/location identification ×1 (M)
──├─DTM Date/time/period ×9 (C)
──├─Segment Group 7 ×99 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×9 (C)
──├─Segment Group 8 ×99 (C)
──├─CCI Characteristic/class id ×1 (M)
──└─DTM Date/time/period ×99 (C)
──└─Segment Group 9 ×99999 (C)
────├─LIN Line item ×1 (M)
────├─PIA Additional product id ×9 (C)
────├─IMD Item description ×9 (C)
────├─PRI Price details ×9 (C)
────├─NAD Name and address ×9 (C)
────├─MOA Monetary amount ×9 (C)
────├─Segment Group 10 ×9999 (M)
────├─QTY Quantity ×1 (M)
────└─DTM Date/time/period ×9 (C)
────└─Segment Group 11 ×99 (C)
──────├─CCI Characteristic/class id ×1 (M)
──────├─MEA Measurements ×99 (C)
──────└─DTM Date/time/period ×9 (C)
├─CNT Control total ×99 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D99A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.