GF Machining Solutions - AgieCharmilles EDM - Wire EDM Gauging
Edm Ide Utilmd
-
Upload
gergo-paksy -
Category
Documents
-
view
63 -
download
5
description
Transcript of Edm Ide Utilmd
Release: VV2@SAP Author: Siar Sarferaz Consulting Utilities Peter Schulz Development Utilities
UTILMD vs. SAP-UTILMD
DL:
History:
VV2@SAP
Version Status Date
1.0 Draft
1.1 Draft
1.2
UTILMD vs. SAP-UTILMD
Page 2
Table of Contents
1 General ............................................................................................................................4
2 UTILMD Segments..........................................................................................................7
2.1 UNH – Message Header..............................................................................................................................7
2.2 BGM – Start of Message.............................................................................................................................7
2.3 DTM – Date/Time/Time Frame....................................................................................................................7
2.4 REF – Reference Specifications ................................................................................................................8
2.5 DTM – Date/Time/Time Frame....................................................................................................................8
2.6 NAD – Name and Address..........................................................................................................................8
2.7 FII – Credit Institute.....................................................................................................................................9
2.8 CTA – Contact Partner................................................................................................................................9
2.9 COM - Communication ...............................................................................................................................9
2.10 IDE - Identification.............................................................................................................................10
2.11 LOC - Location...................................................................................................................................10
2.12 DTM – Date/Time/Time Frame..........................................................................................................11
2.13 STS – Status ......................................................................................................................................11
2.14 TAX – Tolls, Taxes, and Fees...........................................................................................................12
2.15 FTX - Free Text ..................................................................................................................................12
2.16 AGR – Agreement Identification ......................................................................................................13
2.17 INP – Participant for Special Instruction ........................................................................................13
2.18 REF – Reference Specifications ......................................................................................................14
2.19 DTM – Date/Time/Time Frame..........................................................................................................14
2.20 CCI – Characteristic/Class Identification........................................................................................14
2.21 CAV – Characteristic Value ..............................................................................................................14
2.22 SEQ – Sequence Details...................................................................................................................15
2.23 PIA – Additional Product Identification...........................................................................................15
2.24 QTY – Quantity ..................................................................................................................................16
2.25 CCI – Characteristic/Class Identification........................................................................................16
2.26 CAV – Characteristic Value ..............................................................................................................16
UTILMD vs. SAP-UTILMD
Page 3
2.27 MOA – Monetary Amount .................................................................................................................17
2.28 REF - Reference Specifications.......................................................................................................17
2.29 DTM – Date/Time/Time Frame..........................................................................................................17
2.30 NAD – Name and Address................................................................................................................17
2.31 REF - Reference Specifications.......................................................................................................18
2.32 FII – Credit Institute...........................................................................................................................18
2.33 CTA – Contact Partner......................................................................................................................19
2.34 COM - Communication .....................................................................................................................19
2.35 UNT – End of Message Segment .....................................................................................................19
3 XML and UTILMD..........................................................................................................19
Copyright..........................................................................................................................20
UTILMD vs. SAP-UTILMD
Page 4
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
DELFOR Schedules
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 UTILMD message category and the corresponding SAP implementation. The functionality is mapped in basic IDoc type ISU_VDEW_UTILMD_V30 (UTILMD (VDEW 3.0A, D.02B). Message category UTILMD is used for communication between business partners within the energy industry. It contains details on master data for customers, contracts, and points of delivery. This message allows all relevant contract-related data in the deregulated energy industry to be exchanged. Version 3.0a of UTILMD was released on 11.06.2002. The figures below describes the individual segments of UTILMD and the corresponding SAP structures: A UTILMD message consists of the following segments:
• Nachrichtenanfang (UNH, BGM),
• Message date (DTM)
• Reference with date (REF, DAT)
• Sender and recipient ID (NAD, CTA, COM)
• Bank details (FII)
• Transaction ID (IDE)
• Reference point, point of delivery ID according to metering code (LOC)
• Start/end of supply, next periodic meter reading (DTM)
• Transaction reason, response status (STS)
• Franchise fee (TAX)
• Text additions (FTX)
• Specification for supply type, grid usage contract (AGR)
• Information on device replacement (INP)
• Reference specifications such as meter number (REF, DTM)
• Special characteristics (CCI, CAV)
• Sequence specifications (SEQ)
UTILMD vs. SAP-UTILMD
Page 5
• EDIS ID (PIA)
• Quantity specifications (QTY)
• Special characteristics (CCI, CAV)
• Specifications on budget billing amounts (MOA, REF, DTM)
• Additional business partner ID, for example bill recipient, end customer (NAD)
• Reference specifications, for example customer number at distributor (REF)
• Bank details (FII)
• Contact information (CTA, COM)
• End of message (UNT)
E1VDEWUNH
UNH
E1VDEWBGM_1
BGM
E1VDEWDTM
DTM
E1VDEWRFF_1
REF
E1VDEWUNT
UNT
E1VDEWNAD_1
NAD
E1VDEWDTM_2
DTM
E1VDEWCTA
CTA
SAP-UTILMD
VDEW-UTILMD
E1VDEWCOM
COM
E1VDEWFII_3
FII
IDE
UTILMD vs. SAP-UTILMD
Page 6
E1VDEWLOC_3
LOC
E1VDEWDTM_3
DTM
E1VDEWSTS_2
STS
E1VDEWTAX_3
TAX
E1VDEWFTX_2
FTX
E1VDEWAGR
AGR
E1VDEWINP
INP
E1VDEWREW_2
REF
E1VDEWCCI_3
CCI
E1VDEWSEQ_2
SEQ
E1VDEWMOA_6
MOA
E1VDEWNAD_4
NAD
E1VDEWDTM_4
DTM
E1VDEWCAV_3
CAV
E1VDEWPIA_2
PIA
SAP-UTILMD
VDEW-UTILMD
E1VDEWIDE_2
IDE
E1VDEWQTY
QTY
E1VDEWCCI_4
CCI
E1VDEWCAV_4
CAV
E1VDEWREF_3
REF
E1VDEWDTM_6
DTM
E1VDEWFII_4
FII
E1VDEWREF_4
REF
E1VDEWCTA_2
CTA
E1VDEWCOM_2
COM
UTILMD vs. SAP-UTILMD
Page 7
2 UTILMD Segments This section describes the individual UTILMD 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_1 and is used to display the category and function of a message as well as to transfer the ID number.
BGM E1VDEWBGM_1
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
UTILMD vs. SAP-UTILMD
Page 8
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 the outline contract between distributor and supplier.
REF E1VDEWRFF_1
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference number VERSIONNUMBER
1060 Revision number REVISION
2.5 DTM – Date/Time/Time Frame
Segment DTM is implemented as segment E1VDEWDTM_2 and is used to specify dates of previous RFF segments. For example, the contract date.
DTM E1VDEWDTM_2
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.6 NAD – Name and Address
Segment NAD is implemented as segment E1VDEWNAD_1 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. The supplier and the customer also have to be identified if they differ from the sending and receiving companies.
NAD E1VDEWNAD_1
3035 Participant, qualifier ACTION
3039 Identification of participant PARTNER
1131 Code list, qualifier CODELIST
3055 Place responsible for code maintenance, coded
CODELISTAGENCY
3124 Line for name and address NAMEADDRESS1
3124 Line for name and address NAMEADDRESS2
3124 Line for name and address NAMEADDRESS3
3124 Line for name and address NAMEADDRESS4
3124 Line for name and address NAMEADDRESS5
3036 Name of participant PARTNERNAME1
3036 Name of participant PARTNERNAME2
3036 Name of participant PARTNERNAME3
3036 Name of participant PARTNERNAME4
3036 Name of participant PARTNERNAME5
3045 Name of participant, format, coded PARTNERFORMAT
UTILMD vs. SAP-UTILMD
Page 9
3042 Street and house number or PO box STREET1
3042 Street and house number or PO box STREET2
3042 Street and house number or PO box STREET3
3042 Street and house number or PO box STREET4
3164 City CITY
3229 Region, identification REGION
3251 Postal code ZIPCODE
3207 Country, coded COUNTRY
2.7 FII – Credit Institute
Segment FII is implemented as segment E1VDEWFII_3 and is used to specify the bank details of the partner.
FII E1VDEWFII_3
3035 Participant, qualifier PARTY_ID
3194 Account number ACCOUNT_NUMBER
3192 Account holder ACCOUNT_HOLDER_1
3192 Account holder ACCOUNT_HOLDER_2
6345 Currency, coded ACCOUNT_CURRENCY
3433 Bank, ID BANK_ID
1131 Code list, qualifier BANK_CODE_LIST_1
3055 Place responsible for code maintenance, coded
BANK_RESP_AGENCY_1
3434 Branch number BANK_BRANCH
1131 Code list, qualifier BANK_CODE_LIST_2
3055 Place responsible for code maintenance, coded
BANK_RESP_AGENCY_2
3432 Name of credit institute BANK_NAME
3436 Branch location BANK_BRANCH_PLACE
3207 Country, coded COUNTRY
2.8 CTA – Contact Partner
Segment CTA is implemented as segment E1VDEWCTA and is used to specify a person or department as a contact partner.
CTA E1VDEWCTA
3139 Function of contact partner, coded CONTACTFUNC
3413 Department or agent, identification CONTACTID
3412 Department or agent CONTACTNAME
2.9 COM - Communication
Segment COM is implemented as segment E1VDEWCOM and is used to specify a communication number of a department or a person to use as a contact partner.
UTILMD vs. SAP-UTILMD
Page 10
COM E1VDEWCOM
3148 Communication number COMMNUMBER
3155 Communication method/service, qualifier COMMQUALF
2.10 IDE - Identification
Segment IDE is implemented as segment E1VDEWIDE_2 and is used to identify the object type for which the process described in the message is valid.
IDE E1VDEWIDE_2
7495 Identification, qualifier OBJECT_TYPE
7402 Identification Number ID_NUMBER
7405 Identification number, qualifier ID_CODE
4405 Status, coded ID_STATUS
3039 Identification of participant PARTY_ID
1131 Code list, qualifier PARTY_ID_CODE
3055 Place responsible for code maintenance, coded
PARTY_AGENCY
4405 Status, coded STATUS_DESCR
1222 Configuration level CONF_LEVEL
7164 Hierarchical ID number POS_HIERARCHI
1050 Sequence number POS_SEQUENCE_NR
7037 Characteristic, ID PRODUCT_DESCR
1131 Code list, qualifier PRODUCT_ID
3055 Place responsible for code maintenance, coded
PRODUCT_AGENCY
7036 Characteristic PRODUCT_CHARACTERISTIC_1
7036 Characteristic PRODUCT_CHARACTERISTIC_2
2.11 LOC - Location
Segment LOC is implemented as segment E1VDEWLOC_3 and is used to specify the location to which the master data applies.
LOC E1VDEWLOC_3
3227 Location, qualifier PLACE_QUALIFIER
3225 Location, identification PLACE_ID
1131 Code list, qualifier CODE_LIST_QUALIFIER_1
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_1
3224 Location PLACE
3223 Related place/location 1, identification RELATED_PLACE_COMPANY_1
1131 Code list, qualifier CODE_LIST_QUALIFIER_2
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_2
3222 Related place/location 1 RELATED_PLACE_AREA_1
3233 Related place/location 2, identification RELATED_PLACE_COMPANY_2
UTILMD vs. SAP-UTILMD
Page 11
1131 Code list, qualifier CODE_LIST_QUALIFIER_3
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_3
3232 Related place/location 2 RELATED_PLACE_AREA_2
5479 Allocation, coded RELATION_CODE
2.12 DTM – Date/Time/Time Frame
Segment DTM is implemented as segment E1VDEWDTM_3 and is used to determine the start and/or end of supply and the start of a change.
DTM E1VDEWDTM_3
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.13 STS – Status
Segment STS is implemented as segment E1VDEWSTS_2 and is used to communicate the transaction reason and the response status (for example, acceptance or rejection).
STS E1VDEWSTS_2
9015 Status category, coded CATEGORY
1131 Code list, qualifier CATEGORY_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
CATEGORY_AGENCY
4405 Status, coded STATUS_DESCRIPTION_CODE
1131 Code list, qualifier STATUS_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
STATUS_AGENCY
4404 Status STATUS_DESCRIPTION
9013 Status reason, coded REASON_1_DESCRIPTION_CODE
1131 Code list, qualifier REASON_1_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
REASON_1_AGENCY
9012 Status reason REASON_1_DESCRIPTION
9013 Status reason, coded REASON_2_DESCRIPTION_CODE
1131 Code list, qualifier REASON_2_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
REASON_2_AGENCY
9012 Status reason REASON_2_DESCRIPTION
9013 Status reason, coded REASON_3_DESCRIPTION_CODE
1131 Code list, qualifier REASON_3_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
REASON_3_AGENCY
9012 Status reason REASON_3_DESCRIPTION
9013 Status reason, coded REASON_4_DESCRIPTION_CODE
1131 Code list, qualifier REASON_4_CODE_LIST_ID
UTILMD vs. SAP-UTILMD
Page 12
3055 Place responsible for code maintenance, coded
REASON_4_AGENCY
9012 Status reason REASON_4_DESCRIPTION
9013 Status reason, coded REASON_5_DESCRIPTION_CODE
1131 Code list, qualifier REASON_5_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
REASON_5_AGENCY
9012 Status reason REASON_5_DESCRIPTION
2.14 TAX – Tolls, Taxes, and Fees
Segment TAX is implemented as segment E1VDEWTAX_3. It is used to specify the franchise fee of the service location, or which franchise fee rate is applicable.
TAX E1VDEWTAX_3
5283 Toll/tax/fee class, qualifier DTF_FUNCTION
5153 Toll/tax/fee type, coded TYPE_CODED
1131 Code list, qualifier TYPE_CODE_LIST
3055 Place responsible for code maintenance, coded
TYPE_AGENCY
5152 Toll/tax/fee type TYPE
5289 Indicator for clearing tolls, taxes, and fees ACCOUNT_ID
1131 Code list, qualifier ACCOUNT_CODE_LIST
3055 Place responsible for code maintenance, coded
ACCOUNT_AGENCY
5286 Tolls/taxes/fees, assessment basis ASSESMENT_BASIS
5279 Toll/tax/fee rate, identification DETAIL_RATE_ID
1131 Code list, qualifier DETAIL_CODE_LIST
3055 Place responsible for code maintenance, coded
DETAIL_AGENCY_1
5278 Toll/tax/fee rate DETAIL_RATE
5273 ID of calculation basis for tolls, taxes, and fees
DETAIL_RATE_BASIS
1131 Code list, qualifier DETAIL_CODE_LIST_2
3055 Place responsible for code maintenance, coded
DETAIL_AGENCY_2
5305 Toll/tax/fee category, coded CATEGORY
3446 Tax number PARTY_TAX_ID
1227 Calculation sequence, coded CALCULATION_SEQUENCE
2.15 FTX - Free Text
Segment FTX is implemented as segment E1VDEWFTX_2 and is used to specify unformated or coded texts.
FTX E1VDEWFTX_2
4451 Text allocation, coded TEXT_SUBJECT_QUALIFIER
4453 Text processing note, coded TEXT_FUNCTION_CODE
4441 Free text, coded FREE_TEXT_CODE
UTILMD vs. SAP-UTILMD
Page 13
1131 Code list, qualifier CODE_LIST_QUALIFIER
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY
4440 Free text FREE_TEXT_1
4440 Free text FREE_TEXT_2
4440 Free text FREE_TEXT_3
4440 Free text FREE_TEXT_4
4440 Free text FREE_TEXT_5
3453 Language, coded LANGUAGE
4447 Text format, coded TEXT_FORMAT
In the segment definition, the fields for 4440 are implemented with 190 characters, not 512 characters. This is because the maximum total segment length is 1000 characters.
2.16 AGR – Agreement Identification
Segment AGR is implemented as segment E1VDEWAGR and is used to specify the grid usage contract and the supply type.
AGR E1VDEWAGR
7431 Agreement category, qualifier AGREE_TYPE_ID
7433 Agreement category, description, coded AGREE_TYPE_DESCRIPTION
1131 Code list, qualifier AGREE_TYPE_CODE_LIST
3055 Place responsible for code maintenance, coded
AGREE_TYPE_AGENCY
7434 Agreement category AGREE_TYPE
9419 Service layer, coded SERVICE_LAYER
2.17 INP – Participant for Special Instruction
Segment INP is implemented as segment E1VDEWINP and is used to give instructions regarding device replacement.
INP E1VDEWINP
3301 Sender of instruction, identification INSTRUC_PARTICIPANT_SEND_ID
3285 Receipient of instruction, identification INSTRUC_PARTICIPANT_RECEIVE_ID
4403 Instruction, qualifier INSTRUCTION_ID
4401 Instruction, coded INSTRUCTION_CODE
1131 Code list, qualifier INSTRUCTION_CODE_LIST
3055 Place responsible for code maintenance, coded
INSTRUCTION_CODE_AGENCY
4400 Instruction INSTRUCTION
4405 Status, coded INSTRUCTION_STATUS
3036 Name of participant NAME_PARTICIPANT
1229 Action request/notification, coded ACTION_REQUEST_INFORM
UTILMD vs. SAP-UTILMD
Page 14
2.18 REF – Reference Specifications
Segment REF is implemented as segment E1VDEWRFF_2 and is used to specify references to the point of delivery (LOC segment) or to a previous message. For example, the number of the grid usage contract, the meter number at the point of delivery, or the transaction number of a previous message.
REF E1VDEWRFF_2
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference number VERSIONNUMBER
1060 Revision number REVISION
2.19 DTM – Date/Time/Time Frame
Segment DTM is implemented as segment E1VDEWDTM_4 and is used to specify dates of previous RFF segments. For example, the contract date.
DTM E1VDEWDTM_4
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.20 CCI – Characteristic/Class Identification
Segment CCI is implemented as segment E1VDEWCCI_3 and is used to identify and describe specific characteristics such as the entry type for the relevant point of delivery.
CCI E1VDEWCCI_3
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
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY
7036 Characteristic CHARACTERISTIC_1
7036 Characteristic CHARACTERISTIC_2
2.21 CAV – Characteristic Value
Segment CAV is implemented as segment E1VDEWCAV_3 and is used to specify the characteristic values in the previous CCI segment in more detail.
CAV E1VDEWCAV_3
7111 Characteristic value, coded CHARACTERISTIC_VALUE_CODED
UTILMD vs. SAP-UTILMD
Page 15
1131 Code list, qualifier CODE_LIST_ID
3055 Place responsible for code maintenance, coded
AGENCY
7110 Characteristic value CHARACTERISTIC_VALUE_1
7110 Characteristic value CHARACTERISTIC_VALUE_2
2.22 SEQ – Sequence Details
Segment SEQ is implemented as E1VDEWSEQ_2 and is used to introduce the segment group. The segment is used exclusively for numbering segment group 7.
SEQ E1VDEWSEQ_2
1229 Action request ACTION_REQUEST
1050 Sequence number SEQU_INFOS_SEQUENCENR
1159 Sequence number source, coded SEQU_INFOS_SEQUENCENR_CODE
1131 Code list, qualifier SEQU_INFOS_CODE_LIST
3055 Place responsible for code maintenance, coded
SEQU_INFOS_AGENCY
2.23 PIA – Additional Product Identification
Segment PIA is implemented as segment E1VDEWPIA_2 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 data in the German energy industry.
PIA E1VDEWPIA_2
4347 Product identification function, qualifier PRODUCT_ID
7140 Product/service number ITEM_NUMBER_1
7143 Product/service number, type, coded ITEM_NUMBER_TYPE_1
1131 Code list, qualifier CODE_LIST_QUALIFIER_1
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_1
7140 Product/service number ITEM_NUMBER_2
7143 Product/service number, type, coded ITEM_NUMBER_TYPE_2
1131 Code list, qualifier CODE_LIST_QUALIFIER_2
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_2
7140 Product/service number ITEM_NUMBER_3
7143 Product/service number, type, coded ITEM_NUMBER_TYPE_3
1131 Code list, qualifier CODE_LIST_QUALIFIER_3
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_3
7140 Product/service number ITEM_NUMBER_4
7143 Product/service number, type, coded ITEM_NUMBER_TYPE_4
1131 Code list, qualifier CODE_LIST_QUALIFIER_4
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_4
7140 Product/service number ITEM_NUMBER_5
UTILMD vs. SAP-UTILMD
Page 16
7143 Product/service number, type, coded ITEM_NUMBER_TYPE_5
1131 Code list, qualifier CODE_LIST_QUALIFIER_5
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_5
2.24 QTY – Quantity
Segment QTY is implemented as segment E1VDEWQTY as is used to specify quantities for items. For example, estimated quantities or reserve capacity.
QTY E1VDEWQTY
6063 Quantity, qualifier QUANTITY_QUALIFIER
6060 Quantity QUANTITY
6411 Measurement unit, qualifier MEASURE_UNIT_QUALIFIER
2.25 CCI – Characteristic/Class Identification
Segment CCI is implemented as segment E1VDEWCCI_4 and is used to identify and describe specific characteristics. These specifications refer to the previous SEQ segment.l Meter characteristics (such as constants) are specified as required in the next CAV segment.
CCI E1VDEWCCI_4
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
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY
7036 Characteristic CHARACTERISTIC_1
7036 Characteristic CHARACTERISTIC_2
2.26 CAV – Characteristic Value
Segment CAV is implemented as segment E1VDEWCAV_4 and is used to specify the characteristic values in the previous CCI segment in more detail.
CAV E1VDEWCAV_4
7111 Characteristic value, coded CHARACTERISTIC_VALUE_CODED
1131 Code list, qualifier CODE_LIST_ID
3055 Place responsible for code maintenance, coded
AGENCY
7110 Characteristic value CHARACTERISTIC_VALUE_1
7110 Characteristic value CHARACTERISTIC_VALUE_2
UTILMD vs. SAP-UTILMD
Page 17
2.27 MOA – Monetary Amount
Segment MOA is implemented as segment E1VDEWMOA_6 and is used to specify the budget billing amount to be paid for the relevant point of delivery, product, or service.
MOA E1VDEWMOA_6
5025 Monetary amount type, qualifier MONETARY_AMOUNT_TYPE
5004 Monetary amount MONETARY_AMOUNT_VALUE
6345 Currency, coded CURRENCY_ID
6343 Currency qualifier CURRENCY_QUALIFIER
4405 Status, coded STATUS
2.28 REF - Reference Specifications
Segment REF is implemented as segment E1VDEWRFF_3. This segment contains references for (future) budget billing payments.
REF E1VDEWRFF_3
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference version number VERSIONNUMBER
1060 Revision number REVISION
2.29 DTM – Date/Time/Time Frame
Segment DTM is implemented as segment E1VDEWDTM_6 and is used to specify dates and periods for the previous RFF segment. For example, the due date and the rhythm for further payments.
DTM E1VDEWDTM_6
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.30 NAD – Name and Address
Segment NAD is implemented as segment E1VDEWNAD_4 and is used to identify the business partner(s) involved in the process at the level of the service location. For example, end customer or settlement area coordinator.
NAD E1VDEWNAD_4
3035 Participant, qualifier ACTION
3039 Identification of participant PARTNER
1131 Code list, qualifier CODELIST
3055 Place responsible for code maintenance, coded
CODELISTAGENCY
3124 Line for name and address NAMEADDRESS1
3124 Line for name and address NAMEADDRESS2
UTILMD vs. SAP-UTILMD
Page 18
3124 Line for name and address NAMEADDRESS3
3124 Line for name and address NAMEADDRESS4
3124 Line for name and address NAMEADDRESS5
3036 Name of participant PARTNERNAME1
3036 Name of participant PARTNERNAME2
3036 Name of participant PARTNERNAME3
3036 Name of participant PARTNERNAME4
3036 Name of participant PARTNERNAME5
3045 Name of participant, format, coded PARTNERFORMAT
3042 Street and house number or PO box STREET1
3042 Street and house number or PO box STREET2
3042 Street and house number or PO box STREET3
3042 Street and house number or PO box STREET4
3164 City CITY
3229 Region, identification REGION
3251 Postal code ZIPCODE
3207 Country, coded COUNTRY
2.31 REF - Reference Specifications
Segment REF is implemented as segment E1VDEWRFF_4 and is used to specify references to the previous NAD segment. For example, the customer number.
REF E1VDEWREF_4
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference version number VERSIONNUMBER
1060 Revision number REVISION
2.32 FII – Credit Institute
Segment FII is implemented as segment E1VDEWFII_4 and is used to specify the bank details of the partner from the previous NAD segment. For example, if payment should be made to a separate account.
FII E1VDEWFII_4
3035 Participant, qualifier PARTY_ID
3194 Account number ACCOUNT_NUMBER
3192 Account holder ACCOUNT_HOLDER_1
3192 Account holder ACCOUNT_HOLDER_2
6345 Currency, coded ACCOUNT_CURRENCY
3433 Bank, ID BANK_ID
1131 Code list, qualifier BANK_CODE_LIST_1
UTILMD vs. SAP-UTILMD
Page 19
3055 Place responsible for code maintenance, coded
BANK_RESP_AGENCY_1
3434 Branch number BANK_BRANCH
1131 Code list, qualifier BANK_CODE_LIST_2
3055 Place responsible for code maintenance, coded
BANK_RESP_AGENCY_2
3432 Name of credit institute BANK_NAME
3436 Branch location BANK_BRANCH_PLACE
3207 Country, coded COUNTRY
2.33 CTA – Contact Partner
Segment CTA is implemented as segment E1VDEWCTA_2 and is used to identify contact partners within the company specified in the previous NAD segment.
CTA E1VDEWCTA_2
3139 Function of contact partner, coded CONTACTFUNC
3413 Department or agent, identification CONTACTID
3412 Department or agent CONTACTNAME
2.34 COM - Communication
Segment COM is implemented as segment E1VDEWCOM_2 and is used to specify the communication number and the communication category of the agent or department specified in the previous CTA segment.
COM E1VDEWCOM_2
3148 Communication number COMMNUMBER
3155 Communication method/service, qualifier COMMQUALF
2.35 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 UTILMD 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 UTLIMD. This XML schema for UTILMD 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.
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.