Edm Ide Mscons

Siar Sarferaz Consulting Utilities

MSCONS vs. SAP-MSCONS

DL:

History:

VV2@SAP

Version Status Date

1.0 Draft

1.1 Draft


N:\SAPWorkDir\DataExchange\SAP_MSCONS_e.doc Seite 2

Table of Contents

1 General ............................................................................................................................3

2 MSCONS Segments........................................................................................................4

2.1 UNH – Message Header..............................................................................................................................4

2.2 BGM – Start of Message.............................................................................................................................5

2.3 DTM – Date/Time/Time Frame....................................................................................................................5

2.4 REF – Reference Specifications ................................................................................................................5

2.5 DTM – Date/Time/Time Frame....................................................................................................................5

2.6 NAD – Name and Address..........................................................................................................................6

2.7 UNS – Section Control................................................................................................................................6

2.8 NAD – Name and Address..........................................................................................................................6

2.9 LOC - Location ............................................................................................................................................7

2.10 DTM – Date/Time/Time Frame............................................................................................................8

2.11 REF - Reference Specifications .........................................................................................................8

2.12 CCI – Characteristic/Class Identification..........................................................................................8

2.13 MEA – Mass and Weighting ...............................................................................................................9

2.14 LIN – Item Number...............................................................................................................................9

2.15 PIA – Additional Product Identification.............................................................................................9

2.16 QTY – Quantity ..................................................................................................................................10

2.17 DTM – Date/Time/Time Frame..........................................................................................................10

2.18 CCI – Characteristic/Class Identification........................................................................................11

2.19 MEA – Mass and Weighting .............................................................................................................11

2.20 DTM – Date/Time/Time Frame..........................................................................................................11

2.21 UNT – End of Message Segment .....................................................................................................12

3 XML and MSCONS........................................................................................................12

4 MSCONS Example........................................................................................................12

Copyright..........................................................................................................................16



1 General

When processing business processes, it is usually necessary for information to be exchanged

between participating utility companies. The German Electricity Association (VDEW) have defined

a number of message categories in order to standardize information exchange. These include the

following message categories:

Message category

Used to transfer

MSCONS Measured values (consumption data)

UTILMD Master data

REMADV Payment advice notes

APERAK Application errors and confirmation notifications

CONTTRL Syntax and transfer control messages

REQDOC Document requests

INVOIC Billings for grid and energy services

This document describes the MSCONS message category and the corresponding SAP implementation. The MSCONS message category is used for communication between business partners within the energy industry. It contains details on energy supplied or energy consumed and, if necessary, relevant technical information on products, services, and location, such as the place of energy transfer, details on reading or measurement values, if supply is based on a load profile, for example. Version 1.6a of MSCONS was released on 20.03.2002. This section describes the individual segments of MSCONS and the corresponding SAP structures: A MSCONS message consists of the following segments:

• Start of message (UNH, BGM)

• Message date (DTM)

• Reference with date (REF, DAT)

• Sender and recipient ID (NAD)

• Separation segment (UNS)

• Supply or reference location (NAD)

• Location of meter (LOC)

• Date of entry of measurement period length (DTM)

• Reference details for meter (REF)

• Characteristics of meter/measurement (CCI)

• Current item (LIN)

• EDIS code (PIA)

• Quantity specifications (QTY)

• Time specifications (DTM)

• Characteristics of measurement value, such as conversion factor (CCI)

• Value for characteristic (MEA)

• Time specifications (DTM)

• Message end (UNT)



2 MSCONS Segments This section describes the individual MSCONS segments and the corresponding SAP data structures.

2.1 UNH – Message Header

Segment UNH is implemented as segment E1VDEWUNH and is used to open, identify, and specify messages.

UNH E1VDEWUNH

0062 Message reference number REFERENCENUMBER

0065 Message category ID IDENTIFIER

0052 Version number of message category VERSIONNUMBER

0054 Release number of message category RELEASENUMBER

0051 Administrative organization, coded CONTROLAGENCY

0057 Application code of appropriate organization ASSOCCODE

0068 General allocation reference ACCESSREF

0070 Transfer sequence number TRANSFERNUMBER

0073 Indicator for first/last message INDICATOR



2.2 BGM – Start of Message

Segment BGM is implemented as segment E1VDEWBGM and is used to display the category and function of a message as well as to transfer the ID number.

BGM E1VDEWBGM

1001 Document/message name, coded NAME

1131 Code list, qualifier CODELIST

3055 Place responsible for code maintenance, coded

CODELISTAGENCY

1000 Document/message name FULLNAME

1004 Document/message number DOCUMENTNUMBER

1056 Version VERSION

1060 Revision number REVISION

1225 Message function, coded DOCUMENTFUNC

4343 Response type, coded RESPONSETYPE

2.3 DTM – Date/Time/Time Frame

Segment DTM is implemented as segment E1VDEWDTM and is used to specify the document date.

DTM E1VDEWDTM

2005 Date/time/time frame, qualifier DATUMQUALIFIER

2380 Date/time/time frame DATUM

2379 Date/time/time frame, format qualifier FORMAT

2.4 REF – Reference Specifications

Segment REF is implemented as segment E1VDEWRFF_1 and is used to specify references that refer to the entire message. For example, the number of a REQDOC request.

REF E1VDEWREF_1

1153 Reference, qualifier REFERENCEQUALIFIER

1154 Reference number REFERENCENUMBER

1156 Line number LINENUMBER

4000 Reference number VERSIONNUMBER



Segment DTM is implemented as segment E1VDEWDTM_2 and is used to specify dates of previous RFF segments. For example, the request date.

DTM E1VDEWDTM_2






2.6 NAD – Name and Address

Segment NAD is implemented as segment E1VDEWNAD and is used to identify the business partners involved in the process. The sender (usually responsible for the data) and the recipient must be specified.

NAD E1VDEWNAD

3035 Participant, qualifier ACTION

3039 Identification of participant PARTNER



CODELISTAGENCY

3124 Line for name and address NAMEADDRESS1





3036 Name of participant PARTNERNAME1





3045 Name of participant, format, coded PARTNERFORMAT

3042 Street and house number or PO box STREET1




3164 City CITY

3229 Region, identification REGION

3251 Postal code ZIPCODE

3207 Country, coded COUNTRY

2.7 UNS – Section Control

Section UNS is implemented as segment E1VDEWUNS and is used to separate the header section of a message from the item section.

UNS E1VDEWUNS

0081 Section ID, coded SECTION_ID

2.8 NAD – Name and Address

Segment NAD is implemented as segment E1VDEWNAD_2 and is either used to identify the supply location or to identify another service provider that differs from the one defined as the message sender in segment group 2. The supply location is the payer’s address at the point where the product/service is received.



NAD E1VDEWNAD_2

3035 Participant, qualifier ACTION

3039 Identification of participant PARTNER



CODELISTAGENCY











3045 Name of participant, format, coded PARTNERFORMAT





3164 City CITY

3229 Region, identification REGION

3251 Postal code ZIPCODE

3207 Country, coded COUNTRY

2.9 LOC - Location

Segment LOC is implemented as segment E1VDEWLOC and is used to specify the location to which the data applies.

LOC E1VDEWLOC

3227 Location, qualifier PLACE_QUALIFIER

3225 Location, identification PLACE_ID

1131 Code list, qualifier CODE_LIST_QUALIFIER_1


CODE_LIST_RESPONSIBLE_AGENCY_1

3224 Location PLACE

3223 Related place/location 1, identification RELATED_PLACE_COMPANY_1




3222 Related place/location 1 RELATED_PLACE_AREA_1



3233 Related place/location 2, identification RELATED_PLACE_COMPANY_2




3232 Related place/location 2 RELATED_PLACE_AREA_2

5479 Allocation, coded RELATION_CODE


Segment DTM is implemented as segment E1VDEWDTM_3 and is used to determine meter reading dates, entry dates and the entry period, and to specify the measurement periods for values entered periodically.

DTM E1VDEWDTM_3




2.11 REF - Reference Specifications

Segment REF is implemented as segment E1VDEWRFF_2 and is used to specify references that refer to the meter.

REF E1VDEWDTM_2

1153 Reference, qualifier REFERENCEQUALIFIER

1154 Reference number REFERENCENUMBER

1156 Line number LINENUMBER

4000 Reference version number VERSIONNUMBER


2.12 CCI – Characteristic/Class Identification

Segment CCI is implemented as segment E1VDEWCCI and is used to identify and describe specific characteristics. These specifications refer to the previous LOC segment.l

CCI E1VDEWCCI

7059 Characteristic class, coded PROPERTY_CLASS

6313 Measurement specification, dimension, coded

PROPERTY_MEASURE

6321 Significance of measurement specification, coded

MEASUREMENT_SIGNIFICANCE

6155 Measurement attribute, coded MEASUREMENT_ATTRIBUTE_ID

6154 Measurement attribute MEASUREMENT_ATTRIBUTE

7037 Characteristic, ID CHARACTERISTIC_ID

1131 Code list, qualifier CODE_LIST_QUALIFIER


CODE_LIST_RESPONSIBLE_AGENCY

7036 Characteristic CHARACTERISTIC_1




2.13 MEA – Mass and Weighting

Segment E1VDEWMEA is part of SAP-MSCONS as older versions of VDEW-MSCONS have a segment such as this.

MEA E1VDEWMEA

MEASURMENT_APPLICATION

MAESUREMENT_DIMENSION


MEASUREMENT_ATTRIBUTE_CODE

MEASUREMENT_ATTRIBUTE

MEASURE_UNIT_QUALIFIER

MEASUREMENT_VALUE

RANGE_MIN

RANGE_MAX

SIGNIFICANT_DIGITS

SURFACE_INDICATOR

2.14 LIN – Item Number

Segment LIN is implemented as segment E1VDEWLIN and is used to display the start of the item portion within a location. The item portion is created from repetition of segment groups, which always begin with a LIN segment. The item number is increased in order to create different measurement values (multiple registers) or measurement value sequences (active and inactive energy) for a point of delivery.

LIN E1VDEWLIN

1082 Item number LINE_ITEM_NUMBER

1229 Action request/notification, coded ACTION_REQUEST_NOT_CODE

7140 Product/service number ITEM_NUMBER

7143 Product/service number, type, coded ITEM_NUMBER_TYPE




5495 Display for subitem, coded SUBLINE_INDICATOR

1082 Item number SUBLINE_ITEM_NUMBER

1222 Configuration number CONFIGURATION_LEVEL

7083 Subitem allocation, coded CONFIGURATION

2.15 PIA – Additional Product Identification

Segment PIA is implemented as segment E1VDEWPIA and is used to identify the product for the relevant item by means of the EDIS code. This identification process is used during the exchange of energy data in the German energy industry. SAP-MSCONS defines additional fields for this segment.



PIA E1VDEWPIA

4347 Product identification function, qualifier PRODUCT_ID

7140 Product/service number ITEM_NUMBER_1

7143 Product/service number, type, coded ITEM_NUMBER_TYPE_1




ITEM_NUMBER_2

ITEM_NUMBER_TYPE_2

CODE_LIST_QUALIFIER_2


ITEM_NUMBER_3

ITEM_NUMBER_TYPE_3



ITEM_NUMBER_4

ITEM_NUMBER_TYPE_4



ITEM_NUMBER_5

ITEM_NUMBER_TYPE_5



2.16 QTY – Quantity

Segment QTY is implemented as segment E1VDEWQTY and is used to specify quantities for items.

QTY E1VDEWQTY

6063 Quantity, qualifier QUANTITY_QUALIFIER

6060 Quantity QUANTITY

6411 Measurement unit, qualifier MEASURE_UNIT_QUALIFIER


Segment DTM is implemented as segment E1VDEWDTM_4 and contains date and time specifications for the meter data in the previous QTY segment. This refers to the measurement period or run period (for a profile), or the time (for a meter reading) of a value. An entry time is only specified at this point if it is for an individual value that differs from the time given in SG6.

DTM E1VDEWDTM_4



2379 Date/time/time frame FORMAT



2.18 CCI – Characteristic/Class Identification

Segment CCI is implemented as segment E1VDEWCCI_2 and is used to identify and describe specific characteristics. This information refers to the previous LIN segment and is specified in the following MEA segment.

CCI E1VDEWCCI_2

7059 Characteristic class, coded PROPERTY_CLASS


PROPERTY_MEASURE



6155 Measurement attribute, coded MEASUREMENT_ATTRIBUTE_ID


7037 Characteristic, ID CHARACTERISTIC_ID






2.19 MEA – Mass and Weighting

Segment MEA is implemented as segment E1VDEWMEA_2 and is used to specify the characteristic values in the previous CCI segment in more detail.

MEA E1VDEWMEA_2

6311 Measurement specifications, application qualifier

MEASURMENT_APPLICATION


MAESUREMENT_DIMENSION



6155 Measurement attribute, coded MEASUREMENT_ATTRIBUTE_CODE


6411 Measurement unit, qualifier MEASURE_UNIT_QUALIFIER

6314 Measurement value MEASUREMENT_VALUE

6162 Minimum limit RANGE_MIN

6152 Maximum limit RANGE_MAX

6432 Significant digits SIGNIFICANT_DIGITS

7383 Interface/level, coded SURFACE_INDICATOR


Segment DTM is implemented as segment E1VDEWDTM_5 and contains date and time specifications for the product characteristics in the previous MEA segment. The validity periods of a conversion factor can be specified here.



DTM E1VDEWDTM_5



2379 Date/time/time frame FORMAT

2.21 UNT – End of Message Segment

Segment UNT is implemented as segment E1VDEWUNT. This segment is mandatory in UN/EDIFACT. It must always be the last segment in a message.

UNT E1VDEWUNT

0074 Number of segments in the message NUMSEG

0062 Message reference number REFNUM

3 XML and MSCONS XML (Hypertext Markup Language) is increasingly becoming the standard format for exchanging electronic data. We can assume that in the future data exchange will occur exclusively by means of XML. In March 2002, the German electricity association (VDEW) released an XML schema for message category MSCONS. This XML schema for MSCONS was fully implemented in the VV2 project. XML data can be exported and imported using the Business Connector. See the Business Connector documentation for the technical details.

4 MSCONS Example The SAP-MSCONS format is illustrated in this section using an example. The data in the example was generated from IS-U and formatted systematically. The fields in italics have corresponding MSCONS structures. However, they do not contain any data.

ISU_VDEW_MSCONS

E1VDEWUNH SEGMENT

REFERENCENUMBER: 000000000607

IDENTIFIER: MSCONS

VERSIONNUMBER: D

RELEASENUMBER: 99A

CONTROLAGENCY: UN

ASSOCCODE:

ACCESSREF:

TRANSFERNUMBER:

INDICATOR:

E1VDEWBGM SEGMENT

NAME: 7

CODELIST:

CODELISTAGENCY: 5

FULLNAME:

DOCUMENTNUMBER: 000000000607

VERSION:

REVISION:

DOCUMENTFUNC: 9



RESPONSETYPE:

E1VDEWREF SEGMENT

E1VDEWDTM SEGMENT

DATUMQUALIFIER: 137

DATUM: 200208161202

FORMAT: 203

E1VDEWNAD SEGMENT

ACTION: MS

PARTNER: SWBIELEFELD_N

CODELIST:

CODELISTAGENCY: 60

NAMEADDRESS1: EDM: SW BIELEFELD (VNB)

PARTNERNAME1: GP_SP_SVB_VNB

PARTNERFORMAT:

STREET1: Musterstrasse 63

CITY: Ulm

REGION:

ZIPCODE:

COUNTRY: DE

E1VDEWNAD SEGMENT

ACTION: MR

PARTNER: SWBIELEFELD_L

CODELIST:

CODELISTAGENCY: 60

NAMEADDRESS1: EDM: SW BIELEFELD (LIEFERANT)

PARTNERNAME1: GP_SP_SWB

PARTNERFORMAT:

STREET1: Badenwerkstraße 61

CITY: Karlsruhe

REGION:

ZIPCODE: 76228

COUNTRY: DE

E1VDEWUNS SEGMENT

SECTION_ID: D

E1VDEWNAD_2 SEGMENT

ACTION: DP

PARTNER:

CODELIST:

CODELISTAGENCY: 9

NAMEADDRESS1:

PARTNERNAME1:

PARTNERFORMAT:

STREET1:

CITY:

REGION:

ZIPCODE:



COUNTRY: DE

E1VDEWLOC SEGMENT

PLACE_QUALIFIER: 172

PLACE_ID:

CODE_LIST_QUALIFIER_1:

CODE_LIST_RESPONSIBLE_AGENCY_1: 87

PLACE: DE12345612345 MN_RTP2

RELATED_PLACE_COMPANY_1:

RELEATED_PLACE_AREA_1:

RELATION_CODE:

E1VDEWDTM_3 SEGMENT

DATUMQUALIFIER: 163

DATUM: 200101010000

FORMAT: 203

E1VDEWDTM_3 SEGMENT

DATUMQUALIFIER: 164

DATUM: 200101010000

FORMAT: 203

E1VDEWRFF_2 SEGMENT

REFERENCEQUALIFIER: MG

REFERENCENUMBER:

LINENUMBER:

VERSIONNUMBER:

REVISION:

E1VDEWCCI SEGMENT

PROPERTY_CLASS: MCH

PROPERTY_MEASURE:

MEASUREMENT_SIGNFICANCE:

MEASUREMENT_ATTRIBUTE_ID:

MEASUREMENT_ATTRIBUTE:

CHARACTERISTIC_ID:

CODE_LIST_QUALIFIER:

CODE_LIST_RESPONSIBLE_AGENCY: 60

CHARACTERISTIC_1:

CHARACTERISTIC_2:

E1VDEWLIN SEGMENT

LINE_ITEM_NUMBER:

ACTION_REQUEST_NOT_CODE:

ITEM_NUMBER: 1

ITEM_NUMBER_TYPE: EN

CODE_LIST_QUALIFIER:

CODE_LIST_RESPONSIBLE_AGENCY: 9

SUBLINE_INDICATOR:

SUBLINE_ITEM_NUMBER:

CONFIGURATION_LEVEL:

CONFIGURATION:



E1VDEWPIA SEGMENT

PRODUCT_ID: 5

ITEM_NUMBER_1: 5459

ITEM_NUMBER_TYPE_1: MP

CODE_LIST_QUALIFIER_1:

CODE_LIST_RESPONSIBLE_AGENCY_1: 174

E1VDEWQTY SEGMENT

QUANTITY_QUALIFIER: 46

QUANTITY: 7.0000000000000

MEASURE_UNIT_QUALIFIER: KWH

E1VDEWDTM_4 SEGMENT

DATUMQUALIFIER: 163

DATUM: 200101010000+01

FORMAT: 303

E1VDEWDTM_4 SEGMENT

DATUMQUALIFIER: 164

DATUM: 200101010015+01

FORMAT: 303

E1VDEWCCI SEGMENT

E1VDEWUNT SEGMENT

NUMSEG: 18

REFNUM: 000000000607

Copyright

© Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint

are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Edm Ide Mscons

Documents

Transcript of Edm Ide Mscons