IUT235_Col51_Real_Time_Pricing__RTP__.pdf
April 13, 2017 | Author: akelius | Category: N/A
Short Description
Download IUT235_Col51_Real_Time_Pricing__RTP__.pdf...
Description
IUT235 Real Time Pricing
IUT235
Real Time Pricing (RTP)
THE BEST-RUN BUSINESSES RUN SAP SAP AG 2004 SAP AG©2003
SAP IS-Utilities/Customer Care Service 472
2005/Q1
Material number: 50071395
© SAP AG
IUT235
0-1
Copyright
Copyright 2004 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.
SAP AG 2004
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.
© SAP AG
IUT235
0-2
Course Prerequisites
z IUT110 Introduction to the IS-U/CCS System z IUT225 Energy Data Management z IUT230 Billing and Invoicing
SAP AG 1999
© SAP AG
IUT235
0-3
Target Group
z Audience:
Project leader
Project team
Consultants
z Duration: 2 days
SAP AG 1999
User notes
These training materials are not a teach-yourself program. They compliment the explanations provided by your course instructor. Space is provided on each page for you to note down additional information.
There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.
© SAP AG
IUT235
0-4
Course Goals
At the end of this course, you will be able to: z Understand the definition of complex billing,
RTP billing, and time-of-use pricing z Describe the functional scope of the RTP interface z Understand how RTP billing is integrated in IS-U/CCS z Create, maintain, and customize
an RTP interface in the IS-U/CCS system billing in the IS-U/CCS system.
SAP AG 1999
© SAP AG
IUT235
0-5
Course Content
Preface Unit 1
Introduction to the RTP interface
Unit 2
Review of IS/U-CCS Billing
Unit 3
Elements of an RTP interface
Unit 4
Customizing settings for the RTP interface
Unit 5
Exercises: Execute RTP interface
SAP AG 2003
© SAP AG
IUT235
0-6
Introduction to Real Time Pricing Billing
Business functions enabled by complex billing Definition of the RTP interface RTP interface within IS-U/CCS Review of relevant EDM topics from IUT225
SAP AG 2003
© SAP AG
IUT235
1-1
Course Objectives
At the conclusion of this unit, you will be able to: z Describe the need for the RTP interface within
IS-U/CCS. z Explain how the RTP interface can be used to
support complex billing. z Articulate the function of the RTP interface. z Describe the meaning of the RTP interface within
IS-U/CCS
SAP AG 2003
© SAP AG
IUT235
1-2
Business Functions Enabled by Complex Billing
Business functions enabled by complex billing Definition of the RTP interface RTP interface within IS-U/CCS Review of relevant EDM topics from IUT225
SAP AG 2003
© SAP AG
IUT235
1-3
The mySAP Utilities Solution
Components in the Solution Map
IDE
Communication data
EDM
Energy Data Management
IS-U
Sales, billing, customer service
SAP AG 2003
Having been a monopoly in a regulated utilities market, the utilties economy is fast becoming a competition-focused energy and service economy. This is an international development, but the degree of liberalization may vary considerably between regions and regions may use different deregulation rules or guidelines.
Breaking up the value creation chain has required the IT structure of a company to be modified accordingly, which in turn leads to information systems being separated. The new business areas or companies (such as sales, billing, energy data management, grid operation) only store data in their information systems, which they require for their respective business area.
© SAP AG
IUT235
1-4
Electronic Data Exchange Transfers consumption values, meter readings etc.
Distribution Company
Suppliesenergy energy by , Supplies sends the bill and sends the bill and performs to customers payment clearing by
Electronic data exchange Transfers changes to rate information from customer data etc
Supplier
Agrees energy supply contract with customers and supplies energy
Customer SAP AG 2003
Data exchange can only function efficiently if all communication partners define a collective communication standard, in other words, if they all speak the same electronic language. This communication standard can be defined at state or regulatory level, by collective associations within the industry or can be agreed using bilateral agreements between individual communication partners.
© SAP AG
IUT235
1-5
Three Pillars of EDM Energy Data Repository
EDM
Real-TimePricing
Settlement and schedule management
SAP AG 2003
Energy Data Management is a solution which provides functions for measuring load shapes, energy settlement, schedule management and billing of interval energy consumption.
Numerous settlement data flows required can be represented using SAP IS-Utilities. Consumption data that is determined and managed in component SAP IS-U-EDM, is transferred during settlement. With the help of the processes provided by component SAP IS-U-IDE, this data can be communicated to other market participants.
The billing of interval-related data (profiles) is called real time pricing billing (RTP billing). RTP billing allows you to define rates and prices freely across intervals and therefore enables you to structure contracts that are required in a deregulated energy market more freely.
© SAP AG
IUT235
1-6
IS-U/CCS Concept With EDM
IS-U/CCS with EDM
EDI/XML
Download Data Entry
MD
E
Upload
Meter
MR doc uments
Print Data Entry
ZP data
IMPORT / EXPORT
Load shape Meter
IMPORT / EXPORT
Signal
AMR system
Interfaces to other applications
Load shape data
IS-U Energy Data Repository
Download
RTP / TOU Billing
Discrete data
EDI/XML
Customer meter reading
Settlement
Customer/ contract data Device Management Invoice Contract Accounts Receivable & Payable Date control IS-U/CCS component
WWW SAP AG 2003
© SAP AG
IUT235
1-7
Why is the RTP Interface Needed?
Bill on/ off-peak periods
Support deregulation
Bill timeof-use types
Calculate interval data
IS-U/CCS
Bill day types
Complex billing RTP interface
SAP AG 1999
RTP-Interface is needed to support the following: y Billing of weekend/weekday periods y Billing of on/off-peak periods y Billing of seasons such as summer, winter, spring, fall y Calculations based on profile data, such as measured load shapes y Complex billing such as TOU, spot pricing, and RTP (covered in detail in the following slides)
These functions necessitate the use of flexible formula calculations that support multiple billing requirements.
© SAP AG
IUT235
1-8
Complex Billing Using the RTP Interface
Spot billing
TOU Time-of-use pricing
RTP interface
RTP Real time pricing
SAP AG 2003
The RTP interface enhances IS-U Billing to encompass the scope of complex billing.
Complex billing can be divided into three function groups. These are: y Time-of-use pricing (TOU Pricing) y Real-time pricing y Spot billing
You can use RTP billing to calculate time-of-use pricing models and RTP models. You can define prices in advance or adjust prices to the spot price defined by the energy market.
The billing types used in complex billing are described in the detail on the following slides.
© SAP AG
IUT235
1-9
Cross-Application Function: TOU Billing
kW
60
30
10
00:00
12:00
24:00
5. Dec. 2003
6. Dec. 2003
Group 1 Price A
Group 2 Price B
Group 3 Price C
Group 4 Price D
Group 5 Price E
Group 6 Price F
Time-of-use pricing (TOU): z Various prices according to the time of day, day type or season (time block) SAP AG 2003
Time-of-use energy billing is based on the aggregation of energy quantities over pre-defined periods. A profile, such as a measured load shape, forms the basis for this billing.
In TOU, the RTP interface determines the following: y Consumption groups y Peak values, such as maximum demand (if required)
You can use hierarchies to define the consumption periods. A time hierarchy can be created from the following elements: y Seasons, such as summer/winter y Day types, such as working day, public holiday, weekend day y Time of the day, such as on/off-peak times
© SAP AG
IUT235
1-10
TOU Pricing
Quantity B Quantity C
Quantity A
Timedependent limit 1
Timedependent limit 2
SAP AG 2003
© SAP AG
IUT235
1-11
Cross-Application Function: RTP Billing Spot price
kW
60 Load shape measured 30
10
00:00 5. Oct. 2000
12:00
24:00 rt = 60 min
6. Oct. 2000
Agreed price
Example of real time pricing (RTP) z
A new price every 15 minutes
z
Consumption within agreed reference quantity (orange) = agreed price
z
Consumption beyond agreed reference quantity (red) = spot price SAP AG 2003
Real-time pricing is the billing of energy based on energy quantities determined over pre-defined periods of time.
Each interval is valuated separately.
Within an interval you can define any number of value limits and the energy quantities that exceed/fall below these limits can be determined.
© SAP AG
IUT235
1-12
RTP and TOU Pricing
Energydependent limitation*
Time-dependent limit 1 )* Fixed value, profile, schedules etc.
Timedependent limit 2
SAP AG 2003
© SAP AG
IUT235
1-13
Spot Pricing with the RTP Interface Special delivery
Spot price kW
OK
60
OK
OK
ok
ok OK
ok
ok
ok
OK
OK
OK
ok OK OK OK
OK OK
30 OK
OK OK
OK OK OK
OK
OK
OK OK OK
OK
OK OK
OKOK OK OK OK
OK OK
OK OK
OK OK OK OK OK
OK
OK
10
00:00 5. Oct. 2003
12:00 t = 60 min
Period 1 Price A
Period 2 Price B
Group 3 Price C t = 60 min
24:00
Time period 4 Price D
Time period 5 Price E
6. Oct. 2003
Time period 6 Price F
Agreed price SAP AG 2003
Spot pricing: y The spot price is the current market price at which energy can be purchased at short notice (from an energy exchange, for example). y RTP billing can be used to determine the energy quantity that can then be priced using the spot price.
You can also model special agreements that were made with the energy customer.
In the example above, a short term contract is sold to the customer for the time period between 12:00 and 13:00 on 05.10.03 y Customer pays the spot price for consumption above the baseline y Customer pays the spot price for consumption below the baseline y Customer's existing rate is a TOU rate.
© SAP AG
IUT235
1-14
RTP, TOU and Spot Pricing
x
€
Time-Based Price
SAP AG 2003
© SAP AG
IUT235
1-15
Definition of the RTP Interface
Business functions enabled by complex billing Definition of the RTP Interface RTP interface within IS-U/CCS Review of relevant EDM topics from IUT225
SAP AG 2003
© SAP AG
IUT235
1-16
IS-U/CCS Concept With EDM
EDI EDI EDI Profile data
3rd Party System
POD data
EDI/XML
EDIFACT Message (Type MSCONS or XML)
Discrete data
IS-U Energy Data Repository
Point of delivery (POD)
EDI EDI EDI
SAP AG 2003
IS-U-EDM allows you to prepare for RTP billing. An internal interface transfers prepared RTP data to the IS-U billing component. Unlike conventional IS-U billing, RTP billing allows you to bill very small units of time (such as data from 15-minute intervals). These units of time correspond to the time units of the interval data measured.
Profile values are recorded in the Energy Data Repository in the IS-U-EDM component. The point of delivery is used as a collective communication object between an automated meter reading system (AMRS) and IS-U.
© SAP AG
IUT235
1-17
What is the Real-Time Pricing Interface? IS-U/CCS
IS-U-EDM Link between interval data and traditional billing
Download
Signal
AMR system
Device Management
PoD
RTP interface
Profile
(register code)
3rd party system e.g. IS-U
Customer data
Energy Data Repository
Invoicing
Billing
Contract Accounts A/R & A/P
EDI/XML
Scheduling
New rates are developed to manage interval billing - RTP
Other modules
SAP AG 2003
The RTP interface links the profile data contained in EDM (IS-U-EDM) with the IS-U Billing (IS-U-BI). In order to do this, the RTP interface is allocated to the rate used for billing an interval meter This link serves to: y Bill interval-related data (complex billing) y Transfer energy values from the Energy Data Management (IS-U-EDM) component to the Billing (ISU-BI) component. y Flexibly model and bill commercial and industrial utility customers as well as other large accounts.
© SAP AG
IUT235
1-18
RTP Billing
Quantity A
Energydependent limitation*
Quantity B
)* Fixed value, profile, schedules etc. SAP AG 2003
The starting point is always a measured load shape, which provides the consumption values with date information and a consumption period (5, 10, 15, 30 or 60 minute intervals) in a detailed format. This load shape can now be "cut" vertically or horizontally for various points in time.
© SAP AG
IUT235
1-19
Functions in the RTP Interface I z Operations performed on a profile Calculates peak values in a period Sums values for a period
For example: A discrete value can be derived from a profile
60 40
Load profile
20
Profile values
z Determine peak z Sum values z Subtract
+/-
Value 100kWh
SAP AG 2003
Profile values are stored in EDM.
The RTP interface only transfers discrete values to Billing.
The discrete values result from a mathematical formula definition that forms part of the RTP interface.
© SAP AG
IUT235
1-20
Functions in the RTP Interface II
Billing Rate cat.
Billing lines
Rate type
Rate determination
Value
Billing schema Rate step 1 Rate step 2 Rate step 3
SAP AG 2003
The results (values) from the RTP interface are transferred to rate steps in the rate within IS-U/CCS Billing.
The operands receive the values via the rate facts.
© SAP AG
IUT235
1-21
IS-U/EDM: RTP Billing
RTP Billing
Time restriction
Energy dependent restriction (*)
(*) Can also be a profile e.g. schedule
SAP AG 2003
© SAP AG
IUT235
1-22
RTP interface Within IS-U/CCS
Business functions enabled by complex billing Definition of the RTP Interface RTP interface Within IS-U/CCS Review of relevant EDM topics from IUT225
SAP AG 2003
© SAP AG
IUT235
1-23
RTP Interface Within IS-U Data Model Installation
A.) Individual RTP Interface – set up in the INSTALLATION and is only used for billing on installation of the customer
Rate cat.
Ind. RTP interface
Log register
Rate type
PI12
Rate
PI22
B.) General RTP interface assigned through the RATE
RTP interface
P1
P2
P12
...
LUMSUM02 RTPAMNT; ONE DEMAND01 VERLEIS; LEIPREI
SAP AG 2003
Variant programs
P= profile
...
The RTP interfaces enables you to bill energy using profiles.
An RTP interface is allocated in the rate header data.
Special agreements for given customers can be modeled in an individual RTP interface. An individual RTP interface has priority over the general interface.
An individual RTP interface is allocated to the utility installation.
© SAP AG
IUT235
1-24
IS-U/EDM Integration
Business applications E OL
P RT face er int
IS-U/CCS Billing Engine
Automated meter reading systems
PI BA
al ern e Int erfac int
IS-U/CCS Other functions
External systems
c IDo
Energy Data Repository
Profile Management
E
tor ac x tr
External
other enterprises al ern Int terin ce fa
IDE
Clearing House
Business Information Warehouse Customer Relationship Management SAP System
Further processing
Office applications
Industry solution
Internal to enterprise
Other applications
Internal interfaces
External interfaces
SAP AG 2003
© SAP AG
IUT235
1-25
Functions of the Energy Data Repository Energy Data Repository
Meter
ZFA System
BAPI Profile
POD MR Result
IDoc
Meter EDI
Energy Data Repository
EDI - Electronic Data Interchange
Import
Consistency Checks
Replacement values
Evaluation and then analysis
Archive Status Management
SAP AG 2003
© SAP AG
IUT235
1-26
OLE Interface
Profile values status
Profile header data
Profile values
SAP AG 2003
Display and preparation of profiles Microsoft® Excel has been integrated into IS-U-EDM via an OLE (object linking and embedding) interface. This interface allows you to: y Display profile values in Microsoft® Excel. y Change profile values in Excel and save the changes in an Excel file. y Export profile values (including status) from SAP IS-U-EDM to an Excel file and edit them at your workstation. y Import elementary profile values (including status) from an Excel file into SAP IS-U-EDM.
© SAP AG
IUT235
1-27
EDM: Review of Key Points
Business functions enabled by complex billing Definition of the RTP Interface RTP interface Within IS-U/CCS Review of relevant EDM topics from IUT225
SAP AG 2003
© SAP AG
IUT235
1-28
Overview of Central EDM Topics
z Time-of-use groups
z Interval lengths
z Day groups
z Profile values
z Season groups
z Replacement values
z Profile creation
z Formulas
z Profile roles
z Formula profiles
SAP AG 2003
Profile roles In the setup of the input parameters in the RTP interface, a profile role or an actual profile number can be assigned.
Formulas Formulas define the calculations that take place when an RTP interface is executed. You allocate a formula to an RTP interface. When you choose a formula, you define input parameters to be supplied to the interface as well as the output parameters available.
Formula profiles Formulas are used in the RTP interface to model the interval-related portion of the rate. Formulas are also used to calculate one formula profile from any number of individual profiles.
© SAP AG
IUT235
1-29
Consistency Checks
From-time To-time Value 00:00:00 00:14:59 10.000 00:00:00 00:14:59 10.000 00:15:00 00:29:59 9.000 00:30:00 00:44:59 10.200 01:00:00 01:14:59 5.020 01:15:00 01:29:59 10.010 01:30:00 01:44:59 11.000 02:00:00 02:14:59 7.014
Check for gaps
To-time Value 00:14:59 10.000 00:29:59 100.000 00:44:59 10.200 01:14:59 5.020 01:29:59 10.010 01:44:59 11.000 02:14:59 7.014
To-time Value 00:14:59 10.000 00:29:59 9.000 00:44:59 10.200
01:15:00 01:29:59 01:30:00 01:44:59 02:00:00 02:14:59
Overlap check
10.010 11.000 7.014
From-time To-time
Complete ness check From-time 00:00:00 00:15:00 00:30:00 01:00:00 01:15:00 01:30:00 02:00:00
From-time 00:00:00 00:15:00 00:30:00
00:00:00 00:15:00 00:30:00 01:00:00 01:15:00 01:30:00 02:00:00
00:14:59 00:29:59 00:44:59 01:14:59 01:29:59 01:44:59 02:14:59
Value 10.000 9.000 10.200 10.010 11.000 7.014
Tolerance check
SAP AG 2003
You can use consistency checks to check the data import between profile imports, for example to perform a consistency check for overlapping data.
Several consistency checks can be allocated to consistency check groups.
This enables you to perform several consistency checks during a profile import and to trigger various follow-up actions if errors occur.
Action to Take After Errors in Consistency Check y An action determines how to proceed with profile values after an error has occurred when they are imported. The following actions for errors in the consistency check are defined by SAP: - Profile values are saved. - Profile values are not saved. Terminate import. - Profile values are saved in spite of the error.
In the profile header data, you can then choose from previously defined consistency check groups.
© SAP AG
IUT235
1-30
Replacement Values
KW
Extrapolation Extrapolation
50 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
30 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
00:00
01.10.2002
12:00
24:00
Interpolation Interpolation
02.10.2002
SAP AG 2003
In the context of energy data management, values must be provided to replace missing or implausible profile values.
In addition, forecast values for profiles must be created for settlement simulations or schedule creation, for example.
With help from replacement value procedures and replacement value procedure groups, you can determine how replacement values are created for profiles managed in IS-U-EDM.
A function module that executes the replacement value creation is allocated to every replacement value procedure. Customers can therefore define their own replacement value procedures very easily.
SAP provides seven sample replacement value procedures.
© SAP AG
IUT235
1-31
Replacement Values Procedure - Linear, Max/Min Linear replacement values procedure 70 60 50 40
Maximum value replacement values procedure
30 20
Missing values 90 6080 70 50 60 4050 40 30 30 20 20 1010 0 0
10 0
70
70100 60
80
50
East
40
60
East
West
30
40
West
North
20
20
10 0
North
0 1. Qrtl. 2. Qrtl. 3. Qrtl. 4. Qrtl.
Minimum value replacement values procedure
1. Qrtl. 2. Qrtl. 3. Qrtl. 4. Qrtl. 70
100
60
80
50
60
East
30
40
West
20
20
40
10 0
North
0 1. Qrtl. 2. Qrtl. 3. Qrtl. 4. Qrtl.
SAP AG 2003
Linear replacement values procedure y This procedure shows replacement values in a linear format. This means that the difference between the last known value prior to the missing values and the first known value after the missing values is distributed across the number of missing intervals.
Maximum value replacement values procedure y This procedure replaces missing values with the maximum value from the last known value prior to the missing values and the first known value after the missing values.
Minimum value replacement values procedure y This procedure replaces missing values with the minimum value from the last known value prior to the missing values and the first known value after the missing values.
© SAP AG
IUT235
1-32
Data Sheet Explanation of Symbols in Exercises and Solutions Exercises Solutions Course Objectives Business Scenario
Tips & Tricks Warning or Caution Data in the Exercises ## corresponds to your group number (for example 01- 30). Type of data
Data in the training system
Business partner
TR0101A0##
Contract account
TR0101A0##
Contract
TR0101A0##
Installation
TR0101A0##
Device
TR0101A0##
Point of delivery
EN 123456 10004 EDM_R_0##
RTP interface
EDM
RTP interface (1)
EDM_01
RTP interface (2)
EDM_02
Value limit profile 25 kWh
25
Value limit profile 50 kWh
50
Price profile spot price
75
© SAP AG
IUT235
1-33
Exercises Unit: Introduction to RTP Billing Topic: Familiarize Yourself with the Data Model At the conclusion of these exercises, you will be able to • Describe your business partner and its corresponding data objects. • Describe the business partner profile allocation • Analyze values in a profile. The SuppCo company has already installed interval meters. In future, customers are also to be billed for consumption. In this exercise, you familiarize yourself with the commercial and technical master data of your business partner, and the allocated interval meter.
1-1
Familiarize yourself with the data model of the training system. Go to the SAP Easy Access menu and choose Utilities Industry Æ Customer Service Æ Front Office/Customer Interaction Center Æ Customer Interaction Center. 1-1-1
Identify the business partner TR0101A0## and display its data environment. ___________________________________________________ ___________________________________________________
1-1-2
Which device was installed? Which device category and basic device category is this meter based on? Field name or data category
Values
Device Cat. Basic Device Category ___________________________________________________
© SAP AG
IUT235
1-34
Which particular type does the device created have? ___________________________________________________ How does this device differ from a traditional device used by the company? ___________________________________________________ ___________________________________________________ 1-1-3
Identify the register group. ___________________________________________________ ___________________________________________________
1-1-4
Identify and note the register code of the register. ___________________________________________________ Which significant function does this field perform? ___________________________________________________ ___________________________________________________
1-1-5
Which interval length and unit of measurement are allocated? ___________________________________________________ ___________________________________________________
1-1-6
What is the significance of the Interval Length ID field and which values are admissible for this field? ___________________________________________________ ___________________________________________________
© SAP AG
IUT235
1-35
1-2
You want detailed information on the profile that is allocated to business partner TR0101A0##. Use January YYYY (01.01 to 31.01YYYY = current year) as the selection period. Use the information transactions in profile management. Choose the following in the SAP menu: Utilities Industry ÆEnergy Data Management Æ Profile Management Æ Profile Header Æ Display. 1-2-1
Which profile has been allocated to business partner TR0101A0##? ___________________________________________________
1-2-2
What is usually used to make the allocation between a device and a profile? ___________________________________________________ Which type of allocation does this device have? ___________________________________________________ ___________________________________________________
1-2-3
Determine the central profile data for business partner TR0101A0##: Field name or data category
Values
Profile type Interval length defined Unit of measurement for meter reading Profile value type
© SAP AG
IUT235
1-36
1-2-4
How many profile values are available to you for the month of January? ___________________________________________________ In the context of energy data management, values must be provided to replace missing or implausible profile values. Name three processes, which can be used to create or edit replacement values? ___________________________________________________ ___________________________________________________ ___________________________________________________ ___________________________________________________
1-2-5
What is the total consumption for January? ___________________________________________________ ___________________________________________________
1-2-6
What is the maximum value and when did this occur? ___________________________________________________ ___________________________________________________
© SAP AG
IUT235
1-37
Solutions Unit: Introduction to RTP Billing Topic: Familiarize Yourself with the Data Model
1-1
Go to the SAP Easy Access menu and choose Utilities Industry Æ Customer Service Æ Front Office/Customer Interaction Center Æ Customer Interaction Center. 1-1-1
In the business partner field (Part/tel in the selection area, enter the number of your business partner. Field name or data category
Values
Business partner
TR0101A0##
Choose Enter. Confirm your selection and choose Confirm Partner (Enter). The Customer Environment is now available in the navigation area. 1-1-2
Which device was installed? Determine the device and use the context menu (select device, right mouse click) to choose Display Device. Field name or data category
Values
Device
TR0101A0##
Device Cat.
TD-INT15-00
Basic Device Category
Meter
This is a device information record. The device information record is a data object that contains data on an individual physical object and is maintained by an external organization or is not something that you own. The data record therefore only contains device data for the utilities industry component (billing). It is not therefore managed in the Plant Maintenance (PM/CS) component. This “abbreviated” master record is therefore only required for technical billing purposes. The device is not allocated to a device location (functional location). Installation is performed in relation to a utility installation for technical billing reasons.
© SAP AG
IUT235
1-38
A device info record can refer to the following objects: - Counting device (meter) - Controlling device (ripple control receiver) - Data processing device (converter) - Device with protective or adjustive functions (pressure controller) 1-1-3
1-1-4
Identify the register group. Field name or data category
Values
A register group
TP-IN-00
Identify and note the register code of the register. Choose the Registers tab page. Search for the entry in the Register Co field. Field name or data category
Values
Register code
EDM_TRAINING
The register code is used to identify the measurement task, which is performed for this meter. The meter can therefore be used in connection with the point of delivery for unique identification (in Germany for instance to represent the EDIS code). This value is also checked when the profile values are imported. 1-1-5
Which interval length and unit of measurement are allocated? Field name or data category
Values
Interval length defined
15 minutes
Search for the entry in the UM MR field.
© SAP AG
Field name or data category
Values
Unit of measurement
kWh
IUT235
1-39
1-1-6
What is the significance of the Interval Length ID field and which values are admissible for this field? The Interval Length ID field is used to define the time interval, which can be found between the profile values for a profile. During meter reading order creation, the system does not generate meter reading documents for these registers. The utility installations behave like flat-rate installations for meter reading order creation: Admissible intervals are:
1-2
Field name or data category
Values
5
5 minutes
10
10 minutes
15
15 minutes
30
30 minutes
60
60 minutes
Choose the following in the SAP menu: Utilities Industry ÆEnergy Data Management Æ Profile Management Æ Profile Header Æ Display. Enter the value TR0101A0## in the Business Partner field from the selection area. Choose 01.01 YYYY to 31.01.YYYY as the selection date (SelDate). Confirm your entry by choosing Enter. The data environment for your business partner is now available in the navigation area. 1-2-1
Which profile has been allocated to business partner TR0101A0##? Select the last entry in the navigation area. Switch to the profile header display. The profile number and its description are found in the work area.
1-2-2
What is usually used to make the allocation between a device and a profile? The logical register for your interval meter is usually used to make the allocation. Which type of allocation does this device have? Choose the profile in the navigation area and switch to the profile allocation display in the context menu (right mouse click). The allocation was made using a role in the specific example. You can generally access the profile using this role during RTP billing.
© SAP AG
IUT235
1-40
1-2-3
© SAP AG
Determine the central profile data for business partner TR0101A0##: Field name or data category
Values
Profile type
Historical profile
Interval length defined
15 minutes
Unit of measurement for meter reading
kWh
Profile value type
Quantity
IUT235
1-41
1-2-4
How many profile values are available to you for the month of January? Choose the OLE Interface (EXCEL) tab page in the work area in the bottom half of the screen. A total of 2978 lines are displayed. 2976 values (2978 minus two header lines) are available to you as profile values. This result is produced from product 4 (15 minute values) * 24 (hours) * 31 (days). In the context of energy data management, values must be provided to replace missing or implausible profile values. Name three processes, which can be used to create or edit replacement values? Interpolation: If you want to replace missing profile values in the past with replacement values, values must be interpolated. Note that follow-up processes such as RTP billing or settlement are performed on the basis of these interpolated values. It is therefore important that the replacement values created are as realistic as possible. Sample You have allocated a profile to a register with the Consumption measured role. The profile is provided with values from an automated meter reading system on a daily basis. If values for a specific period cannot be imported from the AMR system (for instance due to a technical fault), replacement values must be created here instead. To do so, you must interpolate values for the profile. Extrapolation: If you want to forecast profile values for the future (for instance to create a schedule), values must be extrapolated. Extrapolated values are either overwritten with the values measured at a subsequent point in time or are entered in a separate forecast profile. Note that follow-up processes such as RTP billing or settlement are not performed on the basis of these extrapolated values. Example: You have allocated a profile to a register with the Consumption measured role. The profile is provided with values from an automated meter reading system on a daily basis. You create a schedule for the following day. To do so, you must extrapolate values for the profile. These extrapolated values are overwritten by the values measured from the AMR System on the following day. Manual Change: You can also change profile values manually on an individual basis or make modifications using the mass change function for profile value processing. Values can also be exported using the OLE interface and imported again once they have been modified.
© SAP AG
IUT235
1-42
1-2-5
What is the total consumption for January? In the navigation area, choose the profile. Branch to the profile values display from the context menu. Choose the Display Totals for Each Day access in the group box in the upper half of the work area. Select the column with your profile values and create the Total. A total of 48.246,58 kWh was measured for this profile in January.
1-2-6
What is the maximum value and when did this occur? Choose the Display Peak for Each Day access in the group box in the upper half of the work area. Select the column with your profile values and display the Maximum. The maximum value is 53.8 kWh. You can use the search function (magnifying glass) to determine that the value occurred on 13.01. Double-click on the profile value 53.8 in the group box. The value is now selected again in the lower group box. The maximum occurred on the13.01.in the period between 13:15:00 and 13:29:59. Alternative: Choose the Display Peak for Each Day access in the group box in the upper half of the work area. Select the column with your profile values and display the profile values in descending order. You recognize that the maximum value (first value in the column) occurred on 13.01. Click on this value. The value is now selected again in the lower group box. The maximum occurred on the13.01.in the period between 13:15:00 and 13:29:59.
© SAP AG
IUT235
1-43
Billing Overview in IS-U/CCS
Billing Overview
SAP AG 2003
© SAP AG
IUT235
2-1
Review of Billing in IS/U-CCS: Unit Objectives
At the conclusion of this unit, you will be able to: z Identify the central billing master data in IS-U/CCS. z Describe the bill creation process from meter
reading order creation to bill printout.. z Highlight the special features of RTP billing.
SAP AG 2003
© SAP AG
IUT235
2-2
IS-U/CCS: Billing Process
Creation of Meter Reading Order
Entry of Meter Reading Results
Billing
Billing Order
Billing Order
Meter Reading Order
Plausible Meter Reading Results
Invoicing
Billing Document
Bill Printout
Print Document
Correction of Meter Reading Results
Implausible Meter Reading Results
SAP AG 2003
The central master data for billing is the installation (contains the rate category) or contract (contains the company code) and the device, in particular the installation structure (contains the rate type for each register). The installation structure is created when you perform a billing-related installation (devices installation).
In invoicing, the most important master data object is the contract account.
During meter reading order creation for an interval meter, the system does not generate a meter reading order and it is not therefore necessary to perform meter reading data processing. The billing order can be billed immediately.
© SAP AG
IUT235
2-3
Billing Order Status
Billing order
Actions Actions z
Creation of meter reading order
z
Billing
z
Billing Reversal
Effect Effect on on the the Billing Billing Order Order z
Status 2 = can be billed
z
Billing order is deleted
z
Billing order is restored
SAP AG 2003
The activities described in the upper left have certain effects on the billing order. (This example is only valid for interval meters. The billing order is actually an index for billing. It is used for tracking the status and improving performance. During RTP billing, the billing order is defined as being "billable" immediately when the meter reading data is prepared. This occurs regardless of whether profile values have already been imported.
© SAP AG
IUT235
2-4
Billing Tasks
z Standard process that processes billing orders, creates billing documents for each contract and transfers information to invoicing z Determination of billing periods z Determination of rate data z Quantity conversion z Proration z Execution of variant programs z Creation of billing documents with billing line items z The billing document forms the base for the communication structure (UIS - Sales Statistics)
SAP AG 1999
© SAP AG
IUT235
2-5
Invoicing Tasks
z Standard IS-U process that establishes the link to contract accounts receivable and payable, and provides the basis for bill creation z Groups billing documents of contracts from a contract account into a joint bill (invoicing unit) z Posts documents in subledger accounting z Processes budget billing plans
SAP AG 1999
© SAP AG
IUT235
2-6
IS-U/CCS: Billing Rate Data
Customer and Installation-Related Data
Prices and rate facts
Contract
Installation
Inst. Structure/ Rate Cat. Facts/ Installation Facts
Data Entry and analysis
Ra
R
te
ca t.
e at
pe ty
Rate 1 Rate Determin.
Proration
Rate n
Execute Variant Programs in Acc. with Schema
Procedural Data Schema I Rate
VarProg.
Value
Rate 1 - Step 1 - Step 2 .
VarProg. A VarProg. B .
x1 x2 .
Rate 2 - Step 1 - Step 2 - Step 3 . . .
VarProg. A VarProg. A VarProg. D . . .
x3 x4 x5 . . .
Rate n - Step 1
VarProg. A
xxx
Validation of Billing Results
E X E C U T I O N
Generation of Billing Line Items
SAP AG 2003
© SAP AG
IUT235
2-7
Data Model for Billing
Business partner Contract account Rate cat.
Demand Prices
Contract
Operands Utility Installation
Rate determination
Rate var.
Operand Values
Installation Structure
Rate type
Billing schema Rate 1
Var Prog
Operand Values
Step 1
eg Quantity X Price
1000 kWh, O.25 UNI
Step 2
eg Comparison of 2 Demands
400 kWh, 300 kW
Rate n Step 1
SAP AG 2003
A rate category is allocated to each installation. It contains data which controls the processing of billing data for all rates.
The rate type determines the rate allocation of registers and is therefore generally entered in the installation structure for the register.
The rate is the most important billing component. It contains the billing logic in the form of rate steps (variant programs).
Dynamic rate determination finds the rate using the rate category and the rate type. This control is defined as the last step in this representation of the billing master data. A rate can be allocated to different rate determinations. In this way, individual rates can be used for different billing structures.
All rates that can be billed together in the same contract/installation (for example, on-peak rate for household customers, off-peak rate for household customers) must be brought together in one billing schema.
The schema contains the billing logic and defines the processing order of the rates and rate steps (variant programs) to be processed. A schema contains one or more rates.
© SAP AG
IUT235
2-8
Rate
Rate
Operand
Rate Steps
Operand Category
Variant Programs
SAP AG 1999
The rate consists of a key, header data, and one or more rate steps. A variant program is processed for each rate step.
These are some points that the rate determines: y how the measured consumption is extrapolated or broken down for meter reading data processing and for proration y which billing values are measured by a register y which reference values are billed y in which calculation formulas the values are used y which prices are used y to which G/L accounts the calculation results (billing line items) are posted y how the billing line items are dealt with statistically y to which division and billing class the rate is allocated.
© SAP AG
IUT235
2-9
Variant Programs: 1 Variant Pool QUANTITY X FACTOR Calculates x% of a quantity
QUANTITY
...
Variant Pool
... NUMBER OF DEMAND PEAKS Calculates N peak averages
ACTIVE_KWH x 0,5
ACT_50%
DEMAND
SETTLEMENT LINES DEMAND XPRICE Valuates demand with a price
REACT_KWH
-
BILL_REACT
x $0,06
ACT_50%
BILL_REACT BILLING LINE ITEMS
... QUANTITY QUANTITYDifference of two quantities
QUANTITY
... ... SETTLEMENT LINES QUANTITY X PRICE Valuates energy with a price
Contract text: The reactive energy that exceeds 50% of the active energy is valuated using a separate price.
SAP AG 2003
Variant programs are small, independent ABAP/4 programs (function modules).
Variants perform elementary calculation steps. Many variant programs calculate values relevant to billing and generate billing line items. Other variant programs convert values and in turn make the results available to subsequent variants.
Variant programs can be used in any combination. This allows you to model billing rules.
In most cases, variant programs have input and output operands which represent the ingoing and outcoming parameters (variables) of the variant program. These operands belong to a particular operand category.
© SAP AG
IUT235
2-10
Variant Programs 2
ABAB/4 Function Modules function isu_quanti01. Include ievarbasic. Data: ...... ..... Input Operands
If wprei-preisart = ‘2’. loop at ...... ..... endif.
Output Operands
Billing Line Items
endfunction.
SAP AG 1999
In most cases, variant programs have input and output operands, which represent the ingoing and outcoming parameters (variables) of the variant program. These operands belong to a particular operand category.
SAP defines which variant program needs which input and output operands (number, operand category).
In the system, the variant programs process specified tables. During data collection for billing, these tables are filled with all required data.
© SAP AG
IUT235
2-11
Rate Determination - Operands
Operand categories
Operands
Operand values
• Predefined
• Determined individually
• Provide operands with values
• Serve as the parameters for variant programs
• Define actual values
• Control processing via variant programs
SAP AG 2003
In the following objects, you can allocate values to the operands: y rate facts y Rate category facts y Installation facts y Dynamic determination at billing runtime
© SAP AG
IUT235
2-12
Prices for Billing
Central Price Management
Price Key
Prices
SAP AG 2003
The price key is the name of a price; the price key is also called "price". Control data such as division, billing class, time basis, and rounding are also stored in the header data of prices.
The actual values are stored in the prices. Historical price amounts are also managed in the prices. If the price changes, the new time slice is entered here. In this case, the header data does not change.
The price key also contains a currency key. This means that if you use different currencies for billing, you must maintain all prices in the different currencies.
You establish the currency that is valid for a particular customer in the Trans. currency field in the contract account.
© SAP AG
IUT235
2-13
Facts
Hierarchy
Installation Facts
Price A 0.55
Have precedence over
Rate Category Facts
Price B 0.60
Have precedence over
Rate Facts and Rate Fact Group
Price C 0.75
SAP AG 1999
Fact Groups y Concrete values, keys that the operands have been allocated and that are valid for a particular period, are referred to as facts. Depending on the level at which the key is allocated, these are either installation, rate, or rate category facts. Prices are assigned as facts to the operands.
Operand values can be stored as rate facts, rate category facts or as installation facts. This results is a pricing hierarchy.
© SAP AG
IUT235
2-14
Billing Schema
z Is valid for a certain division z Is valid for a certain billing class z Contains one or more rates z Determines the sequence of the rate steps for billing z Creates the connection to the sales statistics
SAP AG 2003
Rates and their variant programs and operands are included in a billing schema. The following are specified in a billing schema: the rates used for billing, the schema steps used, and the sequence of the schema steps.
More than one rate can be contained in a billing schema than is necessary for the billing of a certain installation. Therefore, it is possible that a billing schema can contain two rates (on-peak household rate and off-peak household rate). Only one single-rate meter is installed in the installation. In this case only the on-peak rate is billed. The off-peak rate is simply ignored in the schema.
The quantity and amount statistics group creates the connection to the sales statistics This determines whether the Utilities Information System (UIS=LIS) or the Business Information Warehouse (mySAP BW) is used to perform analyses.
© SAP AG
IUT235
2-15
Rate Category
Division Billing Schema
Dynamic Period Control
Billing Class
Rate Category
Outsorting Group
Billing in Advance
Memos
Backbilling Period-End Billing
SAP AG 2003
The rate category contains data which controls the processing of billing data for all rates, This includes: y Billing Schema y Control of period-end billing and floating backbilling y Outsorting checks
Any other billing-relevant data is also saved in the rate category. This includes any agreed quantities, demand, prices, or flat rates. In the case of flat rate services (such as cable services and street lights), no quantities are measured. You must therefore define replacement values that the system can use for evaluation (for example number of cable connections or number of street lights with a specific connection value).
© SAP AG
IUT235
2-16
Rate Type z Is valid for a particular division (obligatory) and billing class (optional) z Use of the rate type can be permitted for:
Register must be specified for registers relevant to billing
Device For example: rental price for devices which have no registers relevant to billing
Facts for example: flat rates or installation flat rates
Interval Meters for billing of real-time pricing rates
Period-end billing for example: for determining a special fact group in the period-end billing
Waste billing for example: for determining a special rate for waste management
SAP AG 2003
You can maintain rate types in the following objects:
Register In the case of registers relevant to billing, you must specify a rate type in the installation structure. In doing so, you establish that the consumption or the demand of a register is billed using the corresponding rate.
Device You can specify a rate type for a device if, for example, you wish to levy a rental price at the device level. This is particularly relevant if the device does not contain any registers relevant to billing.
Rate category You can specify rate types in the rate category to perform billing of values not related to registers. For example: by means of the rate type, a rate is determined that is used to bill a flat rate.
Installation If, for example, you wish to levy a flat rate for a certain installation only, you enter the rate type in the installation facts, but not in the rate category.
© SAP AG
IUT235
2-17
Rate Determination List of Rate Determinations Rate Find List Edit Goto System Help
Multiple Multiple rate rate determination determination is is possible possible for for example, example, for for different different RTP RTP billing billing principles principles
Rate Determination for Electricity Division Rate Type
Rate Category
From
To
Rate
Installation
Device Installation
Rate Category
Rate Type
Rate Determination
Rate SAP AG 2003
Rate determination Combining rate categories and rate types is basically responsible for determining the billing rule (rate).
The rate category is entered in the utility installation.
The Rate Type is used to classify registers of the installation structure for billing e.g weak load, on-peak or demand register.
The Rate Type can also be used in: y Devices Devices are frequency installed, which do not contain registers relevant to billing. Rate types can in these cases be used to levy a rental price at the device level. y Facts This admissibility can be used, for example, to bill non-register-related values. Facts - Perform billing of values not related to registers e.g by means of the rate type, a rate is determined that is used to bill a flat rate e.g unmetered lighting. This rate type which is admissible as a result of facts can be assigned at the Installation or Rate Category level.
The rate types/rate categories may not have to be changed in the master data if rates are reformed because the rate can be determined historically. It suffices to find new rates for a certain key date.
The system can also determine more than one rate per rate type and rate category. You can use this option, for example, to model best-rate billing in the system (low consumption rate, basic price rate 1, basic price rate 2).
© SAP AG
IUT235
2-18
Initial Data Creation of a Rate
Rate Rate type type
Prices Prices (create (create from from rate) rate) Rates Rates
Determine
Variant Variant Programs Programs Determine
Billing Billing schema schema Select Rate Rate category category
Rate Rate determination determination
Link to Fact Group
Operands Operands (create (create from from rate) rate)
Rate Rate Sequence Sequence
Billing Billing Schema Schema Allocate
Rates Rates
SAP AG 2003
Individual rate components must be created and maintained in a predefined sequence.
The sequence is determined by the respective links to the individual components.
The components are maintained in the following sequence: - Rate types - Operands - Prices - Rates - Schemas - Rate categories - Rate determination
You do not normally create the operands and prices beforehand, instead you create them from the rate. To do so, you enter the new name (of the operand, for example) in the field and by double-clicking on it, the system automatically goes to the transaction for creating operands.
© SAP AG
IUT235
2-19
Application Example RTP Interface z Billing of a commercial and industrial customer with load profile measurement. z Determine billing-relevant data
Consumption during the on-peak rate period
Consumption during the off-peak period
Max. demand
EDM repository
IS-U/CCS Billing RTP interface
On-peak consumption Off-peak consumption Max. demand
SAP AG 2003
© SAP AG
IUT235
2-20
Elements in an RTP Interface z
RTP formula
z
RTP Components
z
Result parameter
RTP interface Formula
RTP Components
EDM repository
ƒ
"On-Off" Component
"Without rate period" Component
Result Parameter On-peak consumption Off-peak consumption
IS-U/CCS Billing On-peak consumption Off-peak consumption Max. demand
Max. demand
SAP AG 2003
© SAP AG
IUT235
2-21
On-Peak, Off-Peak and Maximum Demand Maximum demand determined from component 1 p
Off-peak consumption determined from component 2
On-peak consumption determined from component 2
Off-peak consumption determined from component 2
On-peak consumption determined from component 2
Off-peak consumption determined from component 2
t SAP AG 2003
The Real-time pricing interface (RTP interface) transfers the values from the Energy Data Management component (IS-U-EDM) the Billing (IS-U-BI) component. The RTP interface enables you to use the profiles maintained in the IS-U-EDM in billing. To do this, you allocate the RTP interface to the rate used for billing an interval meter.
In the RTP interface you can execute billing-relevant processing steps carried out based on profiles. For example, you can process billing agreements for periods as small as 15 minutes. The results from such processing steps are then transferred to the rate steps in the rate for a specific date. Billing lines can then be created from the rate steps.
Example: An RTP interface called ONOFFPEAK is used to determine the following billing values from a measured consumption profile (15-minute interval):On-peak rate consumption. The total consumption used in the period from 06:00:00 to 21:59:59. Off peak consumption The total consumption in a period from 22:00:00 to 05:59:59 hours. Maximum demand value
The following RTP components are defined in RTP interface EDM: y RTP component 1: Determines peak demand for the entire time period and is not dependent on any day, TOU or season group y RTP component 2: Determines the on- and off-peak consumption based on a time-of-use group.
© SAP AG
IUT235
2-22
RTP Component - Profile Slicing
Measured Entry profile kW/kWh
off
on
off
on
off
Virtual profile
Result Function
Σ
Output Profile Off-Peak
off
off
Off-Peak consumption kWh = 275
off
Virtual profile
Output Profile On-Peak
on
Result Parameter
Result Function
Σ
on
Result Parameter
On-Peak kWh = 500
SAP AG 2003
The RTP components slice the measured profile as shown above by creating a virtual on- and off-peak profile (output parameters). It is important to note that these profiles are not stored in the database but are only used as input to the result function.
The result function then sums the results of the on- and off- peak virtual profiles to determine on- and off-peak consumption.
The result parameters are then passed via the rate facts into input operands of the rate steps (variant program)..
© SAP AG
IUT235
2-23
Result Parameter Output Parameter 1
Result Parameter 1
Result Function
Σ
Output Parameter 2
On-Peak consumption kWh = 500 Result Parameter 2
Result Function
Σ
Output Parameter 3
Off-Peak consumption kWh = 375
ISIS-U-BI rate facts
Result Parameter 3
Result Function Maximum demand
Maximum kW = 200
SAP AG 2003
Result Parameters are defined in the RTP interface. Individual values are recorded in the results parameters. These output parameters are allocated to the result parameters (formula-dependent). Results parameters create the relationship to the RTP rate. This facilitates the billable quantities being passed to the IS-U-BI component.
In the above example, the following result parameters are being defined: y Off-peak consumption (1) y On-peak consumption (2) y Maximum demand (3)
© SAP AG
IUT235
2-24
Value Transfer For example: Sum values 60 40 20
Profile values
Value
z
Value transfer to operand (rate facts)
Billing Rate Cat.
Rate Type
10000kWh Billing Line Items
Rate Determin. Billing Schema Rate step Rate step Rate step SAP AG 2003
The results parameters used in the RTP interface and the results functions defined provide discrete values for IS-U billing. The value transfer takes place in the rate facts, where they links the results number with the input operands for the variant program.
© SAP AG
IUT235
2-25
Rate Header Data with RTP Interface Rate: EDM
Permissibility
Register-Based Data
X Interval meter
RTP Interface:
EDM_01
Allocate the RTP Interface to the Rate
Rate Facts/Operands Operands:
Off-peak rate consumption
Operand Category:
QUANT
Result Parameter:
2 – Off Peak Consumption
Must match RTP Operand in the RTPInterface
X RTP Operand
SAP AG 2003
Before the RTP interface can be used, it must be allocated to a rate. This allocation is only possible for rates for which you have selected the Permitted for Interval Meters field. Individual rate step operands can be allocated to the results parameters for the RTP interface in the rate facts. This means that the appropriate operands are provided with result parameter values from the RT iInterface during billing.
It is only possible to allocate result parameters to operands in the rate facts if the RTP operands have been defined. Within the RTP Interface, the operand category must align with those used in the RTP rate.
© SAP AG
IUT235
2-26
Rate Steps Rate: EDM
Rate Steps Variant
InputOp01
InputOp02
OutputOp01
Statistical Rate
001
QUANTI01
ONPEAKUSG
ONPEAKPRICE
RESULTAMT
EDM
002
QUANTI01
OFFPEAKUSG
OFFPEAKPRICE RESULTAMT
EDM
003
DEMAND01 MAXPEAK
DEMANDPRICE
EDM
RESULTAMT
SAP AG 2003
Traditional variant programs are used to generate invoice lines (e.g. QUANTI01).
You can use additional variant programs to determine discrete values that are determined from an RTP interface.
© SAP AG
IUT235
2-27
Exercises Unit: Billing Overview Topic: Familiarize Yourself with the Data Model At the conclusion of these exercises, you will be able to •
Describe the billing and invoicing process.
•
Describe the elements of an RTP rate
•
Describe the elements of an RTP interface
In this exercise, you familiarize yourself with the billing data of your business partner, the RTP rate, and the RTP interface.
1-1
Familiarize yourself with the billing data for your business partner TR0101A0##. Go to the SAP Easy Access menu and choose Utilities Industry Æ Customer Service Æ Front Office/Customer Interaction Center Æ Customer Interaction Center. 1-1-1
Identify the business partner TR0101A0## and display its data environment. ___________________________________________________ ___________________________________________________
1-1-2
Obtain information on the current billing situation. Use the billing view for installation TR0101A0## to do so. Is a billing order already available for this installation? ___________________________________________________ Prepare the installation for periodic billing January YYYY (YYYY = current year). Generate a billing order. How do you proceed? Name the path for meter reading order creation. ___________________________________________________ ___________________________________________________ What is the status of the billing order? ___________________________________________________ ___________________________________________________
© SAP AG
IUT235
2-28
1-2
Obtain information on the current rate situation. 1-2-1
How has rate determination been defined for the installation? Determine the billing master data involved ___________________________________________________ ___________________________________________________ Field name or data category
Values
Rate type Rate category Rate For which level is the rate type admissible? Why has this setting been selected? ___________________________________________________ ___________________________________________________ With which additional field is the rate type always linked? Justify your response. ___________________________________________________ ___________________________________________________ 1-2-2
Now interpret the EDM rate. Name three central characteristics in which the EDM rate (RTP rate) differs from a normal IS-U rate.
1-2-3
1.
_________________
2.
_________________
3.
_________________
How many rate steps is the EDM rate made up of? ___________________________________________________ ___________________________________________________ ___________________________________________________
© SAP AG
IUT235
2-29
1-3
General questions on the RTP interface: 1-3-1
1-3-2
Which IS-U components are linked by the RTP interface? 1.
_________________
2.
_________________
Name the three basic elements of which an RTP interface is composed. _________________________________________________ _________________________________________________ _________________________________________________
1-3-3
The RTP component defines the structure of parameter allocations in the RTP interface. Give examples. _________________________________________________ _________________________________________________ _________________________________________________
1-3-4
What types of time groups can be allocated to an RTP interface? _________________________________________________ _________________________________________________ _________________________________________________
1-3-5
The allocation of a formula to an RTP interface defines the calculation method used in the interface. What else is (indirectly) allocated at this point? _________________________________________________ _________________________________________________ _________________________________________________
© SAP AG
IUT235
2-30
1-4
Display the header data of the RTP interface. 1-4-1
Determine the data for the RTP interface EDM. _________________________________________________ _________________________________________________
1-4-2
Which formula is allocated to the RTP interface? _________________________________________________ _________________________________________________
1-4-3
How many input and output parameters are defined in the formula COPY01? _________________________________________________ _________________________________________________
1-5
Display the result parameter of the RTP interface. 1-5-1
How many results parameters are defined in RTP interface EDM? _________________________________________________ _________________________________________________
1-5-2
Note the results parameters for the individual results functions in the RTP interface EDM. The SUM results function is used to determine the following: _________________________________________________ _________________________________________________ _________________________________________________ The PEAK results function is used to determine the following: _________________________________________________ _________________________________________________ _________________________________________________
© SAP AG
IUT235
2-31
1-6
You branch to billing analysis. Choose the following from the SAP menu: Utilities Industry Æ Billing Æ Billing Execution Æ Billing Analysis. 1-6-1
Perform a billing simulation. Use the existing billing order you created previously. _________________________________________________ _________________________________________________
1-6-2
Ensure that the simulation was successful. _________________________________________________ _________________________________________________
1-6-3
Display the simulated billing document and note the billing document number. Billing document number: _______________________
1-6-4
Note the net amount and the billing quantity (located on the Document overview tab page) for the individual billing lines. Billing line
Net amount
Billing quantity
On-peak rate consumption Off-peak rate consumption Maximum demand Run an RTP analysis for this billing document. _____________________________________________________ _____________________________________________________ 1-6-5
How many input parameters were used in the simulation? _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
2-32
1-6-6
What is the total of the profile values used for input parameter 1? __________________ Compare this value with the total consumption for the load shape measured for the month of January (exercise in the previous unit).
1-6-7
What is the demand value billed? __________________ How has this demand value been determined? _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
2-33
Solutions Unit: Billing Overview Topic: Familiarize Yourself with the Data Model
1-1 1-1-1
In the business partner field (Part/tel), enter the number of your business partner. Field name or data category
Values
Business partner
TR0101A0##
Choose Enter in the selection area. Choose Confirm Partner again. The data environment for your business partner is now available in the navigation area. 1-1-2
Obtain information on the current billing situation. Use the billing view for installation TR0101A0## to do so. Is a billing order already available for this installation? No Choose the installation in the navigation area and switch to display using the context menu. Choose the billing view in the installation. Choose the Billing Order tab page. No entry is available. Open a second session and choose the following from the SAP menu: Utilities Industry Æ Device Management Æ Meter Reading Æ Order Creation Æ Individual Order. Enter TR0101A0## in the Installation field, and choose the entry for periodic billing as the meter reading reason. Now perform meter reading order creation. Choose the meter reading period for 31.01.2003 in the next window. Choose Create Order in the Display Date Record window. Ensue that meter reading order creation is successful. Return to the first session. Choose Refresh. A billing order is now generated, which can be billed immediately.
© SAP AG
IUT235
2-34
1-2
Obtain information on the current rate situation. 1-2-1
Choose the Rate Types tab page in the billing view for the installation. Field name or data category
Values
Rate type
1008
Rate category
EDM
Rate
EDM
For which level is the rate type admissible? Why has this setting been selected? Choose the possible entries in the Rate Type field. The indicator for the value 1008 is selected in the IMR column. Admissibility for interval meters means that these rate types can be used at register level for interval meters. Rates for which this field is selected can now only be allocated to those rate types that are also admissible for interval meters during rate determination. With which additional field is the rate type always linked? Justify your response. The rates fact group must always be specified for the rate type directly. Rate fact groups enable you to use various prices for each operand within a rate. 1-2-2
Now interpret the EDM rate. Name three central characteristics in which the EDM rate (RTP rate) differs from a normal IS-U rate. 1. Permitted for interval meters. 2. An RTP interface is allocated to the rate. 3. RTP operands are allocated in the rate facts. (indicated by RTP interface symbol)
1-2-3
How many rate steps is the EDM rate made up of? The rate is made up of 3 rate steps. Valuation of the on-peak rate quantity with a price (QUANTI01) Valuation of the off-peak rate quantity with a price (QUANTI01) Valuation of the maximum demand with a price (DEMAND01)
© SAP AG
IUT235
2-35
1-3
General questions on the RTP interface: 1-3-1
Which IS-U components are linked by the RTP interface? 1. Energy Data Management (IS-U-EDM) 2. Billing (IS-U-BI)
1-3-2
Name the three basic elements of which an RTP interface is composed. Header data The header data contains the formula for calculating allocated profiles, the interval length, and the division. Result parameter The result parameters originate in the result function. Result parameters are assigned to operand categories and references to output parameters. The result parameters provide the operands with data in the RTP rate in IS-U billing. RTP components An RTP interface can have several components. The components are sorted according to priority. This makes it possible to determine which component is valid when several components have the same activation period. The component with the highest priority is valid. The periods (represented by codes or consecutive numbers for the codes) that have been defined in the components are listed in those respective components. The assigned profiles are the input parameters. The output parameters are obtained from the formula calculation.
1-3-3
The RTP component defines the structure of parameter allocations in the RTP interface. Give examples. In the RTP interface, you want to allocate separate parameters for summer and winter seasons. To do this, define an RTP component with a season group that describes a year separated into summer and winter. In the RTP interface, you want to allocate separate parameters for the time periods covered by on and off-peak rates. To do this, define an RTP component with a time-of-use group that describes a day separated into on and off-peak periods. In the RTP interface, you want to allocate separate parameters for summer and winter seasons, as well as for on and off peak periods. To do this, define an RTP component with a season group that describes a year separated into summer and winter, as well as a time-of-use group that divides a day into on and off-peak periods.
1-3-4
What types of time groups can be allocated to an RTP interface? Season group Day group TOU group
© SAP AG
IUT235
2-36
1-3-5
The allocation of a formula to an RTP interface defines the calculation method used in the interface. What else is (indirectly) allocated at this point? When you choose a formula, you define input parameters to be supplied to the interface as well as the output parameters available.
1-4
Display the header data of the RTP interface. 1-4-1
Determine the data for the RTP interface EDM. Display the header data for the EDM rate. Branch to the RTP interface display (double-click on the EDM entry in the RTP interface field.
1-4-2
Which formula is allocated to the RTP interface? In the Header Data tab page, search for the Formula field.
1-4-3
Field name or data category
Values
Formula
COPY01
How many input and output parameters are defined in the formula COPY01? 1 Input parameter: Consumption profile with profile value category QTY (corresponds to the load shape measured). 2 Output parameter: Copy of the input profile as a consumption profile with profile value category QTY and Copy of the input profile as a demand profile with profile value category DEMAND.
1-5
Display the result parameter of the RTP interface. 1-5-1
How many results parameters are defined in RTP interface EDM? Choose Result parameters. Three results parameters, which represent on-peak, offpeak consumption and maximum consumption are found here.
© SAP AG
IUT235
2-37
1-5-2
Note the results parameters for the individual results functions in the RTP interface EDM. The SUM results function is used to determine the following: The SUM results function can be used to calculate the total profile values for a specific period. The PEAK results function is used to determine the following: The PEAK results function can be used to calculate the maximum profile values for a profile during a specific period.
1-6
You branch to billing analysis. Choose the following from the SAP menu: Utilities Industry Æ Billing Æ Billing Analysis. 1-6-1
Perform a billing simulation. Use the existing billing order you created previously. Choose the billing order you created as the selection criterion for your billing simulation. Copy this into the billing analysis.
1-6-2
Ensure that the simulation was successful. The status display (green light) is used to identify that a billing simulation was successful. You can choose to continue processing or to analyze the billing document first.
1-6-3
Display the simulated billing document and note the billing document number. Billing document number: The billing document number is found in the header data for your document.
1-6-4
Note the net amount and the billing quantity (located on the Document overview tab page) for the individual billing lines. Billing line
Net amount
Billing quantity
On-peak rate consumption
1.469,02
24.483,72
Off-peak rate consumption
712,89
23.762,86
Maximum demand
2.193,27
215,20
Run an RTP analysis for this billing document. Choose the RTP analys. tab page.
© SAP AG
IUT235
2-38
1-6-5
How many input parameters were used in the simulation? One input parameter was used (load shape measured).
1-6-6
What is the total of the profile values used for input parameter 1? Select the first input parameter in the Input Parameter Formula group frame. (The profile values are displayed below in the Profile values group frame). Select the Value column in the Profile values group frame. To see the totals, choose Total and scroll to the end of the table. Field name or data category
Values
Total of profile values for input parameter 1
48.246,58
Compare this value with the total consumption for the load shape measured for the month of January (exercise in the previous unit). This value is identical. 1-6-7
What is the demand value billed? Field name or data category
Values
Demand value
215,2
How has this demand value been determined? The maximum demand from 13.01 YYYY was 53.8kWh. This value was identified during a 15 minute interval. The product 53,8 * 4 produces a value of exactly 215,2.
© SAP AG
IUT235
2-39
Elements in an RTP Interface
Overview of the RTP Interface and Examples Header data Result Parameter RTP Components
SAP AG 2003
© SAP AG
IUT235
3-1
Elements of an RTP Interface: Unit Objectives At the conclusion of this unit, you will be able to: z Explain how the RTP Interface can be used to
bill interval data
z Articulate the use of the header data z Define and explain the function of a formula
in the RTP interface
z Describe the function of a result parameter
and function in the RTP Interface
z Discuss the function of an operand in
the RTP Interface
z Define and explain the function of an RTP
component, its structure, activation types and priority in the RTP Interface
z Describe the function of input and
output parameters in the RTP interface
SAP AG 2003
© SAP AG
IUT235
3-2
Overview of the RTP Interface and Examples
Overview of the RTP Interface and Examples Header Data Result Parameter RTP Components
SAP AG 2003
© SAP AG
IUT235
3-3
RTP Processing 3-level processing 1. Calculation of profile values using definable formulas.
2. Breakdown rate times using "RTP Components“
3. Calculate discrete results using "results functions" for each results parameter.
Profile Results parameter Formula
f(x1,x2, …)
RTP Component
On- and off-peak division
Result Function
Σ on
Discrete values Result parameter
483 kWh
Maximum (Off) 17kW
SAP AG 2003
© SAP AG
IUT235
3-4
RTP Interface Season day type TOU period component control:DD.MM.YYYY HH.MM - DD.MM.YYYY HH.MM active / inactive
Profile
Standard R/3
In
Formula Defined
Out
Standard R/3
Pr1 = x1 Pr2 = x3
x1 x2 xn
y1 = f(x1,x2,...xn
y1 y2 y3
y1 -> e2 y3 -> e1
Result
Facts
e1 e2 en
Dem = e1 Con = e2
Profile
< value > EDM Profile Management
IS-U Billing RTP Interface
Legend x: y: e: con:
input parameter output parameter result parameter consumption
pr: profile f: formula dem: demand
SAP AG 2003
The diagram gives an overview of the components of the RTP interface. The following slides describe the individual components in greater detail.
© SAP AG
IUT235
3-5
Overview of the RTP Interface
Header Data
z Formula z Interval length
defined z Division
Result Parameter z Result number z Result parameter
desc z Result function z Operand cat.
RTP Components z Components z Activation z Input parameter z Output parameter z Parameter template
z Unit of
measurement z Proration
RTP interface SAP AG 2003
The settings for the RTP interface are made in three central areas: y Header data y Result parameter y RTP components
© SAP AG
IUT235
3-6
RTP Interface Elements Season day type TOU period component control:DD.MM.YYYY HH.MM - DD.MM.YYYY HH.MM active / inactive
Profile
Standard R/3
In
Pr1 = x1 Pr2 = x3
x1 x2 xm
Formula Defined
Out
Standard R/3
y1 y2 yn
y1 -> e2 y3 -> e1
yn = f(x1,x2,...xm)
Result
Facts
e1 e2 en
Dem = e1 Con = e2
Profile
< value >
EDM Profile Management
RTP Interface
Elements of the RTP Component
Element of the RTP Header
IS-U Billing
Result Parameter
SAP AG 2003
At a more detailed level, the RTP interface is made up of several elements: y RTP components - RTP components define the structure of parameter allocations in the RTP interface. - This structure links input, output and result parameters. - Different RTP components are required because different periods (such as summer and winter) are usually required for parameter allocations. - You can allocate various time groups, such as season groups, day groups and time-of-use groups to an RTP component. y Formula defined - The formula reproduces the calculation algorithm required for RTP billing. - Input and output parameters are defined for a formula y Result parameters - The formula works with the individual values in the profile. The result function evaluates the results of formula calculation and summarizes the information to form discrete values, which are passed on to billing via the facts.
© SAP AG
IUT235
3-7
Functions in the RTP Interface (I)
component control:DD.MM.YYYY HH.MM - DD.MM.YYYY HH.MM active / inactive
Standard R/3
In
Formula Defined
Out
Standard R/3
y1
y1 -> e1 y3 -> e2
Result
Season day type
x1 = Pr1 x3 = Pr1
x1
TOU period
e1 e2
x1 = Pr2 x3 = Pr2
x2
yn = f( x1, x2, xm )
y2
y1 -> e3 y3 -> e4
e3 e4
x2 = Pf2
x3
y3
y2 -> e5
e5
< value > Profile
Profile
SAP AG 1999
The example illustrates the use of RTP components.
You can use RTP components to allocate different input parameters to one formula.
© SAP AG
IUT235
3-8
Functions in the RTP Interface (II)
component control:DD.MM.YYYY HH.MM - DD.MM.YYYY HH.MM active / inactive
Standard R/3
In
Formula Defined
Out
Standard R/3
y1
y1 -> e1 y3 -> e2
Result
Season day type
x1 = Pr1 x3 = Pr1
x1
TOU period
e1 e2
x1 = Pr2 x3 = Pr2
x2
yn = f( x1, x2, xm )
y2
y1 -> e3 y3 -> e4
e3 e4
x2 = Pf2
x3
y3
y2 -> e5
e5
< value > Profile
Profile
SAP AG 1999
Other profiles are allocated to the same formula in a different component.
© SAP AG
IUT235
3-9
RTP Interface Symbol Definition RTP Component
RTP Component Code
Parameter Allocated
Parameter Not Allocated
Parameter Template
Input Parameter
Output Allocated SAP AG 1999
The slide lists the icons used in the RTP interface.
© SAP AG
IUT235
3-10
Header Data
Overview of the RTP Interface and Examples Header Data Result Parameter RTP Components
SAP AG 2003
© SAP AG
IUT235
3-11
RTP Header Data Defined
Header
Result Parameter
RTP Components
RTP Interface
Header
z Formula Defined z Interval Length
Defined z Division Defined SAP AG 1999
In the header data, three elements are defined: y Formula: used to perform profile calculations y Interval length: interval between two values in a profile (for example, 15 minutes, 30 minutes, 60 minutes). y Division: company-internal key for the division category. - Predefined by the Utilities Industry (IS-U) component.
© SAP AG
IUT235
3-12
Formula Defined Header Data
In
Measured profile
Formula Defined
x1
x2
Out
y1
yn = f( x1, x2, xm )
z
Interval Length Defined
z
Division Defined
Virtual profile
Virtual profile
x3
y3
Limit 2
Formula Defined
y2
Limit 1
SAP AG 2003
z
Virtual profile
function module
Formula: y Basis of the profile calculation wherein the RTP calculations take place. y Allocated to an RTP interface y Contains a fixed number of input and output parameters to be supplied. (Input and output parameters always refer to those of the formulas allocated to the RTP interface.)
Currently, the following formulas are predefined by SAP: y ACCU_TO_BALANCE - Convert cumulative values to balanced values. y COPY01 - Copy one profile into two output profiles. y INTEGRAL01 - Integral creation with resetting function. y LIMIT01 - Value determination above and below demand limit. y MULTI01 - Multiplication of demand profile by a factor. y SUM01 - Addition of profiles (quantities).
© SAP AG
IUT235
3-13
Formula LIMIT01 and the RTP Interface
O04: Above baseline 1: Demand
I01 Measured Load Profile: Quantity
O03 Above baseline 2: Quantity I03 Baseline 2: Quantity O02 Above baseline 1: Quantity I02 Baseline 1: Quantity
O01 Below baseline 1: Quantity
SAP AG 2003
A formula contains a fixed number of input and output parameters. This occurs when a formula is created in the system.
Formula LIMIT01 has 3 Input Parameters and 4 Output Parameters: 3 Input Parameters
4 Output Parameters
I01: Measured Load Profile: Quantity
O01: Below baseline 1: Quantity
I02: Baseline 1: Quantity
O02: Above baseline 1: Quantity
I03: Baseline 2: Quantity
O03: Above baseline 2: Quantity O04: Above baseline 1: Demand
The formula LIMIT01 allocated to an RTP-Interface will look as follows on the next slide.
© SAP AG
IUT235
3-14
Formula LIMIT01 Allocated to an RTP Interface RTP interface Formula LIMIT01 RTP Component 1
RTP Component 2
Input 1
Input 1
Input 2
Input 2
Input 3
Input 3 Output 1
Output 1
Output 2
Output 2
Output 3
Output 3
Output 4
Output 4
SAP AG 2003
When a formula is allocated to the RTP interface, those Input and Output Parameters from the formula are available to be allocated. However, although all parameters are defined, not all Input and Output Parameters must be allocated within the RTP interface.
The number of input and output parameters is dependent on the formula chosen. This means that different parameters can be supplied for each RTP component. However, the maximum number remains unchanged.
Note that in the above example, Input Parameters 1 and 3 are allocated, whereas Input Parameter 2 is not. Output Parameters 1, 2 and 4 are allocated.
© SAP AG
IUT235
3-15
Interval Length Defined Header Data z
Formula
z
Interval length
z
Division
1......................................................................... 5 minutes........................................................................ 288 2......................................................................... 10 minutes........................................................................ 144 3......................................................................... 15 minutes........................................................................ 96 4......................................................................... 30 minutes........................................................................ 48 5......................................................................... 60 minutes........................................................................ 24 SAP AG 2003
Interval Length: intervals between two values in a profile. Defines the number of intervals per day and the time period of the interval. y Predefined By SAP: - 5 minute intervals - 288 per day - 10 minute intervals -144 per day - 15 minute intervals -96 per day - 30 minute intervals -48 per day - 60 minute intervals -24 per day
© SAP AG
IUT235
3-16
Result Parameter
Overview of the RTP Interface and Examples Header Data Result Parameter RTP Components
SAP AG 2003
© SAP AG
IUT235
3-17
Definition of RTP Result Parameters
Header data
Result parameter
RTP Components
RTP interface
Result parameter z Result number z Result parameter desc z Result function z Operand cat. z Unit of measurement z Proration SAP AG 2003
Result Number and Description: identify the Result Parameter
Result Function: y allocated to Result Parameters y define how profile values for a certain period are analyzed y used to calculate a single value such as a sum, minimum or maximum value
RTP Operands:
used in RTP rates to transfer the results of the RTP interface to the RTP rate in IS-U-
BI.
Operand Category:
fixed predefined characteristic that is allocated to an operand
- the Operand Category must match the category of the RTP operand in the Rate Facts
Unit of Measure: y unit of measure for the consumption profile values (i.e. kW, kWh, mWh, etc.)
Proration Option: y prorations to the RTP operands may be taken into consideration when the RTP interface is executed
© SAP AG
IUT235
3-18
Result Functions
Result Function
Σ Example: The result function totals the output amounts to determine on-peak usage
Result
Operand cat.
Unit of measurement
Result Function
e1
QUANT
kWh
SUM
e2
QUANT
kWh
SUM
e3
DEMAND
kW
PEAK
Result Desc. On-Peak consumption Off-Peak consumption Max. demand
SAP AG 2003
Result Functions calculate the value that is passed to the Result Parameters in the RTP-Interface. Result Functions define how profile values for a certain period are analyzed and used to calculate a single value such as a sum, minimum or maximum value. Result functions are defined with a description and a function module that performs the calculation. Results from result functions are currently only used as Input values in billing. This links the RTP interface to IS-U billing.
When a Result Parameter is defined, the Result Function, Unit of Measure and Operand Categories must also be assigned.
Result Functions can be customized. The following Result Functions are supplied by SAP: y MINIMUM:
Minimum Profile Value
y PEAK:
Maximum Profile Value
y SUM:
Total of Profile Values
© SAP AG
IUT235
3-19
Result Parameter:s (I)
Output Parameter 1
Result Function
Σ
Result parameter 1 Off-Peak consumption kWh = 275
ISIS-U-BI rate facts
Output Parameter 2
Result Function
Σ
Result parameter 2 On-Peak consumption kWh = 500
SAP AG 2003
Result parameters are assigned in the RTP interface. Result Parameters store discrete values. Output parameters are allocated to the Result Parameters. The Result Parameters are allocated to the RTP Rate in order to facilitate the billable quantities being passed to the IS-U-BI component.
In the above example, the following Result Parameters are being defined: y Off-Peak Consumption (1) - Summer/Weekend/On-Peak - Summer/Weekday/On-Peak y On-Peak Consumption (2) - Summer/Weekend/Off-Peak - Summer/Weekday/Off-Peak
© SAP AG
IUT235
3-20
Operand Categories Result
Operand cat.
Unit of measurement
Result Function
e1
QUANT
kWh
SUM
e2
QUANT
kWh
SUM
e3
DEMAND
kW
PEAK
Result Desc. On-Peak consumption Off-Peak consumption Max. demand
Rate: ON_OFF_PEAK RegOperand RTP interface
ON_OFF_PEAK
001
...
...
...
007
QUANTI01
ONPEAKCON
...
Pricing for ON Peak consumption
008
QUANTI01
OFFPEAKCON
...
Pricing for OFF Peak consumption
009
DEMAND01
MAXDEMAND
...
Pricing for max. demand
...
... SAP AG 2003
An Operand is an assigned value used as input and output parameters in variant programs.
The Operand Category classifies the operand for the variant programs. Within the RTP interface, the operand category must align with those used in the RTP Rate.
RTP Operands must first be defined in order to allocate Result Parameters to Operands in the Rate Facts.
The Operand Category must also be defined.
The operand category must match the category of the RTP operand.
© SAP AG
IUT235
3-21
RTP Components
Overview of the RTP Interface and Examples Header Data Result Parameter RTP Components
SAP AG 2003
© SAP AG
IUT235
3-22
RTP Component Data Defined
Header data
Result parameter
RTP Components
RTP interface
RTP Components z Components z Activation z Input Parameter z Output Parameter z Parameter Template SAP AG 2003
RTP Components define the structure of parameter allocations to the RTP-Interface and allow you to model the individual calculations in RTP billing. These are typically composed of a Day, TOU and/or Season Group. This structure links input, output and result parameters. Different component codes are required because parameter allocations require different period patterns (such as summer and winter). Different periods can be allocated (such as Season, Day and TOU Groups) to an RTP Component. The RTP Components allow you to model billing for different parts of a profile in the RTP interface. For example, a separate RTP Component for on- and off-peak periods and an RTP Component that determines the maximum demand for the entire period.
Activation defines the dates and time periods for which the RTP Component is active. The RTP components can be activated individually. This means that if there are two RTP components in the RTP interface, one can be allocated individually (at the installation level) and one can be allocated generally. When the RTP Components are activated, the parameters allocated to the RTP Component are used when the interface is executed.
Input Parameter: Profiles are allocated to the Input Parameters based on the business function (formula).
Output Parameter: Profiles are allocated to the Output Parameters based on the business function.
Template Parameter: Only defined if the Activation type is Use and Activate Individually or Use Individually and Activate Generally. This means that profiles can only be allocated to the Input parameter at the installation.
© SAP AG
IUT235
3-23
RTP Interface Components
Season day type TOU period component control:DD.MM.YYYY HH.MM - DD.MM.YYYY HH.MM active / inactive
Profile
Standard R/3
In
Pr1 = x1 Pr2 = x3
x1 x2 xn
Formula Defined
yn = f( x1, x2, xm )
Out
Standard R/3
y1 y2 y3
y1 -> e2 y3 -> e1
Result
Facts
e1 e2 en
Dem = e1 Con = e2
Profile
< value >
EDM Profile Management
Profile
Profile
(only during billing runtime)
(only during billing runtime)
RTP Interface
IS-U Billing
SAP AG 2003
© SAP AG
IUT235
3-24
RTP Component Structure Component 1 Component
Summer Weekend
Season Group
On-Peak kWh Summer
Off-Peak kWh
Winter
Weekday
Day Group
On-Peak kWh Weekday Weekend
Off-Peak kWh
Generates
Winter Weekend
TOU Group
On-Peak kWh Off-Peak kWh
On-Peak kWh Weekday
Off-Peak kWh
On-Peak kWh Off-Peak kWh SAP AG 1999
RTP components define the structure of the parameter allocations in the RTP interface. This structure links the input, output and result parameters. This structure also defines the period for billing. Some RTP components are based on time groups such as: y Season groups y Day groups y Time-of-use groups
Various RTP components may be required to support different periods (such as summer and winter) for parameter allocations. You can allocate various time groups, such as season groups, day groups and time-of-use groups within an RTP component. You define the structure of RTP components by allocating these time groups. You define season, day and time-of-use groups in Customizing (see the cookbook on basic Customizing settings or theSynthetic Profiles unit in IUT225).
RTP components allow you to model the different calculations in RTP billing. For example, you can define one RTP component each for on- and off-peak consumption and an RTP component that determines that maximum demand for the whole period.
RTP components are allocated to the RTP interface.
© SAP AG
IUT235
3-25
RTP Components Described Peak kW determined by component 1-PEAK
Off-peak consumption determined by component 2-ON-OFF
On-peak consumption determined by component 2-ON-OFF
Off-peak consumption determined by component 2-ON-OFF
On-peak consumption determined by component 2-ON-OFF
SAP AG 1999
Different RTP components allow you to slice the profile in different ways in order to calculate amounts for billing. For example, peak demand, on-peak consumption and off-peak consumption all need to be calculated. To calculate the total peak demand, you do not want to include any time periods such as onoff peak. In the above example, there are 2 RTP components. One RTP component is used to look at the entire profile (regardless of time period) and the other RTP component to slice the profile into on- and off-peak periods. y RTP component 1 PEAK: Determines peak demand for the entire time period and is not dependent on any day, TOU or season group y RTP component 2 ON-OFF: Deterimes the on- and off-peak consumption based on a time of use group.
Priorities are defined for each RTP component. These allow you to define which RTP component is used if there is more than one activation period.
When RTP components are allocated to the RTP interface, it is possible to distinguish between activation types. In order to bill customer-specific agreements, for example, you can individually allocate and activate an RTP component called Allocate and activate individually. In other words, you would allocate the RTP components only to those installations that you want to bill. Valid periods are defined for the agreement at the RTP interface level.
© SAP AG
IUT235
3-26
RTP Component - Profile Slicing
Measured Entry profile kW/kWh
off
on
off
on
off
Virtual profile
Result Function
Σ
Output Profile Off-Peak
off
off
off
Virtual profile Output Profile On-Peak
Result Function
Σ on
on
Result parameter Off-Peak consumption kWh = 275
Result parameter
On-Peak kWh = 500
SAP AG 2003
The RTP Components slice the measured profile as shown above by creating a virtual on- and off-peak profile (output parameters). It is important to note that these profiles are not stored in the database but are only used as input to the result function.
The result function then sums the results of the on- and off- peak virtual profiles to determine on- and off-peak consumption.
The result parameters are then passed via the Rate Facts into Input Operands of the Rate steps.
© SAP AG
IUT235
3-27
RTP Component Activation Installation
A.) Individual RTP Interface – set up in the INSTALLATION and is only used for billing on installation of the customer
Rate Category
Ind. RTP interface
Log register
Rate type
PI12
Rate
PI22
B.) General RTP interface assigned through the RATE
...
RTP interface
P1
P2
P12
LUMSUM02 RTPAMNT; ONE DEMAND01 VERLEIS; LEIPREI
SAP AG 2003
Variant programs
P= profile
...
There are three possible activation types for the RTP Component: y Use and Activate generally: - allows for definition of Input Parameter allocations at the level of the RTP-Interface - allows for activation of the RTP Component at the level of the RTP-Interface y Use and Activate individually: - allows for definition of Input Parameter allocations at the installation level - corresponding parameter templates can also be defined at the RTP-Interface level - Output Parameters can also be allocated at the RTP-Interface level - the RTP Component can also be activated at the installation level y Use individually and Activate generally: - allows for definition of Input Parameter allocations at the installation level - corresponding parameter templates can also be defined at the RTP-Interface level - the RTP Component can also be activated at the RTP interface level
© SAP AG
IUT235
3-28
Activation Types
Customer 1
Customer 8
Customer 7
Customer 2
Customer 3
Activated Generally (Rate)
Customer 6
Customer 4
Customer 5 Individually Activated (installation)
SAP AG 2003
RTP Components can be activated at the Rate, where they are generally assigned to numerous customers, or at the Installation where they are individually assigned to a customer.
© SAP AG
IUT235
3-29
RTP Component Prioritization - Generally Activated
Time Priority: medium
comp1
comp1
Priority: low
comp2
comp2
comp1
comp1
comp2
comp1
Component Execution comp1
Activated
Not activated
SAP AG 1999
When the RTP components are activated in the RTP interface, they are given a priority (1 – 99). The activated RTP component with the highest priority will be executed. The prioritization is used to determine which RTP component is valid when several RTP components have the same activation periods. In this case the RTP component with the highest priority is valid
In this scenario above, there are 2 RTP components. y RTP component 1 has a medium priority y RTP component 2 has low priority
RTP component 1 is always executed because it has the highest priority, except for the case when RTP component 1 is not active.
© SAP AG
IUT235
3-30
RTP Component Prioritization - Generally Activated
Time Priority: Medium
Comp1
Comp1
Priority: Low
Comp2
Comp2
Comp1
Comp1
Comp2
Comp1
Component execution Comp1
Activated
Not activated
SAP AG 2003
The activated RTP Component with the highest priority will be executed. The prioritization is used to determine which RTP Component is valid when several RTP Components have the same activation periods. In this case the RTP Component with the highest priority is valid
In this scenario above, there are 2 RTP Components. y RTP Component 1 has a medium priority y RTP Component 2 has low priority
RTP Component 1 is always executed because it has the highest priority, except for the case when RTP Component 1 is not active.
© SAP AG
IUT235
3-31
RTP Component Prioritization-Individually Activated Time General generated in the RTP Interface
Priority: medium
comp1
comp1
comp1
Priority: low
comp2
comp2
Individually Activated
Priority: high
comp3
comp3
comp3
comp3
comp3
comp1
comp2
comp3
comp1
comp1
RTP-Component Priority!
Component Execution
Activated
Not activated
SAP AG 2003
In this scenario above, there are 3 RTP Components. y RTP Component 1 has a Medium priority and is activated Generally at the RTP interface y RTP Component 2 has Low priority and is activated Generally at the RTP interface y RTP Component 3 has the highest priority and is activated individually at the installation level.
RTP Component 1 is executed in the first time block because it has the highest priority. RTP Component 2 is executed in the second time block because it is the only Active RTP Component. RTP Component 3 is executed in the third time block because it has the highest priority and is active. RTP Component 1 is executed in the last time block because it is active and has a medium priority (Over RTP Component 2).
The active RTP Component with the highest priority is always chosen, regardless of whether it is activated at the Installation or the RTP interface.
© SAP AG
IUT235
3-32
Input Parameter
RTP Component 1
RTP Component 2
Input 1
Input 1
Input 2
Input 2
Input 3
Input 3
Role: 0001
SAP AG 1999
Input parameters are defined within the RTP interface. Profiles are assigned to the input parameters within each RTP component. The values from these profiles are used in formula execution. Profiles can be allocated to the input parameter according to the structure defined in the RTP component.
Different profiles can be allocated to one input parameter in different RTP components. The profiles are used according to the priority defined for the RTP component and its corresponding activation periods.
Profiles can also be allocated to input parameters indirectly using roles. The input parameter is supplied with profile values when the RTP interface is executed. These profile values are assigned to a profile with a specified role and are allocated to the interval meter to be billed. This enables the user to provide an input parameter with only those profile values that match the load shape of the meter to be billed. For example, if a role of ‚0001‘ (measured consumption) is assigned to the input parameter, when the interface is executed, the system will look for the profile attached to that device with a role of ‚measured consumption‘. This makes the process more flexible so the profile number is not hard-coded into the interface.
© SAP AG
IUT235
3-33
Parameter Template RTP Interface EDM_01
RTP Component: SPOT Input 1 Installation 1: Value = 25
Input 2 (Parameter Template)
Installation 2: Value = 30
Installation 3: Value = 45 Input 3 SAP AG 1999
When an RTP component has the activation type Use and Activate Individually or Use Individually and Activate Generally, it is possible to define input parameters as template parameters. The advantage of template parameters is that they allow the user to define input parameters via the installation. This means that profiles or roles can ONLY be allocated to input parameters at the installation.
In the example above, the SPOT component is activated at the installation. During the time the individual component is activated, the profile allocated to the installation will be used for this calculation.
For example, if the parameter template was used, different limits can be defined for each customer, based on the customer-specific requirement. If input parameter 2 was a LIMIT value, then a different limit will be assigned for each customer: y Customer 1: limit = 25 y Customer 2: limit = 30 y Customer 3: limit = 45
© SAP AG
IUT235
3-34
Output Parameter RTP Component 1 Input 1 Input 2 Virtual profile
Output 1
Result Function
Σ
Virtual profile
Output 2
Result Function
Σ
Result parameter
Off-Peak kWh = 275
Result parameter
On-Peak kWh = 500
SAP AG 2003
Result Parameters are assigned in the RTP interface. Output Parameters are allocated to the Result Parameters. The Result Parameters are then allocated to the RTP Rate in order to facilitate the billable quantities being passed to the IS-U-BI component.
© SAP AG
IUT235
3-35
Putting it all Together - RTP Interface Review RTP Interface I. Header Data Formula Defined
Interval Length Defined
II. RTP Components
Division Defined
III. Result Parameters
1. On-Off Component
N u m b e r
On-Peak Component Code In Out – Portion above 1st limit (QUANTITY) à on-peak
Off-Peak Component Code In Out – Portion above 1st limit (QUANTITY) à off-peak
Default Component Code
Result
Operand Result Category Function
1
On-Peak Cons
QUANT
SUM
2
Off-Peak Cons
QUANT
SUM
3
Peak Demand
DEMAND
PEAK
In 1 – Measured value (QUANTITY) à historic consumption Out
Component structure is time sliced for onand off-peak periods
2. Peak Component Default Component Code In 1 – Measured value (QUANTITY) à historic consumption Out – Demand above limit (DEMAND) à max. demand
Component structure is NOT time sliced
SAP AG 1999
Within the header data, the formula defines the input and output parameters that will be allocated within the RTP components.
RTP components allow flexible use of allocation to an individual installation or a group of customers.
The RTP components allow slicing of the profile by different time allocations such as TOU, day or seasons.
The output parameters are allocated to the result parameters.
The result parameters are allocated to operand categories in the RTP interface. The result parameters are also allocated to operands in the rate facts. The operand category must match the category of the RTP operand.
© SAP AG
IUT235
3-36
Using an RTP Interface Rate: EDM_01 Permissibility
Register-Based Data
X Interval meter
RTP Interface:
Allocate the RTP interface to the rate
EDM_01
Rate Facts/Operands Operands:
Off-Peak Consumption
Operand Category:
QUANT
Result Parameter:
2 – Off-Peak Consumption
Must match RTP operand in the RTP interface
X RTP Operand
Rate Steps Variant
InputOp01
InputOp02
InputOp01
Statistical Rate
001
QUANTI01
ONPEAKUSG
ONPEAKPRICE
ONPEAKAMT
EDM_01
002
QUANTI01
OFFPEAKUSG
OFFPEAKPRICE OFFPEAKAMT
EDM_01
SAP AG 1999
Before the RTP interface can be used, it must be allocated to a rate. This allocation is only possible for rates that have selected the Permitted for Interval Meters option. Within the RTP rate facts, individual rate step input operands can be allocated to result parameters of the RTP interface. This means that the appropriate operands are provided with result parameter values from the RTP interface during billing.
It is only possible to allocate result parameters to operands in the rate facts if the RTP operands have been defined. The operand category must also be assigned. This is the operand category in which the RTP rate values in the RTP rate are to be processed. The operand category must match the category of the RTP operand.
© SAP AG
IUT235
3-37
Exercises Unit: Elements in an RTP interface Topic: Follow-Up At the conclusion of these exercises, you will be able to • Describe the elements of an RTP interface • Describe the elements of an RTP rate • Perform billing analysis for an RTP rate Various tests of your existing RTP rate have shown that differentiation by on and off-peak rates and consideration of maximum demand is not sufficient. In this exercise, you change the rates used at the installation and use the changed billing master data to analyze the RTP rate and the RTP interface again. 1-1
Change the rates used for your TR0101A0## installation. Use the rate maintenance function from the CIC context menu to do so. Go to the SAP Easy Access menu and choose Utilities Industry Æ Customer Service Æ Front Office/Customer Interaction Center Æ Customer Interaction Center. 1-1-1
Identify the business partner TR0101A0## and display its data environment. ___________________________________________________ ___________________________________________________
1-1-2
Use the rate maintenance function to change the RTP rate. How do you proceed? ___________________________________________________ ___________________________________________________ Change EDM rate category to EDM_01. ___________________________________________________ Which new rate determination does this produce? ___________________________________________________ ___________________________________________________
© SAP AG
IUT235
3-38
1-2
Display the header data of the RTP interface. Go to Customizing for SAP Utilities and choose Energy Data Management Æ Interface to RTP Billing Æ Define RTP Interface Æ Display RTP Interface. 1-2-1
Identify the data for the RTP interface EDM_01. _________________________________________________ _________________________________________________
1-2-2
Which formula is allocated to the RTP interface? _________________________________________________ _________________________________________________
1-2-3
How many input and output parameters are defined in the formula LIMIT01? _________________________________________________ _________________________________________________
1-3
Display the result parameter of the RTP interface. 1-3-1
How may results parameters are defined in RTP-Interface EDM_01? _________________________________________________ _________________________________________________
1-3-2
Note the results parameters for the individual results functions in the RTP interface EDM_01. _________________________________________________ _________________________________________________
© SAP AG
IUT235
3-39
1-4
Display the RTP components for the RTP interface (activation, input and output parameters, and parameter template). 1-4-1
How many components make up the RTP interface EDM_01? List the RTP components: _________________________________________________ _________________________________________________
1-4-2
How many components in RTP interface EDM_01 are active? Which components are active? _________________________________________________ _________________________________________________
1-4-3
Which activation type is allocated to the RTP component 0005 Æ (billing of peak demand) in RTP interface EDM_01? A. B C.
1-4-4
Use and activate generally Use and activate individually Use individually and activate generally
Which component in RTP interface EDM_01 has the highest priority? _________________________________________________ _________________________________________________
1-4-5
If RTP interface EDM_01 were now activated, what result would be determined for the RTP component 006 (billing for spot price agreement)? _________________________________________________ _________________________________________________
1-4-6
How many input parameters (not including parameter templates) are allocated to RTP interface EDM_01? Make a list of these parameters. _________________________________________________ _________________________________________________
© SAP AG
IUT235
3-40
1-4-7
Search for the Measured value QUANTITY input parameter for the second RTP component (005 Æ billing of peak demand). Input parameters can be allocated in three ways. How was the profile allocated to this input parameter? _________________________________________________ _________________________________________________
1-4-8
Which parameter template is defined in the RTP interface EDM_01? _________________________________________________ _________________________________________________
1-4-9
How are you able to use this parameter template? _________________________________________________ _________________________________________________
1-4-10
How may output parameters are defined in RTP-Interface EDM_01? Make a list of the allocated output parameters. Field name or data category
Values
_________________________________________________ _________________________________________________
© SAP AG
IUT235
3-41
1-4-11
Note the individual output parameters and the corresponding result parameters. RTP Component
© SAP AG
Output Parameter
IUT235
Result Parameter
3-42
Exercises Unit: Elements in an RTP interface Topic: Execute RTP interface EDM_01 At the conclusion of these exercises, you will be able to • Execute the EDM_01 RTP interface for your business partner, using a billing simulation • Activate a temporary spot agreement at installation level for your customer • Execute the EDM_01 RTP interface with an individual spot agreement First of all a customer with an interval meter must be billed for the on-peak and off-peak rate consumption, and maximum demand. Then during the billing period, an individual spot agreement must be activated, where an individual quantity limit is allocated to the customer at installation level. The customer must now be billed for the spot agreement with the individual allocated quantity limit. 2-1
Run a billing simulation with RTP interface EDM_01. In the SAP menu, choose Utilities Industry → Billing → Billing Execution -> Individual Processing → Billing Analysis. 2-1-1
Run an individual simulation (billing analysis) for your installation for the period from January 1, YYYY to January 31, YYYY (YYYY = current year). _____________________________________________________ _____________________________________________________
2-1-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
2-1-3
Display the document and note the billing document number: Billings document number: ________________________________
© SAP AG
IUT235
3-43
2-1-4
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Result Parameter
Net amount
Billing quantity
On-peak rate consumption Off-peak rate consumption Maximum demand 2-1-5
Run an RTP analysis for the billing simulation. _____________________________________________________ _____________________________________________________
2-1-6
How many input parameters were used in the simulation? _____________________________________________________ _____________________________________________________
2-1-7
What is the total of the profile values used for input parameter 1? __________________
2-1-8
How many output parameters were determined in the simulation? Which output parameters were determined? _____________________________________________________ _____________________________________________________
2-1-9
How many result parameters were determined in the simulation? List the determined result parameters. _____________________________________________________ _____________________________________________________
2-1-10 What values do the individual result parameters have? _____________________________________________________ _____________________________________________________ © SAP AG
IUT235
3-44
2-1-11
Which periods are defined for the on-peak and off-peak rate periods within the RTP interface? Note the defined periods. Call up another session and look for the definition of time-of-use types in the Customizing settings. On-peak rate period
__________________
Off-peak rate period __________________ __________________ 2-1-12
Export the values for the off-peak rate parameters to Excel, and add up the offpeak rate values. What is the result? _____________________________________________________ _____________________________________________________
2-2
Run an invoicing simulation for the bill period. 2-2-1
Run an invoicing simulation for the billing analysis you just executed. _____________________________________________________ _____________________________________________________
2-2-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
2-2-3
Display the print document. _____________________________________________________ _____________________________________________________
2-2-4
Display the bill preview. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
3-45
2-2-5
What are the price, quantity and amount for the following parameters: Result Parameter
Billing quantity
Price
Net amount
On-peak rate consumption Off-peak rate consumption Maximum demand 2-3
Activate a temporary spot agreement within the installation. In the Utilities Industry menu, choose Technical Master Data → Installation → Change. 2-3-1
Enter the ID of your installation. _____________________________________________________ _____________________________________________________
2-3-2
By activating the spot component, specify a temporary special agreement in the installation. Ensure that the value of the maximum demand is contained in the agreement period. The value of the maximum demand occurred on January 13, YYYY. _____________________________________________________ _____________________________________________________
2-3-3
Check the installation and determine whether the component is activated. _____________________________________________________ _____________________________________________________
2-3-4
In the spot component, allocate the limit value profile (25) from January 1, YYYY in the Allocate Profiles or Roles to Components screen. This is a limit value, and the price of the special agreement applies to any values above this limit value. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
3-46
2-4
Run a billing simulation for the individual agreement. 2-4-1
Run an individual simulation (billing analysis) for your installation. Take into account the individual agreement for the period January 1, YYYY to January 31, YYYY. _____________________________________________________ _____________________________________________________
2-4-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
2-4-3
Display the document and note the billing document number: Billing document number:
2-4-4
___________________
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Result Parameter
Net amount
Billing quantity
Spot consumption below baseline Spot consumption above baseline On-peak rate consumption Off-peak rate consumption Maximum demand 2-4-5
Run an RTP analysis for the billing simulation. _____________________________________________________ _____________________________________________________
2-4-6
Why was nothing billed for the six result parameters (maximum demand for spot agreement?). _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
3-47
2-4-7
What happens when the spot component is activated? _____________________________________________________ _____________________________________________________
2-4-8
Run an invoicing simulation for the billing analysis you just executed. _____________________________________________________ _____________________________________________________
2-4-9
Ensure that the simulation was successful. _____________________________________________________
2-4-10
Display the print document. _____________________________________________________
© SAP AG
IUT235
3-48
Solutions Unit: Elements in an RTP interface Topic: Follow-Up
1-1 1-1-1
In the business partner field (Part/tel), enter the number of your business partner. Field name or data category
Values
Business partner
TR0101A0##
From the initial screen, choose Enter. Choose Confirm Partner. The data environment for your business partner is now available in the navigation area. 1-1-2
Use the rate maintenance function to change the RTP rate. How do you proceed? Select the installation in the navigation area. The Rate Maintenance access is found in the context menu. You should ensure that you make subsequent changes for the 01.01.YYYY. Old Rate Category
New Rate Category
EDM
EDM_01
Which new rate determination does this produce?
© SAP AG
Field name or data category
Values
Rate type
1008
Rate Category
EDM_01
Rate
EDM_01
RTP interface
EDM_01
IUT235
3-49
1-2 1-2-1
1-2-2
1-2-3
Enter the RTP interface. Field name or data category
Values
RTP interface
EDM_01
Which formula is allocated to the RTP interface? In the Header Data tab page, search for the Formula field. Field name or data category
Values
Formula
LIMIT01
How many input and output parameters are defined in the formula LIMIT01? On the left-hand side of the screen, search for the input and output parameters for each component. 3 Input Parameters, 4 Output Parameters
© SAP AG
Field name or data category
Values
Input parameter 1
Measured value QUANTITY
Input parameter 2
First value limit as quantity QUANTITY
Input parameter 3
Second value limit as quantity QUANTITY
Output parameter 1
Portion below first limit QUANTITY
Output parameter 2
Portion above first limit QUANTITY
Output parameter 3
Portion above second limit QUANTITY
Output parameter 4
Demand above limit DEMAND
IUT235
3-50
1-3
Display the result parameter of the RTP interface. 1-3-1
1-3-2
How may results parameters are defined in RTP-Interface EDM_01? Choose Result parameters. Six result parameters are defined. Field name or data category
Values
Result parameter 1
On-peak rate consumption
Result parameter 2
Off-peak rate consumption
Result parameter 3
Maximum demand
Result parameter 4
Spot consumption below baseline
Result parameter 5
Spot consumption above baseline
Result parameter 6
Maximum demand for spot agreement
Note the results parameters for the individual results functions in the RTP interface EDM_01. The SUM results function is used to determine the following: - On-peak rate consumption - Spot consumption below baseline
Off-peak rate consumption Spot consumption above baseline
The PEAK results function is used to determine the following: - Maximum demand
© SAP AG
Maximum demand for spot agreement
IUT235
3-51
1-4
Display the RTP components for the RTP interface (activation, input and output parameters, and parameter template). 1-4-1
How many components make up the RTP interface EDM_01? List the components: On the left-hand side of the screen, identify the components (symbol with 3 documents). Three components are defined.
1-4-2
Field name or data category
Values
Component 1
0006Æ Billing of spot agreement
Component 2
0005Æ Billing of peak demand
Component 3
0001Æ Billing of on- and offpeak rates
How many components in RTP interface EDM_01 are active? Which components are active? You can find the entries on the screen on the RTP components tab page under the Activation tab page. 2 components are defined.
1-4-3
Field name or data category
Values
Component 2
0005Æ Billing of peak demand
Component 3
0001Æ Billing of on- and offpeak rates
Which activation type is allocated to the RTP component 0005 Æ (billing of peak demand) in RTP interface EDM_01? On the left-hand side of the screen, double-click the RTP component 005 Æ billing of peak demand. You can find the entries on right-hand side of the screen on the RTP components tab page in the Activation type field. A. Use and activate generally
© SAP AG
IUT235
3-52
1-4-4
Which component in RTP interface EDM_01 has the highest priority? On the left-hand side of the screen, double-click on each RTP component. You can find the entries on right-hand side of the screen on the RTP components tab page in the Priority field. Or Identify the RTP components on the left-hand side of the screen. The priority is to the right of the name of the RTP component. 0006 Æ Billing of spot agreement
1-4-5
If RTP interface EDM_01 were now activated, what result would be determined for the RTP component 006 (billing for spot price agreement)? None, since the component is currently inactive.
1-4-6
How many input parameters (not including parameter templates) are allocated to RTP interface EDM_01? Make a list of these parameters. On the left-hand side of the screen, search for the input parameters for each of the active RTP components (indicated by a green circle). OR Go to the RTP components tab page and choose the Input parameters tab page. (Note that you must perform this step for each RTP component in the interface). 3 input parameters are allocated.
© SAP AG
Field name or data category
Values
Component 1, 0006 Æ billing of spot agreement
Measured value QUANTITY
Component 2, 0005 Æ billing of peak demand
Measured value QUANTITY
Component 3, 0001 (billing according to on or offpeak rate, default component code)
Measured value QUANTITY
IUT235
3-53
1-4-7
Search for the Measured value QUANTITY input parameter for the second RTP component (005 Æ billing of peak demand). There are 2 ways of allocating profiles to the input parameter. How was the profile allocated to this input parameter? Double-click on RTP component 0005 Æ billing of peak demand. Double-click on the Measured value QUANTITY input parameter and choose the Input parameter tab page on the RTP components tab page. Profiles can be allocated in the following ways: 1) Using the profile number 2) Using the profile role 3) As a constant value In this case, the profile is allocated via a role. This means that when the RTP interface is executed, the profile is used with the Measured consumption role (0001):
1-4-8
1-4-9
Which parameter template is defined in the RTP interface EDM_01? Field name or data category
Values
Component 1, 0006 Æ billing of spot agreement
First limit value as QUANTITY (second input parameter)
How are you able to use this parameter template? You can allocate individual profile to an installation.
© SAP AG
IUT235
3-54
1-4-10
How may output parameters are defined in RTP-Interface EDM_01? Make a list of the allocated output parameters. On the left-hand side of the screen, search for the output parameters for each of the active RTP components (indicated by a green circle). OR Go to the RTP component tab page and choose the Outp. parameters tab page. 6 output parameters are allocated. 3 output parameters are allocated to the first RTP component 0006 Æ billing of spot agreements. 1 output parameter is allocated to the first RTP component 0005 Æ billing of peak demand). 2 output parameters are allocated to the third RTP component 0001 Æ on and off-peak.
© SAP AG
Field name or data category
Values
Component 1, 0006 Æ billing of spot agreement
Portion below first limit QUANTITY
Component 1, 0006 Æ billing of spot agreement
Portion above first limit QUANTITY
Component 1, 0006 Æ billing of spot agreement
Demand above limit DEMAND
Component 2, 0005 Æ billing of peak demand
Demand above limit DEMAND
Component 3, 0001 Æ on or off-peak, component code for on-peak period
Portion above first limit QUANTITY
Component 3, 0001 Æ on or off-peak, component code for off-peak period
Portion above first limit QUANTITY
IUT235
3-55
1-4-11
Note the individual output parameters and the corresponding result parameters.
RTP Component
Output Parameter
Result Parameter
Component 1, 0006 Æ billing of spot agreement
Portion below first limit QUANTITY
Spot consumption below baseline
Component 1, 0006 Æ billing of spot agreement
Portion above first limit QUANTITY
Spot consumption above baseline
Component 1, 0006 Æ billing of spot agreement
Demand above limit DEMAND
Maximum demand for spot agreement
Component 2, 0005 Æ billing of peak demand
Demand above limit DEMAND
Maximum demand
Component 3, 0001 Æ on or off-peak, component code for on-peak period
Portion above first limit QUANTITY
On-peak rate consumption
Component 3, 0001 Æ on or off-peak, component code for off-peak period
Portion above first limit QUANTITY
Off-peak rate consumption
© SAP AG
IUT235
3-56
Solutions Unit: Elements in an RTP interface Topic: Execute RTP interface EDM_01 2-1 2-1-1
Run an individual simulation (billing analysis) for your installation for the period from January 1, YYYY to January 31, YYYY. Enter the following data on the initial screen for automatic billing and simulation: Select the simulation in the Billing types group frame. Field name or data category
Values
Simulation period
01.01.YYYY - 31.01.YYYY
Select the Installation in the Selection criteria group frame. Field name or data category
Values
Installation
TR0101A0##
Select Bill/simulate (F8). 2-1-2
Ensure that the simulation was successful. Check that the following message is displayed at the bottom, left hand side of the screen: Simulation of installation TR0101A0## was carried out successfully.
2-1-3
Display the document and note the billing document number: Billing document number: ___________________ Select Display document. Choose Enter.
2-1-4
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Choose the Doc. overview tab page.
© SAP AG
Result Parameter
Net amount
Billing quantity
On-peak rate consumption
1.469,02
24.483,72
Off-peak rate consumption
712,89
23.762,86
IUT235
3-57
Maximum demand 2-1-5
2.193,27
215,20
Run an RTP analysis for the billing simulation. Choose the RTP analys. tab page. Choose Start analysis.
2-1-6
How many input parameters were used in the simulation? Choose the Overview tab page on the Input parameters tab page. Æ Three input parameters were used.
2-1-7
What is the total of the profile values used for input parameter 1? __________________ Select the first input parameter in the Input Parameter Formula group frame. (The profile values are displayed below in the Profile values group frame). Select the Value column in the Profile values group frame. To see the totals, choose Total and scroll to the end of the table.
2-1-8
Field name or data category
Values
Total of profile values for input parameter 1
48.246,58
How many output parameters were determined in the simulation? Which output parameters were determined? Choose the Overview tab page on the Output parameter tab page. Æ Two input parameters were used.
© SAP AG
Field name or data category
Values
Output parameter 1
On-peak consumption 02 Portion above first limit
Output parameter 2
Off-peak consumption 04 Demand above limit
IUT235
3-58
2-1-9
How many result parameters were determined in the simulation? List the determined result parameters. Choose the Overview tab page on the Result parameters tab page. Æ 3 result parameters were determined:
2-1-10
2-1-11
Field name or data category
Values
Result parameter 1
On-peak rate consumption
Result parameter 2
Off-peak rate consumption
Result parameter 3
Maximum demand
What values do the individual result parameters have? Field name or data category
Values
On-peak rate consumption
24.483,72
Off-peak rate consumption
23.762,86
Maximum demand
215,2
Which periods are defined for the on-peak and off-peak rate periods within the RTP interface? Note the defined periods. Call up another session and look for the definition of time-of-use types in the Customizing settings. On-peak rate period
__________________
Off-peak rate period
__________________ __________________
Go to Customizing for SAP Utilities and choose Energy Data Management → Basic Settings → Time-of-Use Group → Define Time-of-Use Types. Select the on-peak rate period (season type 0001) and double-click on the Definition folder. Select the off-peak rate period (season type 0002) and double-click on the Definition folder. Æ On-peak rate period
08:00:00 – 17:59:59
Æ Off-peak rate period
00:00:00 – 07:59:59 18:00:00 – 23:59:59
© SAP AG
IUT235
3-59
2-1-12
Export the values for the off-peak rate parameters to Excel, and add up the offpeak rate values. What is the result? Go back to the billing simulation and display the billing document. Choose the RTP analy. tab page. Start the RTP analysis. Select the parameter number for off-peak rate consumption (result 2) in the Result parameters section. Choose Export and then Spreadsheet. Choose Enter. Select the pivot table in the Export list object to XXL dialog box. Choose Enter. Choose Enter in the dialog box with the Microsoft Excel option. The number of the results parameter is displayed in the first column of the spreadsheet that opens. Scroll down till you come to the ‘002 result’ line. (Alternatively, you can also use the existing filter and hide the 001 and 003 results numbers).
2-2
Field name or data category
Values
Off-peak rate consumption
23.762,86
Run an invoicing simulation for the bill period. 2-2-1
Run an invoicing simulation for the billing analysis you just executed. Choose Invoicing simulation on the initial screen for automatic billing and simulation. Ensure that the number of the billing document is correct. Choose Enter.
2-2-2
Ensure that the simulation was successful. Check that the following message appears at the bottom left hand side of the screen: Invoicing completed.
2-2-3
Display the print document. Choose Display print document on the initial screen for automatic billing and simulation. Choose Enter. Display the bill preview. Choose Bill preview on the Display Print Document screen.
© SAP AG
IUT235
3-60
2-2-4
What are the price, quantity and amount for the following parameters: Result Parameter
Billing quantity
Price
Net amount
On-peak rate consumption
24.483,72
0,06
1.469,02
Off-peak rate consumption
23.762,86
0,03
712,89
Maximum demand
215,20
120,00
2.193,27
Note: The demand price printed on the bill is 120. The demand price in the rate facts is 10 USD/kWh. The system uses 120, because an annual price (10 USD * 12 months) is determined from the monthly price of 10. Since period control for the individual rate steps is set to the basic procedure for an exact number of days, the following calculation takes place, and is deceptive on the billing form: We have billed for January, which includes 31 days. (31 / 365) * 120 = 10.19 (final price) 215.20kW * 10.19 = ~2193.27
© SAP AG
IUT235
3-61
2-3
Activate a temporary spot agreement within the installation. In the Utilities Industry menu, choose Technical Master Data → Installation → Change. 2-3-1
Enter the ID of your installation. Field name or data category
Values
Installation
TR0101A0##
Choose Enter. 2-3-2
By activating the spot component, specify a temporary special agreement in the installation. Ensure that the value of the maximum demand is contained in the agreement period. The value of the maximum demand occurred on January 13, YYYY. Choose RTP interface in the Change Installation screen. Expand the data objects below the Installation (top left on screen). Open up the data objects and double-click on the component (0006). Choose the Component tab page. Select the Activate field. Enter the date January 13, YYYY in the From-Date field. Choose Copy to table. Go back. Save your data in the Change Installation screen.
2-3-3
Check the installation and determine whether the component is activated. Return to the installation. Choose RTP interface in the Change Installation screen. Expand the data objects below the Installation (top left on screen). Expand the data objects and double-click on the component (0006). According to the Component tab page, the component should be activated from January 13, YYYY.
2-3-4
In the spot component, allocate the limit value profile (25) from January 1, YYYY in the Allocate Profiles or Roles to Components screen. This is a limit value, and the price of the special agreement applies to any values above this limit value. Expand the data objects below the Installation (above left on screen) in the Allocate Profiles or Roles to Components screen. Expand the data objects and double-click on input parameter 02. Choose the Parameter tab page. Enter the date January 01, YYYY in the From-Date field. Enter the value limit profile 25 in the Profile field. Choose Copy to table. Alternatively, you can enter the value 25 in the Constant Value field. Go back. Save your data in the Change Installation screen.
© SAP AG
IUT235
3-62
2-4
Run a billing simulation for the individual agreement. 2-4-1
Run an individual simulation (billing analysis) for your installation. Take into account the individual agreement for the period January 1, YYYY to January 31, YYYY.
2-4-2
Ensure that the simulation was successful. Check that the following message is displayed at the bottom, left hand side of the screen: Simulation of installation TR0101A0## was carried out successfully.
2-4-3
Display the document and note the billing document number: Billing document number: ___________________ Select Display document. Choose Enter.
2-4-4
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Choose the Doc. overview tab page.
2-4-5
Result Parameter
Net amount
Billing quantity
Spot consumption below baseline
607,74
30.387,18
Spot consumption above baseline
440,86
5.510,78
On-peak rate consumption
371,50
6.191,60
Off-peak rate consumption
184,71
6.157,02
Maximum demand
2.123,97
208,04
Run an RTP analysis for the billing simulation. Choose the RTP analys. tab page. Choose Start analysis.
© SAP AG
IUT235
3-63
2-4-6
Why was nothing billed for the six result parameters (maximum demand for spot agreement?). The operand for the Maximum Demand for Spot Agreement parameter is not allocated to rate EDM_01 in the rate facts. Display rate EDM_01 in transaction EA32. Choose the Facts pushbutton. The RTP operand for Maximum Demand for Spot Agreement is not allocated in the rate facts. No value is therefore calculated for this result parameter.
2-4-7
What happens when the spot component is activated? The quantity above and below the limit is determined and multiplied with the spot price.
2-4-8
Run an invoicing simulation for the billing analysis you just executed. Choose Invoicing simulation on the initial screen for automatic billing and simulation. Ensure that the number of the billing document is correct. Choose Enter.
2-4-9
Ensure that the simulation was successful. Check that the following message appears at the bottom left hand side of the screen: Invoicing completed.
2-4-10
Display the print document. Choose Display print document on the initial screen for automatic billing and simulation. Choose Enter. Display the bill preview. Choose Bill preview on the Display Print Document screen.
© SAP AG
IUT235
3-64
Customizing Steps to Build an RTP Interface
Customizing the RTP Interface Steps to Build an RTP Interface Allocating the RTP Interface to a Rate
SAP AG 2003
© SAP AG
IUT235
4-1
Course Objectives At the conclusion of this unit, you will be able to: z Recognize use of TOU, season and day groups z Define and generate RTP components z Define result functions z Prioritize and activate components z Assign input and output parameters z Use templates to define the RTP Interface z Define and set up result
parameters
z Allocate the RTP interface
to a rate
SAP AG 2003
© SAP AG
IUT235
4-2
Customizing the RTP Interface
Customizing the RTP Interface Steps to Build an RTP Interface Allocating the RTP Interface to a Rate
SAP AG 2003
© SAP AG
IUT235
4-3
Elements in the RTP Interface
Header Data
Result parameter
RTP Components
z Formula
z Result Number
z Components
z Interval length
z Result Parameter
z Activation
z Division
Desc
z Input Parameter
z Result Function z Operand cat.
z Output Parameter z Parameter Template
z Unit of measurement z Proration
RTP interface SAP AG 2003
The RTP interface is built from the Header Data, Result Parameters and RTP Components. In order to customize an RTP interface, these building blocks must be developed. The following slides give you the information needed to build and customize an RTP interface.
© SAP AG
IUT235
4-4
Process Flow for Creating an RTP Interface No
Set up Season, Day, TOU Groups
Determine RTP interface to be used
Exist?
No
Determine RTP components to be used.
Exist? Yes
Define RTP components
Exist?
Define RTP Interface
No
Define blocks
No
Determine formula to be used.
Define formulas
Exist? Yes
Allocate RTP header data.
Allocate result parameter
Allocate components
Allocate input parameter
Allocate output parameter
SAP AG 2003
Set up Season, Day and TOU Groups (i.e. component structure). This takes place outside RTP Customizing by means of the following menu path: Utilities Industry ® Energy Data Management ® Basic Settings
Determine RTP interface to be used. If the desired RTP interface does not exist, you can create it in Customizing. SAP Utilities Energy Data Management ® Interface to RTP Billing Define RTP interface
Determine RTP components to be used. If the desired RTP component does not exist, you can create it in Customizing. SAP Utilities Energy Data Management ® Interface to RTP Billing Defining RTP Components
Determine formula to be used. If the desired formula does not exist, you can create it in Customizing. SAP Utilities Tools System Modifications ® User-Defined Enhancements for Energy Data Management ® Formulas (for further information, see the Formula Profiles unit of IUT225)
Allocate RTP header data.
Allocate result parameters
Allocate RTP components
Allocate input and output parameters to each component
© SAP AG
IUT235
4-5
Customizing Steps to Build an RTP Interface SAP Utilities EDM Basic Settings Season Groups
Define Season Types Define Season Groups Define Day Types Define Day Groups
Day Group
Define TOU Types
TOU Group
Define TOU Groups Customize RTP Component
Interface to RTP Billing
Customize RTP Interface
Tools System Modifications User-Defined Enhance. for EDM
Result Functions
Customize Result Functions Define Information Types
SAP AG 1999
You can make the settings listed on the slide for the RTP interface. The following settings are dealt with in this unit: y Define RTP component y Define RTP interface y Define result functions
© SAP AG
IUT235
4-6
Customizing an RTP Component
RTP Component ID
Description
On-Off
On- and Off-Peak Consumption
Season On-Off
Seasonal On-Off Peak Cons
Peak
Maximum Demand
RTP Comp: OnOn-Off TOU Group 1: On-Off Peak
Season Group
Day Group
TOU Group 1
2
RTP Comp: Season OnOn-Off
1
RTP Comp: Peak
Seas Grp 2: Year Div in Sum/Win
TOU Type 1: On-Peak
Season Type 1: Summer
TOU Type 2: Off-Peak
Season Type 2: Winter TOU Group 1: On-Off Peak TOU Type 1: On-Peak TOU Type 2: Off-Peak
SAP AG 1999
RTP Component Structure is comprised of a unique combination of Season Groups, Day Groups and TOU Groups.
When an RTP Component is customized the following information is entered: y RTP Component ID y RTP Description y Season, Day or TOU Groups as defined by the requirements (not all have to be chosen)
When a new RTP Component is created, the Day, Season or TOU groups are allocated to the RTP Component.
In the above example, there are 3 RTP Components y On-Off which is comprised of just a TOU Group y Season On-Off which is made up of both a Season Group and a TOU Group y Peak which contains no time periods at all
Path to Customizing: SAP Utilities Æ Energy Data Management Æ Interface to RTP Billing Æ Define RTP Component
By allocating these Groups to the RTP Component in the RTP-Interface, it signals billing to be carried out according to these defined time periods.
After the RTP Component is created, it must be Generated before it can be used. Once the RTP Component has been generated, no changes can be made.
© SAP AG
IUT235
4-7
Customizing Result Functions
Result Function
Description
Function Module
MINIMUM
Minimum profile value
ISU_EDM_RESULT_0003
PEAK
Maximum profile value
ISU_EDM_RESULT_0002
SUM
Total of profile values
ISU_EDM_RESULT_0001
SAP AG 1999
Result Functions define how profile values for a certain period are analyzed and used to calculate a single value such as a sum, minimum or maximum value.
Result functions are defined with a description and a function module that performs the calculation. Results from result functions are currently used as input values in billing. This links the RTP interface to IS-U billing.
Those provided by SAP are:
Function
Description
Function Module
y MINIMUM:
Minimum Profile Value
ISU_EDM_RESULT_0003
y PEAK:
Maximum Profile Value
ISU_EDM_RESULT_0002
y SUM:
Total of Profile Values
ISU_EDM_RESULT_0001
Result Function modules can be created at the customer site and implemented in this customizing process.
© SAP AG
IUT235
4-8
Steps to Build an RTP Interface
Customizing the RTP Interface Steps to Build an RTP Interface Allocating the RTP Interface to a Rate
SAP AG 2003
© SAP AG
IUT235
4-9
Header Data RTP Interface: RTP Interface Description:
Header Data Formula: In
Profile
Interval Length:
Profile Profile
Formula
x1 x2
Out y1
yn = min( x1, x2,xm)
xn
y2 ym
Profile Profile Profile
Division: SAP AG 2003
The following data must be entered to start the creation of the RTP-Interface: y RTP Interface Code and Description: identifies the RTP interface - Header data Formula, Interval Length, Division
Note: The Formula is the basis of the calculation as it determines the input and output parameters.
© SAP AG
IUT235
4-10
Result Parameter Operand Category to which the RTP Interface result can be passed
Results can be passed to the Rate Step of the RTP Rate
Result Number
Operand cat.
Unit of measurement
Result Function
Result Parameter Desc
1
QUANT
kWh
SUM
On-Peak consumption
2
QUANT
kWh
SUM
Off-Peak consumption
3
DEMAND
kW
PEAK
Max. demand
Installation
Rate Category
Result Function used to calculate the Output Parameters
Ind. RTP interface
Log register
Rate type
Rate
PI12
PI22 P_VB
P_FC RTP interface P1
P2
P12
LUMSUM02 RTPAMNT; ONE DEMAND01 BILLABLE KW; PEAK KW
SAP AG 2003
To create Result Parameters, the following information must be entered: y Result Number, Result Parameter Description, Operand Category, Result Function, Unit of Measure (use the ‚copy‘ pushbutton to insert the information into the RTP interface)
Note: The Result Parameters come from the Result Function. Result Parameters are assigned to operand categories and reference the output parameters. The Result Parameters supply the operands with data for the RTP rate used in IS-U billing.
© SAP AG
IUT235
4-11
Components RTP Component: On-Off
Activation Type: Use and Activate Generally Use and activate generally Use and activate individually Use individually and activate generally
Enter for each component
Priority: 1
To-Date: 31.12.9999
From-Time: 00:00:00
To-Time: 23:59:59
Period
From-Date: 01.01.00
SAP AG 2003
RTP Components: Activation, Input Parameters, Output Parameters and possibly Template Parameters should be defined for each RTP Component, depending on the requirements. Note: The Activation type and Priority should be defined.
In the ‚Activation‘ tab, enter the following: y Choose an RTP Component y For each RTP Component, enter the following: - Choose one of the Activation Types - For each RTP Component, enter the following: Enter a Priority for the RTP Component (if several RTP Components have the same activation period, this number defines which RTP Component is valid). RTP Components are sorted by priority. The prioritization is used to determine which RTP Component is valid when several RTP Components have the same activation periods. The component with the highest priority is valid in each case. To enter data in the fields, choose Insert component. - Enter a period in the "From/To Date" and "From/To Time" fields. (Choose the "Copy" function to insert the data below.)
© SAP AG
IUT235
4-12
Component Structure RTP Components “Structure“ of the RTP components corresponds to the Time Groups used
1. On-Off Component On-Peak Component Code In Out – Portion Above 1st Limit (QUANTITY) on-peak
Off-Peak Component Code In Out – Portion Above 1st Limit (QUANTITY) off-peak comp1
Default Component Code
Summer
In 1 – Measured Value (QUANTITY) Historic Consumption
Weekend
Out
on-peak
Component Structure is time sliced for on and off peak periods
off-peak Component
Weekday on-peak
summer/winter
2. Peak Component
off-peak
weekday/weekend
Default Component Code
on peak/off peak
Winter Weekend
In 1 – Measured Value (QUANTITY) Historic Consumption
on-peak
Out – Demand Above Limit (DEMAND) Max. demand
off-peak
Component Structure is NOT time sliced
Weekday on-peak off-peak
SAP AG 2003
Recall that the structure of the RTP Component is determined by the Season, Day and TOU Groups allocted to the RTP Component.
In the above examples: y RTP Component 1 contains TOU periods On and Off y RTP Component 2 contains no time periods
© SAP AG
IUT235
4-13
Component Activation and Prioritization Activation Type: Use and Activate Generally Use and activate generally Use and activate individually Use individually and activate generally
Time General generated in the RTP Interface Individually Activated
Priority: medium
comp1
comp1
comp1
Priority: low
comp2
comp2
Priority: high
comp3
comp3
comp3
comp3
comp3
comp1
comp2
comp3
comp1
comp1
RTP-Component Priority!
RTP Component Execution Activated
Not activated
SAP AG 2003
Individual RTP Components such as a specific agreement for a customer are defined in the Installation.
The RTP Components can be activated in various ways: y Generally y Individually
The activation and prioritization determine which RTP Component will be executed in the RTPInterface.
© SAP AG
IUT235
4-14
Input Parameter Input Parameter
Input Parameter
From-Date: 01.01.00
To-Date: 31.12.9999
From-Time: 00:00:00
To-Time: 11:59:59
Assigned Status
Profile:
Role: Input parameters can be allocated to a role or a profile SAP AG 2003
On the Input Parameter Tab, Input Parameters are the assigned a profile.
Enter the period (From and To Date/Time) in which a profile is allocated to the Input Parameter of the RTP Component. This enables allocation of different profiles to the same parameter (time slicing).
Choose the Profile OR Role to be allocated to the parameter. (Once you have entered this data, insert the information using the Copy function.)
© SAP AG
IUT235
4-15
Historical Profiles for one Input Parameter RTP Interface Formula LIMIT01 RTP Component 1
From-Date: 01/01/2000
To-Date: 01/31/2000
Profile: 101
Input 1: Measured Cons
From-Date: 02/01/2000
To-Date: 02/29/2000
Profile: 320
Input 2
From-Date: 03/01/2000
To-Date: 03/31/2000
Profile: 001
Input 3 Output 1 Output 2 Output 3 Output 4
SAP AG 1999
The above example displays how different profiles can be assigned to one input parameter based on the validity dates of the profile assignment.
© SAP AG
IUT235
4-16
Usage of the Parameter Template RTP Component 1 Parameter Template
Input 1
Installation: EDM_IN_002
Input 2 Input 3 Output 1
Profile 53
Output 2 Output 3 Installation
Output 4
Rate Category
Ind. RTP interface
Log register
Rate type
Rate
PI12
PI22 P_VB
P_FC RTP interface P1
P2
P12
LUMSUM02 RTPAMNT; ONE DEMAND01 BILLABLE KW; PEAK KW
SAP AG 2003
When an RTP Component has the activation type Use and Activate Individually or Use Individually and Activate Generally, it is possible to define Input Parameters as Template Parameters. The advantage of Template Parameters is that they allow the user to define Input Parameters via the installation. This means that profiles or roles can ONLY be allocated to Input Parameters at the installation.
In order to assign the profile to the parameter template, go to the Installation [NES31]. Choose the 'RTP interface' pushbutton. Within this transaction, it is possible to assign the profile to the template parameter. This is typically used for short term agreements such as a SPOT pricing limit.
© SAP AG
IUT235
4-17
Output Parameter
Output Parameter Result Number: The Output Parameters are allocated to the Result Parameters.
Result Number
Result Parameter Description
Output 1
1
Portion Above First Limit
Output 2
2
Portion Below First Limit
Output 3
3
Maximum demand
Output 4
SAP AG 2003
In the Result number field, choose a result parameters that you want to allocate to the output parameter. (Once you have entered this data, insert the information using the Copy function.)
Defined Result Parameters can be found under the Result Parameters tab.
© SAP AG
IUT235
4-18
RTP- Interface Complete RTPRTP- Interface Header Data
Formula: LIMIT01
Interval Length: 60 minutes
Division: Electric
Priority
RTP Component 1
Priority
RTP Component 2
Activation
Input 1
Input 1
Input 2
Input 2
Input 3
Input 3
Ouput Parameters Allocated to Result Parameters
Output 1
Output 1
Output 2
Output 2
Output 3
Output 3
Output 4
Output 4
Result Number
Operand Category
Unit of Measure
Result Function
Result Parameter Description
1
QUANT
kWh
SUM
On-Peak Cons
2
QUANT
kWh
SUM
Off-Peak Cons
3
DEMAND
kW
PEAK
Peak Demand
Activation
Ouput Parameters Allocated to Result Parameters
SAP AG 1999
After these steps below have been performed, the RTP-Interface has been created: y Header y Result Parameters y RTP Component Activation and Prioritization y Input and Output Parameters
© SAP AG
IUT235
4-19
Allocating the RTP Interface to a Rate
Customizing the RTP Interface Steps to Build an RTP Interface Allocating the RTP Interface to a Rate
SAP AG 2003
© SAP AG
IUT235
4-20
Using an RTP- Interface Rate: EDM_01 Permissibility
Register-Based Data
X Interval Meters
RTP- Interface:
Allocate the RTP Interface to the Rate
EDM_01
Rate Facts/ Facts/Operands Operands:
Off Peak Usage
Operand Category:
QUANT
Result Parameter:
2 – Off Peak Consumption
Must match RTP Operand in the RTPInterface
X RTP Operand
Rate Steps Variant
InputOp01
InputOp02
InputOp01
Statistical Rate
001
QUANTI01
ONPEAKUSG
ONPEAKPRICE
ONPEAKAMT
EDM_01
002
QUANTI01
OFFPEAKUSG
OFFPEAKPRICE OFFPEAKAMT
EDM_01
SAP AG 1999
Before the RTP-Interface can be used, it must be allocated to a Rate. This allocation is only possible for rates that have selected the Permitted for Interval Meters option. Within the RTP rate facts, individual rate step input operands can be allocated to Result Parameters of the RTP-Interface. This means that the appropriate operands are provided with Result Parameter values from the RTPInterface during billing.
It is only possible to allocate Result Parameters to operands in the rate facts if the RTP operands have been defined. The Operand Category must also be defined. This is the Operand Category in which the RTP rate values in the RTP rate are to be processed. The Operand Category must match the category of the RTP operand.
© SAP AG
IUT235
4-21
Rate Permissibility for Interval Meters Change Rate Rate: Division: Bill Class: Permissibility
RegisterRegister-based data
Reg. Permiss. Permiss.
Register Operand
Interval Meters
Val. Class
Interval Meters
Min. Port.
Facts Permissible
Ref. value
PE Bill perm. perm.
RTP Interface Installation
Rate Category
Ind. RTP interface
Log. Register
Rate Type
Rate
PI12
PI22 P_VB
P_FC RTP Interface P1
P2
P12
LUMSUM02 RTPAMNT; ONE
DEMAND01 BILLABLE KW; PEAK KW
SAP AG 1999
The permissibility for interval meters is assigned within the Rate.
© SAP AG
IUT235
4-22
Operands Result Parameters Result Number
Operand Category
Unit of Measure
Result Function
Result Parameter Description
1
QUANT
kWh
SUM
On-Peak Cons
2
QUANT
kWh
SUM
Off-Peak Cons
3
DEMAND
kW
PEAK
Peak Demand
Rate Steps RTP interface provides the operand.
Variant
InputOp01
InputOp02
InputOp01
Statistical Rate
001
QUANTI01
ONPEAKUSG
ONPEAKPRICE
ONPEAKAMT
EDM_01
002
QUANTI01
OFFPEAKUSG
OFFPEAKPRICE OFFPEAKAMT
EDM_01
Operands Operand:
Off-Peak Usage
Operand Category:
QUANT
Division
Electric
Normal Usage Register Operand
The RTP operand type must be used.
Complete History RTP Operand
SAP AG 1999
© SAP AG
IUT235
4-23
Rate Facts Display Rate: EDM_01 - Facts Symbol for RTP Operands
0002
+
DEMANPRS
Demand Price
+
OFFPEAKUSG
Off Peak Usage
-
ONPEAKUSG
On Peak Usage Off-Peak Consumption
+
PEAK
Maximum Demand
Display Operand Value Operand:
OFFPEAKUSG
Season: The operand will be a result number of the RTP-Interface; operand type and unit of measurement must be the same.
Unit of Measure:
kWh
kWh
Valid From:
Valid To:
Result:
Description:
01.01.2000
31.12.9999
2
Off-Peak Cons
..
..
..
..
SAP AG 1999
Within the Rate Facts, the Operands coming from the RTP-Interface are indicated with the RTP Operand Symbol.
The Operands are tied to a Result Parameter Number from the RTP-Interface
© SAP AG
IUT235
4-24
Exercises Unit: Customizing settings for the RTP interface Topic: Execute RTP interface EDM_02 At the conclusion of these exercises, you will be able to • Describe the elements of the EDM_02 RTP interface • Execute the EDM_02 RTP interface for your business partner, using a billing simulation • Describe the functions of the EDM_02 RTP interface • Execute the EDM_02 RTP interface with an individual spot agreement First a customer with an interval meter must be billed for on-peak consumption, off-peak consumption below a value limit (25kWh) and consumption above the limit, which is valuated with a price for each interval above the limit. Then during the billing period, an individual spot agreement must be activated, where an individual quantity limit (50 kWh) is allocated to the customer at installation level. The determined quantity above the limit must be billed, based on the individually allocated limit value. The onpeak and off-peak rate consumption below the limit must also be billed. 1-1
Familiarize yourself with the EDM_02 RTP interface. In Customizing for SAP Utilities, choose Energy Data Management → Interface to RTP Billing → Define RTP Interface → Display RTP Interface. 1-1-1
Enter the RTP interface. _____________________________________________________
1-1-2
Which formula is allocated to the RTP interface? _____________________________________________________
1-1-3
How many input and output parameters are defined in the formula LIMIT02? _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-25
1-2
Display the result parameter of the RTP interface. 1-2-1
How may result parameters are defined in RTP-Interface EDM_02? _____________________________________________________ _____________________________________________________
1-3
Display the RTP components for the RTP interface. 1-3-1
How many components make up the RTP interface EDM_02? List the RTP components: _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________
1-3-2
Which RTP component in the EDM_02 RTP interface has the highest priority? _____________________________________________________ _____________________________________________________
1-4
Allocate rate category EDM_02 to the installation. In the Utilities Industry menu, choose Technical Master Data → Installation → Change. 1-4-1
Enter the ID of your installation (TR0101A0##). _____________________________________________________ _____________________________________________________
1-4-2
Change the rate category from EDM_01 to EDM_02. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-26
1-5
Run a billing simulation with RTP interface EDM_02. In the SAP menu, choose Utilities Industry → Billing → Billing Execution → Individual Processing → Billing Analysis. 1-5-1
Run an individual simulation (billing analysis) for your installation for the period from January 1, YYYY to January 31, YYYY. _____________________________________________________ _____________________________________________________
1-5-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
1-5-3
Display the document and note the billing document number: Billing document number:
1-5-4
___________________
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Result Parameter
Net amount
Billing quantity
Quantity multiplied with spot price Amount: Spot price * consumption above baseline On-peak consumption below baseline Off-peak consumption below baseline 1-5-5
Run an RTP analysis for the billing simulation. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-27
1-5-6
What value does the second input parameter have on the Input parameters tab page? This value is the limit quantity. _____________________________________________________ _____________________________________________________
1-5-7
How many result parameters were determined in the simulation? List the values for the individual determined result parameters. _____________________________________________________ _____________________________________________________
1-6
Run an invoicing simulation for the bill period. 1-6-1
Run an invoicing simulation for the billing analysis you just executed. _____________________________________________________ _____________________________________________________
1-6-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
1-6-3
Display the print document and the bill preview. _____________________________________________________ _____________________________________________________
1-7
Activate a temporary spot agreement within the installation. In the Utilities Industry menu, choose Technical Master Data → Installation → Change. 1-7-1
Enter the ID of your installation. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-28
1-7-2
By activating the individual agreement, specify a temporary special agreement in the installation. Activate the agreement from January 13, YYYY. _____________________________________________________ _____________________________________________________
1-7-3
In the individual agreement, allocate the limit value profile (50) from January 1, YYYY in the Allocate Profiles or Roles to Components screen. This is a limit value, and the price of the special agreement applies to any values above this limit value. _____________________________________________________ _____________________________________________________
1-8
Run a billing simulation for the individual agreement. In the SAP menu, choose Utilities Industry → Billing → Billing Execution → Individual Processing → Billing Analysis. 1-8-1
Run an individual simulation (billing analysis) for your installation. Take into account the individual agreement for the period January 1, YYYY to January 31, YYYY. _____________________________________________________ _____________________________________________________
1-8-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
1-8-3
Display the document and note the billing document number: Billing document number:
© SAP AG
___________________
IUT235
4-29
1-8-4
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Result Parameter
Net amount
Billing quantity
Quantity multiplied with spot price Amount: Spot price * consumption above baseline On-peak consumption below baseline Off-peak consumption below baseline 1-8-5
Run an RTP analysis for the billing simulation. _____________________________________________________ _____________________________________________________
1-8-6
© SAP AG
What changed for the RTP calculation, after the component for the billing of an individual consumption limit was activated for the period January 13, YYYY to January 31, YYY? (Check the data on the Parameters tab page).
IUT235
4-30
Exercises Unit: Customizing settings for the RTP interface Topic: Create RTP interface At the conclusion of these exercises, you will be able to • Define season types and season groups • Define and generate RTP components • Create RTP interfaces • Create billing-relevant data for an RTP rate • Execute your RTP interface A new RTP interface must be created for billing off-peak and on-peak rate consumption below the limit, and seasonal consumption above the limit. A season change must be defined for the billing period of January. All billing data that is necessary for the new RTP interface must also be defined.
2-1
Define the season types and season groups. 2-1-1
Define two season types (e.g. with short text SA1_0## and SA2_0##) within the settlement period (01.01.YYYY – 31.01.YYYY) e.g. season 1 from 01.01. to 14.01. and from 01.10. to 31.12.; season 2 from 15.01. to 30.09. Choose the following in the SAP Reference IMG: SAP Utilities→ Energy Data Management → Basic Settings → Season Group → Define Season Types. _____________________________________________________
2-1-2
Define a season group that contains the season types you just created. Choose the following in the SAP Reference IMG: SAP Utilities → Energy Data Management → Basic Settings → Season Group → Define Season Groups. _____________________________________________________
© SAP AG
IUT235
4-31
2-2
Define and generate an RTP component. 2-2-1
Create an RTP component for determining seasonal consumption. (Choose the name RTPKomp_# for example). Choose the following in the SAP Reference IMG: SAP Utilities → Energy Data Management → Interface to RTP Billing → Define RTP Components → Create RTP Components.
2-2-2
Generate the RTP component. _____________________________________________________
2-3
Create an RTP interface with header data, activation of the RTP component and prioritization. 2-3-1
Create the RTP interface (RTPSch_##) and allocate formula LIMIT01 to it. In Customizing for SAP Utilities, choose Energy Data Management → Interface to RTP Billing → Define RTP Interface → Create RTP Interface.
2-3-2
Allocate the RTP component for seasonal consumption and the component for on-peak and off-peak rate consumption to the RTP interface. Activate both RTP components. Prioritize the components, so that the component with the seasonal consumption has highest priority. The components should determine the following: *Consumption in summer and winter Add the created component for seasonal consumption with activation type Use and activate generally. Allocate priority 2 to this component. *On-peak and off-peak rate consumption Add the component for on-peak and off-peak rate consumption with activation type Use and activate generally. Allocate priority 3 to this component.
2-4
Create result parameters in the RTP interface. 2-4-1
Define the following result parameters: - On-peak rate consumption Off-peak rate consumption - Consumption for season 1 (above limit) Consumption for season 2 (above limit) ___________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-32
2-5
Create input parameters in the RTP interface. 2-5-1
Allocate the input parameters for measured consumption and value limit profile. _____________________________________________________ _____________________________________________________
2-6
Create output parameters in the RTP interface. 2-6-1
Allocate the following output parameters: - On-peak rate consumption - Consumption for season 1 (above limit)
Off-peak rate consumption Consumption for season 2 (above limit) ___________________________________________________ _____________________________________________________ 2-7
Create rate EDM_0## for your RTP interface. 2-7-1
Define the RTP rate EDM_0##. Use rate EDM_01 as a template. _____________________________________________________ _____________________________________________________
2-7-2
Change the rate steps and create seasonal operands here (see below). Delete the rate steps that you do not require. _____________________________________________________ _____________________________________________________ The following four operands should be created for the seasonal consumption and prices: * Season 1 Consumption above limit * Season 2 Consumption above limit * Season 1 Price above limit * Season 2 price above limit ___________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-33
Which of these operands are defined as RTP operands, and why? _____________________________________________________ _____________________________________________________ 2-8
Allocate the operands in the rate facts. 2-8-1
Change the rate facts to allocate the price operands for season 1. You must create a price for season 1. _____________________________________________________ _____________________________________________________
2-8-2
Change the rate facts to allocate the price operands for season 2. You must create a price for season 2. _____________________________________________________ _____________________________________________________
2-8-3
Change the rate facts to allocate a result parameter to the operand for on-peak consumption. _____________________________________________________ _____________________________________________________
2-8-4
Change the rate facts to allocate a result parameter to the operand for off-peak rate consumption. _____________________________________________________ _____________________________________________________
2-8-5
Change the rate facts to allocate a result parameter to the consumption operand for season 1. _____________________________________________________ _____________________________________________________
2-8-6
Change the rate facts to allocate a result parameter to the consumption operand for season 2. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-34
2-9
Create billing schema EDM_0##. 2-9-1
Define the billing schema EDM_0##,using EDM_01 as a template. You must also define how the bill lines are presorted. _____________________________________________________ _____________________________________________________
2-10
Create rate category EDM_0##. 2-10-1
Define rate category EDM_0##,using EDM_01 as a template. _____________________________________________________ _____________________________________________________
2-11
Create a rate determination. 2-11-1
2-12
Define a rate determination for rate category EDM_0##.
Allocate rate category EDM_0## to installation TR0101A0##. 2-12-1
Enter the ID of your installation, to change the rate category in EDM_0##. _____________________________________________________ _____________________________________________________
2-12-2
Change the rate category from EDM_01 to EDM_0##. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-35
2-13
Perform a billing simulation with installation TR0101A0##. 2-13-1
Run an individual simulation (billing analysis) for your installation for the period from January 1, YYYY to January 31, YYYY. _____________________________________________________ _____________________________________________________
2-13-2
Ensure that the simulation was successful. _____________________________________________________ _____________________________________________________
2-13-3
Display the document and note the billing document number: Billing document number:
2-13-4
______________________________
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. (The net amount can vary depending on the created price. The quantities must be identical). Result Parameter
Net amount
Billing quantity
Consumption for season 1 Consumption for season 2 On-peak rate consumption Off-peak rate consumption 2-13-5
Run an RTP analysis for the billing simulation. Check the results. _____________________________________________________ _____________________________________________________
© SAP AG
IUT235
4-36
Solutions Unit: Customizing settings for the RTP interface Topic: Execute RTP interface EDM_02
1-1
Familiarize yourself with the EDM_02 RTP interface. In Customizing for SAP Utilities, choose Energy Data Management → Interface to RTP Billing → Define RTP Interface → Display RTP Interface. 1-1-1
1-1-2
Enter the RTP interface. Field name or data category
Values
RTP interface
EDM_02
Which formula is allocated to the RTP interface? In the Hdr data tab page, look for the entry in the Formula field. Field name or data category
Values
Formula
LIMIT02
1-1-3 How many input and output parameters are defined in the formula LIMIT02? On the left-hand side of the screen, search for the input and output parameters for each component. 3 Input Parameters, 3 Output Parameters
© SAP AG
Field name or data category
Values
Input parameter 1
Measured consumption QUANTITY
Input parameter 2
Limit QUANTITY
Input parameter 3
Price PRICE
Output parameter 1
Consumption above limit QUANTITY
Output parameter 2
Consumption below limit QUANTITY
Output parameter 3
Amount above limit AMOUNT
IUT235
4-37
1-2
Display the result parameter of the RTP interface.
1-2-1 How may result parameters are defined in RTP-Interface EDM_02? Choose the Result parameters tab page. Four result parameters are defined.
1-3
Field name or data category
Values
Result parameter 1
On-peak consumption below baseline
Result parameter 2
Off-peak consumption below baseline
Result parameter 3
Amount: Spot price * consumption above baseline
Result parameter 4
Quantity multiplied with spot price
Display the RTP components for the RTP interface. 1-3-1
1-3-2
How many components make up the RTP interface EDM_02? List the RTP components: Search for the components on the left hand side of the screen (symbol with 3 documents). Three components are defined. Field name or data category
Values
Component 1
0007Æ Billing of individual agreement
Component 2
0006Æ Billing of spot agreement
Component 3
0001Æ Billing of on- and offpeak rates
Which RTP component in the EDM_02 RTP interface has the highest priority? Double-click on each RTP component on the left side of the screen. You can find the entries on right-hand side of the screen on the RTP component tab page in the Priority field. OR Search for the RTP components on the left-hand side of the screen. The priority is to the right of the name of the RTP component. 0007Æ Billing of individual agreement
© SAP AG
IUT235
4-38
1-4
Allocate rate category EDM_02 to the installation. In the Utilities Industry menu, choose Technical Master Data → Installation → Change. 1-4-1
Enter the ID of your installation. Field name or data category
Values
Installation
TR0101A0##
Choose Enter. 1-4-2
1-5
Change rate category EDM_01 to EDM_02. Change the rate category in EDM_02 in the Time-dependent data group frame.
Run a billing simulation with RTP interface EDM_02. In the SAP menu, choose Utilities Industry → Billing → Billing Execution -> Individual Processing → Billing Analysis. 1-5-1
Run an individual simulation (billing analysis) for your installation for the period from January 1, YYYY to January 31, YYYY. Enter the following data in the initial screen for automatic billing and simulation: Select the simulation in the Billing types group frame. Field name or data category
Values
Simulation period
01.01.YYYY - 31.01.YYYY
Select the Installation in the Selection criteria group frame. Field name or data category
Values
Installation
TR0101A0##
Select Bill/simulate (F8). 1-5-2
© SAP AG
Ensure that the simulation was successful. Check that the following message is displayed at the bottom, left hand side of the screen: Simulation of installation TR0101A0## was carried out successfully.
IUT235
4-39
1-5-3
Display the document and note the billing document number: Billing document number: ___________________ Select Display document. Choose Enter.
1-5-4
Note the determined net amount and the billing quantity (see Document overview tab page) for the individual result parameters. Choose the Doc. overview tab page. Result Parameter
Net amount
Quantity multiplied with spot price
1-5-5
-------
Billing quantity 5937,16
Amount: Spot price * consumption above baseline
1187,43
00000
On-peak consumption below baseline
1222,25
20370,76
Off-peak consumption below baseline
658,16
21938,66
Run an RTP analysis for the billing simulation. Choose the RTP analys. tab page. Choose Start analysis.
1-5-6
What value does the second input parameter have on the Input parameters tab page? This value is the limit quantity. Choose the Input parameters tab page. Select the second input parameter in the Input Parameter Formula group frame. Look at the profile values in the Profile value field.
© SAP AG
Field name or data category
Values
Quantity limit
25 kWh
IUT235
4-40
1-5-7
How many result parameters were determined in the simulation? List the values for the individual determined result parameters. Choose the Overview tab page on the Result parameters tab page. Æ 4 result parameters were determined:
1-6
Field name or data category
Values
On-peak consumption below baseline
20370,76
Off-peak consumption below baseline
21938,66
Amount: Spot price * consumption above baseline
1187,432
Quantity multiplied with spot price
5937,16
Run an invoicing simulation for the bill period. 1-6-1
Run an invoicing simulation for the billing analysis you just executed. Choose Invoicing simulation on the initial screen for automatic billing and simulation. Ensure that the number of the billing document is correct. Choose Enter.
1-6-2
Ensure that the simulation was successful. Check that the following message appears at the bottom left hand side of the screen: Invoicing completed.
1-6-3
Display the print document. Choose Display print document on the initial screen for automatic billing and simulation. Choose Enter. Display the bill preview. Choose Bill preview on the Display Print Document screen.
© SAP AG
IUT235
4-41
1-7
Activate a temporary spot agreement within the installation. In the Utilities Industry menu, choose Technical Master Data ### Installation ### Change. 1-7-1
Enter the ID of your installation. Field name or data category
Values
Installation
TR0101A0##
Choose Enter. 1-7-2
By activating the individual agreement, specify a temporary special agreement in the installation. Activate the agreement from January 13, YYYY. Choose RTP interface in the Change Installation screen. Expand the data objects below the Installation (top left on screen). Expand the data objects and double-click on the component (0007). Choose the Component tab page. Select the Activate field. Enter the date January 13, YYYY in the From-Date field. Choose Copy to table.
1-7-3
In the individual agreement, allocate the limit value profile (50) from January 1, YYYY in the Allocate Profiles or Roles to Components screen. This is a limit value, and the price of the special agreement applies to any values above this limit value. Expand the data objects below the Installation (above left on screen) in the Allocate Profiles or Roles to Components screen. Expand the data objects and double-click on input parameter 02. Choose the Parameter tab page. Enter the date January 01, YYYY in the From-Date field. Enter the value limit profile 50 in the Profile field. Choose Copy to table. Go back. Save your data in the Change Installation screen.
© SAP AG
IUT235
4-42
1-8
Run a billing simulation for the individual agreement. Choose Utilities Industry → Billing → Billing Execution → Individual Processing → Billing Analysis. 1-8-1
Run an individual simulation (billing analysis) for your installation. Take into account the individual agreement for the period January 1, YYYY to January 31, YYYY.
1-8-2
Ensure that the simulation was successful. Check that the following message is displayed at the bottom, left hand side of the screen: Simulation of installation TR0101A0## was carried out successfully.
1-8-3
Display the document and note the billing document number: Billing document number: Select Display document. Choose Enter.
1-8-4
Note the determined net amount and the billing quantity (see Doc. overview tab page) for the individual result parameters. Result Parameter Quantity multiplied with spot price
1-8-5
___________________
Net amount -------
Billing quantity 455,58
Amount: Spot price * consumption above baseline
91,12
00000
On-peak consumption below baseline
1445,22
24086,98
Off-peak consumption below baseline
711,12
23704,02
Run an RTP analysis for the billing simulation. Choose the RTP analys. tab page. Choose Start analysis.
© SAP AG
IUT235
4-43
1-8-6 What changed for the RTP calculation, after the component for the billing of an individual consumption limit was activated for the period January 13, YYYY to January 31, YYY? (Check the data on the Parameters tab page). Æ The component for billing an individual consumption limit was activated from January 13, YYYY with a quantity limit of 50 kWh. The original quantity limit of 25kWh for the first part of the billing period (January 1, YYYY to January 12, YYYY) and the quantity limit 50kWh for the second part of the billing period (January 13, YYYY to January 31, YYYY) were used.
© SAP AG
Field name or data category
Values
Limit quantity 01.01.YYYY 12.01.YYYY
25 kWh
Limit quantity 13.01.YYYY 31.01.YYYY
50 kWh
IUT235
4-44
Solutions Unit 4: Customizing settings for the RTP interface Topic: Create RTP interface
2-1
Define the season types and season groups. 2-1-1
Define two season types within billing period # (January 1, YYYY to January 31, YYYY). Choose the following in the SAP Reference IMG: SAP Utilities→ Energy Data Management → Basic Settings → Season Group → Define Season Types. Choose New entries. Define season type 1 with short description SA1_0##, where ## is your group number. Select the lines in the Season type group frame and double-click on the Definition folder. Choose New entries. Enter data for the first season type. Field name or data category
Values
Consecutive number
1
Start
01.01
End
14.01
Consecutive number
2
Start
01.10
End
31.12
Save your data. Go back and display the next season type. Define season type 2 with short description SA2_0##, where ## is your group number. Select the lines in the Season type group frame and double-click on the Definition folder. Choose New entries. Enter the following data for the second season type. Field name or data category
Values
Consecutive number
1
Start
15.01
End
30.09
Save your data. © SAP AG
IUT235
4-45
2-1-2
Define a season group that contains the season types you just created. Choose the following in the SAP Reference IMG: SAP Utilities → Energy Data Management → Basic Settings → Season Group → Define Season Groups. Choose New Entries. Define a season group with short description SB_0##, where ## is your group number. Select the lines in the Season Group group frame and double-click on the Definition folder. Choose New entries. Enter data for the first season type. Field name or data category
Values
Consecutive number
1
Season type
First season type you created
Consecutive number
2
Season type
Second season type you created
Save your data. 2-2
Define and generate an RTP component. 2-2-1
Create an RTP component for determining seasonal consumption. In Customizing for SAP Utilities, choose Energy Data Management → Interface to RTP Billing → Define RTP Component → Create RTP Component. Enter a reference number (RTPComp_##) in the RTP component field. Choose Enter. Enter a description. Choose a block group and block group category. Field name or data category
Values
Block category
Season group
Block
Season group that you created
Choose Transfer. Save. 2-2-2
© SAP AG
Generate the RTP component. Generate the component code. Answer Yes when asked if you wish to continue.
IUT235
4-46
2-3
Create an RTP interface with header data, activation of the RTP component and prioritization. 2-3-1
Create the RTP interface and allocate formula LIMIT01 to it. Go to Customizing for SAP Utilities and choose Energy Data Management → Interface to RTP Billing → Define RTP Interface → Display RTP Interface. Enter a reference number (RTPInt_##) in the RTP interface field. Choose Enter. Enter a description. Enter the header data.
2-3-2
Field name or data category
Values
Formula
LIMIT01
Interval length defined
15 minutes
Division
Electricity
Allocate the RTP component for seasonal consumption and the component for on-peak and off-peak rate consumption to the RTP interface. Activate both RTP components. Prioritize the components, so that the component with the seasonal consumption has highest priority. The components should determine the following: * Consumption in summer and winter Add the created component for seasonal consumption with activation type Use and activate generally. Allocate priority 2 to this component. ÆChoose the RTP component tab page. Enter your component in the RTP component field. Enter the following data: Field name or data category
Values
Activation Type
Use and activate generally
Priority
2
To activate the components, choose Insert component. In the Activation tab page, enter the following: Field name or data category
Values
Valid from
01.01.YYYY
Choose Transfer.
© SAP AG
IUT235
4-47
*On-peak and off-peak rate consumption Add the component for on-peak and off-peak rate consumption with activation type Use and activate generally. Allocate priority 3 to this component. Enter component 0001 in the RTP component field. Enter the following data: Field name or data category
Values
Activation Type
Use and activate generally
Priority
3
To activate the components, choose Insert component. In the Activation tab page, enter the following: Field name or data category
Values
Valid from
01.01.YYYY
Choose Transfer. 2-4
Create an RTP interface – Result parameters. 2-4-1
Define the following result parameters: - On-peak rate consumption Off-peak rate consumption - Consumption for season 1 (above limit) Consumption for season 2 (above limit) Switch to the Result parameters tab page. Enter the following data:
Res.No.
Result Parameter Desc
Operand category
UoM
Result function
1
On-peak rate consumption
QUANT
kWh
UM
2
Off-peak rate consumption
QUANT
kWh
SUM
3
Consumption for season 1
QUANT
kWh
SUM
4
Consumption for season 2
QUANT
kWh
SUM
Choose Transfer.
© SAP AG
IUT235
4-48
2-5
Create an RTP interface – Input parameters. 2-5-1
Allocate the input parameters for measured consumption and value limit profile. Go to the RTP component tab page and choose the Input parameters tab page. Double-click on the corresponding input parameter (left-hand side of screen). Enter the following data for the component with seasonal consumption, to allocate Measured Value QUANTITY to the input parameter: Component code
Param. No.
From
Role
Default
1
01.01.YYYY
0001
Choose Transfer. Double-click on the corresponding input parameter (left-hand side of screen). Choose Insert component. Enter the following data for the component with seasonal consumption, to allocate the First Limit Value as a Quantity to the input parameter: Component code
Param. No.
From
Profile
Default
2
01.01.YYYY
25
Choose Transfer. Double-click on the corresponding input parameter (left-hand side of screen). Enter the following data for the component with on-peak and off-peak rate consumption values, to allocate Measured Value QUANTITY to the input parameter: Component code
Param. No.
From
Role
Default
1
01.01.YYYY
0001
Choose Transfer.
© SAP AG
IUT235
4-49
2-6
Create an RTP interface – Output parameters. 2-6-1
Allocate the following output parameters: - On-peak rate consumption Off-peak rate consumption - Consumption for season 1 (above limit) Consumption for season 2 (above limit) Go to the RTP component tab page and choose the Outp. parameters tab page. Double-click on the corresponding output parameter (left-hand side of screen). Enter the following data for the component with on-peak and off-peak rate consumption values, to allocate the Portion Below the First Limit QUANTITY to the output parameter: Component code
Param. No.
Res.No.
Des...
On-peak rate period
1
1
On-peak rate consumption
Seas
Timeof-use type 0001
Choose Transfer. Double-click on the corresponding output parameter (left-hand side of screen). Enter the following data for the component with on-peak and off-peak rate consumption values, to allocate the Portion Below the First Limit QUANTITY to the output parameter: Component code
Param. No.
Res.No.
Des...
Off-peak rate period
1
2
Off-peak consumption
Seas
Timeof-use type 0002
Choose Transfer. Double-click on the corresponding output parameter (left-hand side of screen). Enter the following data for the component with season consumption values, to allocate the Portion Below the First Limit QUANTITY to the output parameter. RTP comp.
Param. No.
Res.No.
Des...
Seas
Season (002)
2
3
Consumption for season 1
Seas 1
Timeof-use type
Choose Transfer.
© SAP AG
IUT235
4-50
Double-click on the corresponding output parameter (left-hand side of screen). Enter the following data for the component with season consumption values, to allocate the Portion Below the First Limit QUANTITY to the output parameter. RTP comp.
Param. No.
Res.No.
Des...
Seas
Season (002)
2
4
Consumption for season 2
Seas 2
Timeof-use type
Choose Transfer. Save. 2-7
Create rate EDM_0## for your RTP interface. 2-7-1
Define the RTP rate EDM_0##. Use rate EDM_01 as a template. Field name or data category
Values
Rate
EDM_0##
Rate description
Electricity rate ## with RTP interface
RTP interface
Your RTP interface
Ensure that the rate is permissible for the interval meter. 2-7-2
Change the rate steps and create seasonal operands here. Delete the rate steps that you do not require. The following four operands should be created for the seasonal consumption and prices: Topic: Create RTP interface Which of these operands are defined as RTP operands, and why? *Season 1 Consumption above limit *Season 2 Consumption above limit These two operands are RTP operands because the consumption values for season 1 and season 2 are transferred by the RTP interface (results parameters). The prices are defined as operands with normal operand usage because they do not originate from the RTP interface. Operand 1 ________________________________________ Operand 2 ________________________________________ Operand 3 ________________________________________ Operand 4 ________________________________________
© SAP AG
IUT235
4-51
Æ Data for Season 1 consumption above the limit Field name or data category
Values
Operand
COL1__0##
Operand cat.
QUANT
Division
Electricity
Operand usage
RTP Operand
Choose Enter. Field name or data category
Values
Text
Season 1 consumption above limit
Unit of measurement
kWh
Weighting key
01
Check your data and save. Data for Season 2 consumption above the limit Field name or data category
Values
Operand
COL2__0##
Operand cat.
QUANT
Division
Electricity
Operand usage
RTP Operand
Choose Enter. Field name or data category
Values
Text
Season 2 consumption above limit
Unit of measurement
kWh
Weighting key
01
Check your data and save.
© SAP AG
IUT235
4-52
Data for Season 1 price above the limit Field name or data category
Values
Operand
PRIOL1_##
Operand cat.
QPRICE
Division
Electricity
Operand usage
Normal usage
Choose Enter. Field name or data category
Values
Text
Season 1 price above limit *
Unit of measurement
kWh
Weighting key
01
Check your data and save. Data for Season 2 price above the limit Field name or data category
Values
Operand
PRIOL2_##
Operand cat.
QPRICE
Division
Electricity
Operand usage
Normal usage
Choose Enter.
Field name or data category
Values
Text
Season 2 price above limit *
Unit of measurement
kWh
Weighting key
01
Check your data and save.
© SAP AG
IUT235
4-53
Season 1 consumption/price Rate step cons. no.
Input operand 1
Input operand 2
1
EQUANT__2## (season 1 consumption)
EQUANT___0
2
EQUANT__2## (season 1 consumption)
EQPRICE_2## (season 1 price)
Season 2 consumption/price Rate step no.
Input operand 1
Input operand 2
1
EQUANT__2## (season 2 consumption)
EQUANT___0
2
EQUANT__2## (season 2 consumption)
EQPRICE_2## (season 2 price)
Check the data. Save.
© SAP AG
IUT235
4-54
2-8
Allocate the operands in the rate facts. 2-8-1
Change the rate facts to allocate the price operands for season 1. You must create a price for season 1. Select Facts. Choose Enter. Click on the price operands for season 1. Valid-from
Valid to
Price
01.01.2000
31.12.9999
EDM_1## (create a new price for season 1)
Choose Transfer. Answer Yes when asked if you want to create a price. Field name or data category
Values
Currency
USD
Price type
0 (normal price)
Choose Enter. Enter the following data in the Create Price screen: Field name or data category
Values
Text
Season 1 price above limit *
Quantity base
1
Price amount
As required
Check your data and save. Choose Copy, to complete the allocation of the price operand to season 1.
© SAP AG
IUT235
4-55
2-8-2
Change the rate facts to allocate the price operands for season 2. You must create a price for season 2. Click on the price operands for season 2. Valid-from
Valid to
Price
01.01.2000
31.12.9999
EDM_2## (new price for season 2)
Choose Enter. Answer Yes when asked if you want to create a price. Field name or data category
Values
Currency
USD
Price type
0 (normal price)
Choose Enter. Enter the following data in the Create Price screen: Field name or data category
Values
Text
Season 1 price above limit *
Quantity base
1
Price amount
As required
Check your data and save. Choose Copy, to complete the allocation of the price operand to season 1. 2-8-3
Change the rate facts to allocate a result parameter to the operand for on-peak consumption. Click on the operand for on-peak rate consumption. Valid-from
Valid to
Result Parameter
01.01.2000
31.12.9999
On-peak rate consumption
Choose Copy, to complete the allocation of the result parameter to the operand for on-peak rate consumption.
© SAP AG
IUT235
4-56
2-8-4
Change the rate facts to allocate a result parameter to the operand for off-peak rate consumption. Click on the operand for off-peak rate consumption. Valid-from
Valid to
Result Parameter
01.01.2000
31.12.9999
Off-peak rate consumption
Choose Copy, to complete the allocation of the result parameter to the operand for off-peak rate consumption. 2-8-5
Change the rate facts to allocate a result parameter to the consumption operand for season 1. Click on the consumption operand for season 1. Valid-from
Valid to
Result Parameter
01.01.2000
31.12.9999
Season 1 consumption
Choose Copy, to complete the allocation of the result parameter to the consumption operand for season 1. 2-8-6
Change the rate facts to allocate a result parameter to the consumption operand for season 2. Click on the consumption operand for season 2. Valid-from
Valid to
Result Parameter
01.01.2000
31.12.9999
Season 2 consumption
Choose Copy, to complete the allocation of the result parameter to the consumption operand for season 2. Save your data.
© SAP AG
IUT235
4-57
2-9
Create billing schema EDM_0##. In the SAP menu choose: Utilities Industry → Billing → Master Data → Define Schemas ### Create Schemas. 2-9-1
Define the billing schema EDM_0##,using EDM_01 as a template. You must also define how the bill lines are presorted. Field name or data category
Values
Schema
EDM_0##
Choose Enter. Enter the following data: Field name or data category
Values
Text description
Electricity schema 3 for EDM
Select Schema steps. Choose Insert rate. Field name or data category
Values
Rate
EDM_0##
Choose Execute. Save the schema.
© SAP AG
IUT235
4-58
2-10
Create rate category EDM_0##. In the SAP menu choose: Utilities Industry → Billing → Master Data → Define Rate Categories → Create Rate Categories. 2-10-1
Define rate category EDM_0##,using EDM_01 as a template. Enter the following data for the rate category: Field name or data category
Values
Rate Category
EDM_0##
Division
01
Choose Enter. Enter the following data in the Create Rate Category screen: Field name or data category
Values
Rate category description
Electricity schema 3 for EDM
Billing Schema
EDM_0##
Save your data. 2-11
Create a rate determination. In the SAP menu choose: Utilities Industry → Billing → Master Data → Define Rate Determination. 2-11-1
Define a rate determination for rate category EDM_0##. Enter the following data for the rate determination: Field name or data category
Values
Rate type
1008 (rate type for interval meter)
Rate Category
EDM_0##
Choose Create rate determination.
© SAP AG
IUT235
4-59
Choose Insert period. Field name or data category
Values
Valid-from
01.01.2000
Valid to
31.12.9999
Rate
EDM_0##
Choose Transfer/Enter. Save your data. 2-12
Allocate rate category EDM_## to the installation. In the Utilities Industry menu, choose Technical Master Data → Installation → Change. 2-12-1
Enter the ID of your installation, to change the rate category in EDM_0##. Field name or data category
Values
Installation
TR0101A0##
Choose Enter. 2-12-2
Change the rate category from EDM_01 to EDM_0##. Change the rate category to EDM_0## in the Time-dependent data group frame. Save your data in the Change Installation screen.
2-13
Perform a billing simulation. In the SAP menu, choose Utilities Industry → Billing → Billing Execution → Individual Processing → Billing Analysis. 2-13-1
Run an individual simulation (billing analysis) for your installation for the period from January 1, YYYY to January 31, YYYY. Enter the following data on the initial screen for automatic billing and simulation: Select Simulation in the billing types group frame.
© SAP AG
Field name or data category
Values
Simulation period
01.01.YYYY - 31.01.YYYY
IUT235
4-60
Select the Installation in the Selection criteria group frame. Field name or data category
Values
Installation
TR0101A0##
Select Bill/simulate (F8). 2-13-2
Ensure that the simulation was successful. Check that the following message is displayed at the bottom, left hand side of the screen: Simulation of installation TR0101A0## was carried out successfully.
2-13-3
Display the document and note the billing document number: Billing document number: Select Display document. Choose Enter.
2-13-4
___________________
Note the determined net amount and the billing quantity (see Doc. overview tab page) for the individual result parameters. (The net amount can vary depending on the created price. The quantities must be identical). Choose the Doc. overview tab page. Note that the net amounts vary due to the prices used. The amounts below are based on the price 0.35 for season 1 and 0.6 for season 2.
2-13-5
Result Parameter
Net amount
Billing quantity
Consumption for season 1
606,69
1733,4
Consumption for season 2
2522,26
4203,76
On-peak rate consumption
1222,25
20370,76
Off-peak rate consumption
658,16
21938,66
Run an RTP analysis for the billing simulation. Check the results. Choose the RTP analys. tab page. Choose Start analysis.
© SAP AG
IUT235
4-61
Exercises - Use of the RTP Interface
Exercise 1: RTP Interface EDM_01 Exercise 2: RTP Interface EDM_02 Exercise 3: Build an RTP Interface Exercise 4: Build RTP Interface with an Indiv. Agreement
SAP AG 2003
© SAP AG
IUT235
5-1
Exercise 1: RTP Interface EDM_01
Exercise 1: RTP Interface EDM_01 Exercise 2: RTP Interface EDM_02 Exercise 3: Build an RTP Interface Exercise 4: Build RTP Interface with an Indiv. Agreement
SAP AG 2003
In this exercise, RTP interface EDM_01 will be used to determine the following values for billing from a profile of measured consumption (15 minute intervals): y SPOT amount below a Limit y SPOT amount above a Limit y On-peak rate consumption y Off-peak rate consumption y Maximum demand
Exercises y 1-1 Execute RTP interface EDM_01 y 1-2 Execute RTP interface EDM_01 with a temporary special agreement
© SAP AG
IUT235
5-2
Formula LIMIT01
I01 Measured load profile: Quantity
RED: Input BLUE: Output
O03 Above baseline 2: Quantity I03 Baseline 2: Quantity O04 Above baseline 1: Demand O02 Above baseline 1: Quantity I02 Baseline 1: Quantity
O01 Below baseline 1: Quantity
SAP AG 1999
Formula LIMIT01 determines the values above and below a demand limit. This formula is used to cut individual subareas out of a load shape dependent on two limits. y Description of input parameters: - Load shape (quantity): Load shape, out of which the sub-areas must be cut. - Limit 1 (quantity): Lower limit area. If no entry is made for this parameter the limit is set to zero. - Limit 2 (quantity): Upper limit area. If there is no entry for this parameter, the limit is the same as limit 1. y Description of output parameters: - Quantity up to limit 1 (quantity): The profile contains the portion of the load shape up to limit 1. - Quantity above limit 1 (quantity): The profile contains the portion of the load shape that is above limit 1. This portion is independent of limit 2. This means this is the entire portion above limit 1 including the portion above limit 2. - Quantity above limit 2 (quantity): The profile contains the portion of the load shape that is above limit 2. - Demand over limit 1 (demand): The profile contains the portion of the load shape above limit 1 that is converted into demand values.
Prerequisite: Baseline 2 ³ Baseline 1
© SAP AG
IUT235
5-3
RTP Interface EDM_01 Maximum demand determined from component 2 - 0005
p
SPOT Above
Off-peak consumption determined by component 3 - 0001
On-peak consumption determined by component 3-ON-OFF
SPOT Below
tm
On-peak consumption Off-peak determined by component consumption 3-ON-OFF determined from component 3 - 0001
tn
t
SPOT Agreement Period (temporary) Component 1 - 0006 SAP AG 1999
The following RTP components are defined in RTP interface EDM_01: y RTP component 1 SPOT: Determines SPOT consumption above and below a baseline and the maximum demand for the agreement. - Activation: Use and activate individually - Priority: 1 y RTP component 2 PEAK: Determines peak demand for the entire time period and is not dependent on any day, TOU or season group. - Activation: Use and activate generally - Priority: 2 y RTP Component 3 ON-OFF: Deterimes the on- and off-peak consumption based on a time-of-use group. - Activation: Use and activate generally - Priority: 3
© SAP AG
IUT235
5-4
Exercise 2: RTP Interface EDM_02
Exercise 1: RTP Interface EDM_01 Exercise 2: RTP Interface EDM_02 Exercise 3: Build an RTP Interface Exercise 4: Build RTP Interface with an Indiv. Agreement
SAP AG 2003
In this exercise, RTP interface EDM_02 will be used to determine the following values for billing from a profile of measured consumption (15 minute intervals): y On- and Off-Peak Consumption below the border y Multiplication of the SPOT price with usage above the border y Amount used for multiplication with SPOT price
Exercises y 1-1 Execute RTP interface EDM_02 y 1-2 Execute RT interface EDM_02 with a temporary special agreement
© SAP AG
IUT235
5-5
Formula LIMIT02 RED: Input BLUE: Output
I01: Measured Load Profile (Quantity)
O02: Quantity above limit 1
I02: Limit 1 (Quantity) O01: Quantity below limit 1 (Quantity)
USD
X
Amount above baseline 1
=
O03: Amount from Valuation Quantity with Price
SAP AG 2003
Formula LIMIT02 determines the value below/above a limit and spot price. This formula is used to divide up a load shape based on a limit and to perform an evalution with a price profile. y Description of input parameters: - I01: Load shape (quantity): Load shape that is to be divided up. - I02: Limit (quantity): Limit from when the evaluation with the price profile is performed. If no entry is made for this parameter the limit is set to zero. - I03: Price profile (price): Price with which the consumption above the limit is valuated. y Description of output parameters: - O01: Quantity up to limit (quantity): The profile contains the portion of the load shape up to the limit. - O02: Quantity above the limit (quantity): The profile contains the portion of the load shape above the limit. - O03: Amount from the valuation with price profile (amount): For each interval, the profile contains the amount that results from the valuation of the portion above the limit, with the price of the interval.
© SAP AG
IUT235
5-6
RTP Interface EDM_02
Quantity above
X
USD
=
Amount determined from Comp. 2 - 0006
p
SPOT usage above limit
Off-peak consumption
SAP AG 2003
On-peak consumption
Off-peak consumption
On-peak consumption
tn tm Period for SPOT agreement (limited)
Off-peak consumption
t
The following RTP Components are defined in RTP interface EDM_02 y RTP Component 1: Determines individual consumption limit - Activation: Use and activate individually - Priority: 1 y RTP Component 2 - 0006: Determines SPOT usage above and below the limit and the amount above the limit - Activation: Use and activate generally - Priority: 2 y RTP Component 3 - 0001: Determines the on- and off-peak consumption based on a time-of-use group. - Activation: Use and activate generally - Priority: 3
© SAP AG
IUT235
5-7
Exercise 3: Build an RTP Interface
Exercise 1: RTP Interface EDM_01 Exercise 2: RTP Interface EDM_02 Exercise 3: Build an RTP Interface Exercise 4: Build RTP Interface with an Indiv. Agreement
SAP AG 2003
In this exercise, you will build an interface to calculate: y On-peak rate consumption y Off-peak rate consumption y Usage for Season 1 above the limit y Usage for Season 2 above the limit
Exercises y 1-1 Create an RTP interface
© SAP AG
IUT235
5-8
Hints and Tips for Exercise 3
p
Season 1
Season 2
Limit for the seasonal values
Off-peak consumption determined by component 3 - 0001
On-peak consumption determined by component 3-ON-OFF
Off-peak consumption determined by component 3 - 0001
On-peak consumption Off-peak determined by component consumption 3-ON-OFF determined by component 3 - 0001
t
SAP AG 1999
Limit for seasonal valuation
On-peak period
Off-peak period
© SAP AG
IUT235
5-9
Exercise 4: Build RTP Interface with an Indiv. Agreement
Exercise 1: RTP Interface EDM_01 Exercise 2: RTP Interface EDM_02 Exercise 3: Build an RTP Interface Exercise 4: Build RTP Interface with an Indiv. Agreement
SAP AG 2003
In this exercise, you will build an interface to calculate: y On-peak rate consumption y Off-peak rate consumption y Usage for Season 1 above the limit y Usage for Season 2 above the limit y Maximum demand for the individual agreement above the limit y Usage for the individual agreement above the limit
Exercises y 1-1 Create an RTP interface with an individual agreement
© SAP AG
IUT235
5-10
Hints and Tips for Exercise 4 Maximum demand determined from component 2 - 0005
p
Season 1
Season 2
Limits for maximum demand
Limits for seasonal values
Off-peak consumption determined by component 3 - 0001
On-peak consumption determined by component 3 - 0001
Off-peak consumption determined by component 3 - 0001
On-peak consumption determined by component 3 - 0001
tm
tn Only the highest demand is billed for this period
Off-peak consumption determined by component 3 - 0001
t
SAP AG 1999
Maximum demand
Limit for seasonal valuation
Only the highest demand will be billed for the period (customer-specific)
© SAP AG
IUT235
5-11
View more...
Comments
