RTP BILLING

Real Time Price Billing (RTP) is Billing of Interval related data i.e. profiles. Consumption is
measured in each interval in each rate.

RTP COMPONENT

RTP components define the structure of parameter allocations in the RTP Interface. This
structure links the input, output and result parameters. You require different parameters
because parameter allocations require different period patterns (such as summer and winter).
You can allocate different periods (such as season, day and TOU groups) to an RTP interface.
The components allow you to model billing for different parts of a profile in the RTP interface
(for example, a separate component for on- and off-peak periods and a component that
determines the maximum demand for the entire period.)

The RTP components must be generated before they can be used in an RTP interface.

Example

You want to define the RTP component 01 with separate billing for summer and winter periods.

In the summer period, you want to bill based on week days and weekends. On the weekends
you want to bill using peak and off-peak rates.

In the winter period, you want to bill using peak and off-peak rates only.

To do this structure the RTP component as follows: RTP_KPOMP01

> Summer

>Weekd\y

>Weeked
> Peak
> Off-peak
> Winter
> Peak
> Off-peak

Allocate the individual blocks as follows:

1. Allocate the Component node category to the SOWI season block.

RTP_Komp01
> Summer
 > Winter
2. Allocate the WOTAGENDE day block to the Season Block node category and the
Summer node.
RTP_Komp01

> Summer
> Weekday
> Weekday
> Winter
3. Allocate the HTNT day block to the Day Block node category and the Weekend node.
RTP_Komp01

> Summer

> Weekday

> Weekend
> Peak
> Off-Peak
> Winter

Menu SPROIMGSAP UtilitiesEnergy Data ManagementInterface to RTP

Path BillingDefine RTP Component.

T-Code EEDM_CMP01 – Create, EEDM_CMP02 – Change, EEDM_CMP03 – Display

In order to define RTP Component, Click on the execute button for Define RTP
Component. The following overview screen will display.
Select the Create RTP Component and double click it on it. Following over view screen will
display. Maintain the RTP Component there.
After Maintain the RTP Component, RTPKOMP01, Press the enter key. Following over view
screen will display.

Enter the RTP Component Details. Select the Block Category. There are 3 Block Category. They
are Season group, Day Group and Time-of-group. Here Select the Block Category as Day
Group. Using Block Category and Block we can divide the consumption according to different
blocks.

Here we r selecting the Block category as Day group and Block will be ZWEEK.
After selecting Block Category and Block click on COPY button . Once you click
the Copy Button the details will be displayed in the Left Pan under the RTP Component.
Under the RTP Component there are Two Blocks, One is WEEKDAYS WEEKDAYS and the
other one is WEEKENDS WEEKENDS. Select any one the blocks. Double click on it. The Node
category and Nodes will change. Now under this node select the new block category and block.

Click on copy Button . Repeat the same step for the second Nest group.

Now it will looks like a nested group.

Enter and Save. Following message will display. .

After saving the data we have to activate the RTP Component. For activating the RTP

Component click on the activate button . You will get the following message when u r
clicking the Activate Button.
Click on Yes. You will get the following message.

Click on Go back Button and exit the screen.

RTP INTERFACE.

They transfer the values that are managed in the Energie Data Management component (IS-U-
EDM) to the Contract Billing component (IS-U-BI). There are three RTP Interface, they are
Header Data, Result Parameter and RTP Components.

 Header data: The header data contain the formula for calculating the assigned profiles,
the interval length and the division.
 Result parameters: The result parameters come from the result function. Result
parameters are assigned to operand categories and references to the output parameters.
The result parameters supply the operands with data in the RTP rate in IS-U billing.

 RTP components: An RTP interface can contain several components. The components
are sorted by priority. The prioritization is used to determine which component is valid
when several components have the same activation periods. In this case 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 componenents. The input parameters are the assigned profile. The output
parameters come from calculating the formula.

The following activation types exist for the components:

 General (valid for all installations)
 Individual (valid for individual installations)
  Used individually and activated generally

RTP components contain the following assignments:

 Activation
 Input parameters

 Output parameters

 Parameter templates

In short the the RTP components can have several components. The components are sorted
according to priority. This makes it possible to determine which component is to be executed
when several components have the same activation period. The assigned profiles are the input
parameters. The output parameters are obtained from the formula calculation.

Example

An RTP interface named EVU_HTNT determines the following values for billing from a profile
of a measured consumption (15-minute interval):

 On/Off-peak consumption

Time of day type Time interval

On-peak 06:00:00 hours to 21:59:59 hours
Off-peak 22:00:00 hours to 05:59:59 hours
 Maximum demand value

These requirements result in two RTP components:

Comp. Comp. description Prio Activation type

HTNT Calc. on/off-peak consu. 1 General
MAXPOWER Determine max. demand 2 Individual

The profile values from the measured consumption profile are used as input parameters for the
formula for all components.

The output parameters for component HTNT are the consumption as a copy of the
consumption profile (separated by on-peak and off-peak periods), and for component
MAXPOWER the demand as a copy of the demand profile.

The result number can be used to assign the corresponding result functions in the result
parameters.

RTP interface EVU_HTNT can be used in the corresponding RTP rates in billing to bill on/off-
peak consumption and the maximum incurred demand.

Recommendation
For a better overview, you can choose Hide lines to hide all the parameters assigned to the
component that have not yet been allocated.

Choose Show lines to display the parameters again.

Activities

1. Choose Create RTP interface.

2. Enter your data and save.

Menu SPROIMGSAP UtilitiesEnergy Data ManagementInterface to RTP

Path BillingDefine RTP Interface.

T-Code EEDM_RTP01- Create, EEDM_RTP02 - for change, EEDM_RTP03 – For Display

In order to define RTP Interface, Click on the execute button for Define RTP Interface. The
following overview screen will display.
Click on create RTP Interface. Following overview screen will display.
Enter the RTP Interface name and press enter. Following overview screen will display.

Maintain the RTP Interface name. Maintain the From.ProfCalc, Interval Length, Division and
Day Offsets.

 Form. ProfCalc: it is known as Formula for Calculation of Profiles, You use formulas to
perform profile calculations. Formula calculations, in turn, also result in profiles. A fixed
number of input and output parameters is defined for each formula. A profile value
category is defined for each parameter.
  profile value category : Classification of profile values in the system. Profile values are
predefined as Quantity, Demand, Price, Amount, Factor, Other

 Interval Length ID: Intervals between two values in a profile, determined from the
assigned Interval length and interval length category. The interval length is used for
profiles and registers. If an interval length was entered for a register, then no meter
reading documents will be created for the register. The interval length describes the
intervals between the values of a profile.
 Day Offset: it is the starting of the time, like Morning 8 to evening 8 etc.

All these treated as a header data. After maintain all the header data, click on Result Parameter
Tab, and enter the following details.

Result parameter number: Number of a result parameter in the RTP interface.

Unit of measurement: Measuring value for a dimension. Quantity units that have no
dimensions, such as cartons or pallets, are treated in the Utilities Industry (IS-U) component as
units of measurement, but one unit cannot be converted to another unit.

Operand category: Fixed, pre-defined characteristic that is allocated to an operand. Classifies

the operand for the variant programs.

Result function for profile: Defines how profile values in a certain period are analyzed.

The analysis results in a single value. You use result function SUM to calculate the sum of
profile values for a certain period. You use result function PEAK to calculate the maximum
value of a profile during a certain period. You use result function MINIMUM to calculate the
minumum value of a profile during a certain period.

No prorations in result parameter: Means that prorations to RTP operands are not taken into
account when the RTP interface is executed. If you do not select this field, the result function for
the result parameter is only executed once for the total execution period of the RTP interface.
Ex, You use a result parameter in the RTP interface that determines the peak demand from the
load shape of the interval meter. You allocate the result function PEAK to the result parameter.
You have allocated the DEMAND operand to the result parameter in the rate facts. The rate step
for this operand provides the maximum demand value with a price. Billing is carried out for the
period from 01/01/2000 to 01/31/2000. The demand price changes on 01/15/2000. If you do
not select this field: 1. The maximum demand between 01/01/2000 and 01/14/2000 is
calculated and valuated with the demand price for this period. 2. The maximum demand
between 01/15/2000 and 01/31/2000 is calculated and valuated with the de mand price for this
period. If you select this field, the maximum demand is calculated for the entire period from
01/01/2000 to 01/31/2000 and for the sub-periods. The demand is then valuated with the
appropriate demand price for the period.

Consumption Type: Classfies consumption (and demand) according to business criteria. This
classification is derived from how the consumption is billed. Note that the classification is not
identical to the rate based on which the consumption is billed, but is more general. The
consumption type is primarily used in SAP IS-U and SAP CRM integration scenarios. It enables
you to access the consumption data from IS-U when you calculate quotations for existing
customers without using load profiles. To do this, the following criteria must have been met:
You must have maintained the consumption types table. You must have enhanced your rates to
include rate steps with variant program QUANTI22 or QUANTI23. These variants include
additional information in the billing document. In the entry operands for QUANTI22, maintain
an appropriate consumption type. If required, you can also enhance you demand rates to
include steps with variant program DEMAND22 or DEMAND23. Note that if you do this, you
must maintain the consumption type for entry operands that have the DEMAND category. If
you have implemented the SAP IS-U/SAP CRM integration scenario, you can calculate
quotations for customers in the CRM system. To do this, you require estimated consumption for
the quotation period. In the case of existing customers, the consumption can be estimated on the
basis of the meter reading results stored in the IS-U system. The CRM system contains a
function for estimating the consumption does the following: Simulates billing for the utility
installation, Derives the consumption information from the simulated billing document,
Displays the consumption for each consumption type. The estimated data is managed in CRM
as a profile. A separate quotation profile is created for each consumption type. You can use
these quotation profiles in subsequent quotation calculations.

Example, You can use the following value: On-peak consumption, Off-peak consumption,
Active power, Ractive power.

After entering the Result Parameter like Result number, Unit of meas, Res.param.desc, Operand
cat., Result function, Consumptn Type. Press the copy button.

Else you can create the 4 result parameters like the following.
Click on RTP Component, the following tab will display.
RTP component: Defines the structure of parameter allocations in the RTP interface. Example is
you want to allocate parameters in the RTP interface separately according to summer and
winter seasons. To do this, you define an RTP component with a season group the divides the
year into summer and winter.

 You want to allocate parameters separately according to on-peak and off-peak rate
periods.

To do this, you define an RTP component with a time-of-use (TOU) group that divides
day into on-peak and off-peak periods.
 You want to allocate parameters separately according to summer and winter seasons
and according to on- and off-peak rate periods.

To do this, you define an RTP component with a season group that divides the year into
summer and winter and with a TOU group that divides days into on-peak and off-peak
rate periods.

Activation type of RTP component: Defines the activation type of an RTP component for RTP
interface allocation. The following activation types exist:
 Use and activate generally: This allows for definition of input paramater allocations
parameters at the level of the RTP interface. You can also activate the RTP component at
the level of the RTP interface.

 Use and activate individually: Allows for definition of input parameter allocations at
the installation level. You can define corresponding parameter templates at the level of
the RTP interface. You can also allocate output parameters at the level of the RTP
interface. It also is possible to activate the RTP component at the installation level.

 Use individually and activate generally: Allows for definition of input parameter
allocations at the installation level. You can define corresponding parameter templates at
the level of the RTP interface. You can also activate the RTP component at the level of
the RTP interface.

Priority of RTP component: You use this field to define which RTP component and in turn
which parameter allocations are to be used when the RTP interface is executed and the
activation period contains more than one RTP component.

After entering the RTP component, Activation type, Priority click on Insert component
Button.
Enter from and to date, from and to time and click on copy button. After
clicking the copy button the details will be added into the table grid. This time the RTP
Component is added to the RTP Interface. For checking that just expand the tree view of the
RTPINTFC01 in the left pan
Click on the Input parameters tab.