EDM IDE DELFOR
-
Upload
gergo-paksy -
Category
Documents
-
view
31 -
download
7
description
Transcript of EDM IDE DELFOR
Siar Sarferaz Consulting Utilities
DELFOR vs. SAP-DELFOR
DL: History:
VV2@SAP
Version Status Datum
1.0 Draft 30.08.2002
DELFOR vs. SAP-DELFOR
Page 2
Table of Contents
1 General ..................................................................................................................................... 4
2 DELFOR Segments.................................................................................................................. 5
2.1 UNH – Message Header.........................................................................................................................................6
2.2 BGM – Start of Message........................................................................................................................................6
2.3 DTM – Date/Time/Time Frame...............................................................................................................................6
2.4 REF – Reference Specifications ...........................................................................................................................6
2.5 DTM – Date/Time/Time Frame...............................................................................................................................7
2.6 NAD – Name and Address.....................................................................................................................................7
2.7 CTA – Contact Partner...........................................................................................................................................8
2.8 COM - Communication ..........................................................................................................................................8
2.9 GIS – General Indicator .........................................................................................................................................8
2.10 NAD – Name and Address .............................................................................................................................8
2.11 CTA – Contact Partner ...................................................................................................................................9
2.12 COM - Communication...................................................................................................................................9
2.13 LIN – Item Number ..........................................................................................................................................9
2.14 PIA – Additional Product Identification ......................................................................................................10
2.15 LOC - Location ..............................................................................................................................................11
2.16 DTM – Date/Time/Time Frame .....................................................................................................................11
2.17 FTX - Free Text..............................................................................................................................................11
2.18 REF - Reference Specifications ..................................................................................................................12
2.19 SCC – Schedule Requirements ...................................................................................................................12
2.20 QTY – Quantity..............................................................................................................................................12
2.21 DTM – Date/Time/Time Frame .....................................................................................................................13
2.22 NAD – Name and Address ...........................................................................................................................13
2.23 LOC - Location ..............................................................................................................................................14
2.24 CTA – Contact Partner .................................................................................................................................14
2.25 COM - Communication.................................................................................................................................14
2.26 QTY – Quantity..............................................................................................................................................14
DELFOR vs. SAP-DELFOR
Page 3
2.27 UNT – End of Message Segment.................................................................................................................15
Copyright................................................................................................................................... 16
DELFOR vs. SAP-DELFOR
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) has defined a number of message categories in order to standardize information exchange. These include the following message categories:
Message category
Use 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 DELFOR message category and the corresponding SAP implementation. Message category DELFOR is used for communication between business partners within the energy industry. It contains specifications for future energy supply (schedules). It can be used to announce or request fixed schedules or to enquire about free capacity. Another use is to respond to a schedule with a confirmation, a rejection, or with adjustments. Version 1.2g of DELFOR was released on 26.10.2001. The figure below describes the individual segments of DELFOR and the corresponding SAP structures: A DELFOR message consists of the following segments:
• Start of message (UNH, BGM)
• Message date (DTM)
• Reference with date (REF, DAT)
• Sender and recipient ID (NAD, CTA, COM)
• Schedule status or category (GIS)
• Requester (NAD, CTA, COM)
• Current item (LIN)
• EDIS ID (PIA)
• Reference point (LOC)
• Reference date (DTM)
• Free text (FTX)
• Transaction number or version (REF)
• Start of profile (SCC)
• Quantity specifications (QTY)
• Time specifications (DTM)
• Buyer/seller/coordinator (NAD)
DELFOR vs. SAP-DELFOR
Page 5
• Control area allocation supplied or to supply (LOC, CTA. COM)
• Reserve (QTY)
• Message end (UNT)
2 DELFOR Segments This section describes the individual DELFOR segments and the corresponding SAP data structures.
DELFOR vs. SAP-DELFOR
Page 6
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 or a previous supply schedule (DELFOR).
DELFOR vs. SAP-DELFOR
Page 7
REF E1VDEWREF_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 request 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 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
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
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
DELFOR vs. SAP-DELFOR
Page 8
3164 City CITY
3229 Region, identification REGION
3251 Postal code ZIPCODE
3207 Country, coded COUNTRY
2.7 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, identifier CONTACTID
3412 Department or agent CONTACTNAME
2.8 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.
COM E1VDEWCOM
3148 Communication number COMMNUMBER
3155 Communication method/service, qualifier COMMQUALF
2.9 GIS – General Indicator
Segment GIS is implemented as segment E1VDEWGIS and is used to specify the status and the type of the transfer services/schedules. Multiple schedules can be allocated together in a message.
GIS E1VDEWGIS
7365 Process indicator, coded PROCESS_INDICATOR
1131 Code list, qualifier CODELIST
3055 Place responsible for code maintenance, coded
CODELISTAGENCY
7187 Process type, identification PROCESS_TYPE
2.10 NAD – Name and Address
Segment NAD is implemented as segment E1VDEWNAD_2 and is used to specify the name, address, and function of a partner.
NAD E1VDEWNAD_2
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
DELFOR vs. SAP-DELFOR
Page 9
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
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.11 CTA – Contact Partner
Segment CTA is implemented as segment E1VDEWCTA_2 and is used to specify a person or department to use as a contact partner.
CTA E1VDEWCTA_2
3139 Function of contact partner, coded CONTACTFUNC
3413 Department or agent, identification CONTACTID
3412 Department or agent CONTACTNAME
2.12 COM - Communication
Segment COM is implemented as segment E1VDEWCOM_2 and is used to specify a communication number of a department or a person to use as a contact partner.
COM E1VDEWCOM_2
3148 Communication number COMMNUMBER
3155 Communication method/service, qualifier COMMQUALF
2.13 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.
LIN E1VDEWLIN
1082 Item number LINE_ITEM_NUMBER
DELFOR vs. SAP-DELFOR
Page 10
1229 Action request/notification, coded ACTION_REQUEST_NOT_CODE
7140 Product/service number ITEM_NUMBER
7143 Product/service number, type, coded ITEM_NUMBER_TYPE
1131 Code list, qualifier CODE_LIST_QUALIFIER
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY
5495 Display for subitem, coded SUBLINE_INDICATOR
1082 Item number SUBLINE_ITEM_NUMBER
1222 Configuration level CONFIGURATION_LEVEL
7083 Subitem allocation coded CONFIGURATION
2.14 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.
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
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
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
DELFOR vs. SAP-DELFOR
Page 11
2.15 LOC - Location
Segment LOC is implemented as segment E1VDEWLOC and is used to specify the location to which the data applies. For example, the reference point.
LOC E1VDEWLOC
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
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.16 DTM – Date/Time/Time Frame
Segment DTM is implemented as segment E1VDEWDTM_3 and is used to determine the validity date or the validity period.
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.17 FTX - Free Text
Segment FTX is implemented as segment E1VDEWFTX and is used to specify unformated or coded texts that refer to an individual item. For example, a rejection reason. Use of this segment in free form is not recommended as it affects automatic processing for the message. A better option is to agree upon coded references, which allow automatic processing and reduces the number of characters to be transferred. The standard texts should be agreed upon by the data exchange participants and can fulfill legal and other requirements.
FTX E1VDEWFTX
4451 Text allocation, coded TEXT_SUBJECT_QUALIFIER
4453 Text processing note, coded TEXT_FUNCTION_CODE
4441 Free text, coded FREE_TEXT_CODE
1131 Code list, qualifier CODE_LIST_QUALIFIER
DELFOR vs. SAP-DELFOR
Page 12
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
2.18 REF - Reference Specifications
Segment REF is implemented as segment E1VDEWRFF_2 and is used to determine the transaction number (part of schedule key) of the profile. If the transaction number is not found, a point of delivery ID (synthetic if possible) is generally used in SG12/LOC.
REF E1VDEWREF_2
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference version number VERSIONNUMBER
1060 Revision number REVISION
2.19 SCC – Schedule Requirements
Segment SCC is implemented as segment E1VDEWSCC and introduces an individual profile into a transaction. It is possible to allocate multiple profiles to a transaction, for example, if the time intervals in a profile are very short, or if the request period is very long.
SCC E1VDEWSCC
4017 Supply schedule status display, coded DELIVERY_PLAN_STATUS
4493 Supply request, coded DELIVERY_REQUEST
2013 Frequency, coded FREQUENCY
2015 Supply schedule, coded DELIVERY_SCHEDULE
2017 Delivery time schedule, coded DELIVERY_TIME
2.20 QTY – Quantity
Segment QTY is implemented as segment E1VDEWQTY as is used to specify quantities for items. For example, quarter hour values.
QTY E1VDEWQTY
6063 Quantity, qualifier QUANTITY_QUALIFIER
6060 Quantity QUANTITY
6411 Measurement unit, qualifier MEASURE_UNIT_QUALIFIER
DELFOR vs. SAP-DELFOR
Page 13
2.21 DTM – Date/Time/Time Frame
Segment DTM is implemented as segment E1VDEWDTM_4 and contains data and time specifications for the quantity-related data in the previous QTY segment. This refers to the run period (for a profile) or the time of a value.
DTM E1VDEWDTM_4
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame FORMAT
2.22 NAD – Name and Address
Segment NAD is implemented as segment E1VDEWNAD_3. Buying and selling settlement area coordinators are identified when the schedule is registered. If the buyer or seller is not the settlement area coordinator, it must be identified separately. This segment is also used to identify the supply location, the generator, the customer, and the operator depending on the supply schedule category. The supply location is the payer’s address at the point where the product/service is received. The parties involved are displayed based on the profile.
NAD E1VDEWNAD_3
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
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
DELFOR vs. SAP-DELFOR
Page 14
2.23 LOC - Location
Segment LOC is implemented as segment E1VDEWLOC_2 and is used to specify the location to which the data applies.
LOC E1VDEWLOC_2
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
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.24 CTA – Contact Partner
Segment CTA is implemented as segment E1VDEWCTA_3 and is used to identify contact partners within the company specified in the previous NAD segment.
CTA E1VDEWCTA_3
3139 Function of contact partner, coded CONTACTFUNC
3413 Department or agent, identification CONTACTID
3412 Department or agent CONTACTNAME
2.25 COM - Communication
Segment COM is implemented as segment E1VDEWCOM_3 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_3
3148 Communication number COMMNUMBER
3155 Communication method/service, qualifier COMMQUALF
2.26 QTY – Quantity
Segment QTY is implemented as segment E1VDEWQTY_2 and is used to specify standby energy for the current item with reference to the generator identified in the previous NAD segment.
DELFOR vs. SAP-DELFOR
Page 15
QTY E1VDEWQTY_2
6063 Quantity, qualifier QUANTITY_QUALIFIER
6060 Quantity QUANTITY
6411 Measurement unit, qualifier MEASURE_UNIT_QUALIFIER
2.27 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
DELFOR vs. SAP-DELFOR
Page 16
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.