Billing Master Data

Billing Master Data

 SAP AG

© SAP AG 1
Billing Master Data

Billing Master Data

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Billing schema
 Rate category

 SAP AG

© SAP AG 2
Billing Master Data: Unit Objectives

Billing Master Data: Unit Objectives

At the conclusion of this unit, you will be able to

explain:

 The billing master data in the IS-U System

 The dependencies between the individual objects
 The order in which you maintain billing master
data

 SAP AG

© SAP AG 3
Billing/Invoicing: Business Scenario 3

Billing/Invoicing: Business Scenario 3

Budget Billings

Maintain billing Use of rates

in the master Billing Invoicing Bill
master data printout
data

Additional Functions:
Discounts/surcharges
Manual billing
Special billing features
R

 SAP AG

 The scenario in this unit deals with entering billing master data. The master data is then tested in the
billing process.
 As a member of the sales department, you should understand the process of defining billing master
data in the system, for which you will primarily use the implementation guide (IMG).

© SAP AG 4
Billing Master Data: 1

Billing Master Data: 1

 Individual components
 Modeling of the billing logic
 Facts
 Dynamic rate determination

 SAP AG

© SAP AG 5
Business Objects/Utility Services

Business Objects/Utility Services

Business Regional
Partner Structure

Contract
A/R + A/P

Contract
(Utility))
(Utility

Utility Connection
Premise
Installation Object

Device Device
Device Connection
Category Location

Meter
Meter R

Reading

 SAP AG

© SAP AG 6
Universal Billing Engine

Universal Billing Engine

Customer- and Rate Data Procedural Data
Installation-Related Data

Prices and Schema I

Rate Facts E
Contract Rate Var.Prog.Values
Rate 1
X
- Step 1 VarProg. A x1 E
Rate 1 - Step 2 VarProg. B
. .
x2
.
C
Rate 2 U
Installation - Step 1 VarProg. A x3 T
- Step 2 VarProg. C x4
Rate - Step 3 VarProg. D x5 I
Determ. .
.
.
.
.
.
O
Inst. Structure/ Rate n . . . N
. . .
Rate Cat. Facts/ Rate n
Install. Facts - Step 1 VarProg. A xxx

Execution
Quantity Validation Generation
Data Entry of Variant
and Conversion of Billing of Billing
Programs
Analysis and
R

According to Results Line Items

Proration
Schema
 SAP AG

 The rate is the most important billing component. The rate is determined from the rate type and rate
category.
 Every utility installation is allocated a rate category which contains data to control the processing of
meter reading data and billing irrespective of the rate.
 The rate type determines the rate allocation of registers and is therefore generally entered in the
register.

© SAP AG 7
Billing Modules: 1

Billing Modules: 1

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 8
Data Model for Billing

Data Model for Billing

Demands
Demands
Prices...
Prices...
Operands
Operands

Rate
RateCat.
Cat.

Utility
UtilityInstallation
Installation Rate
RateVar.
Var.
Rate
RateDeterm.
Determ. Operand
OperandValues
Values
Prog.
Prog.
Installation
InstallationStructure
Structure

Rate
RateType
Type

Billing
BillingSchema
Schema
Rate 1 Variant Program Operand Values
Step 1 e.g. Quantity x Price 1000 kWh, $0.25
Step 2 Comparison of 2 demands 400 kW, 300 kW
R

Rate n
Step 1

 SAP AG

© SAP AG 9
Company Data Model: Billing

Com pany Data Model: Billing

S AP-Company Data Mo de l
IS -U: Billing Mas te r Data
30106 30107
Billing s che ma Sche ma ste p
H

30104 30105 30108

Utility ra te Utility ra te ste p Opera nd
H A
determination

30109 30110
Va ria nt program Va ria nt program
H A
parame te r

R
30111 30112
Opera nd Opera nd
H R
ca te gory

 SAP AG

© SAP AG 10
Billing Modules: 2

Billing Modules: 2

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 11
Billing Class: 1

Billing Class: 1

 Classifies utility installations within a division;

for example: residential or nonresidential contract
 Change of the billing class is always combined with the
change of the rate category. Final billing is not necessary.
 Can be valid for several utility rate categories
 Establishes the type of billing for several utility installations
 Can be included in several scheduling rules
 Enables you to define several franchise fee groups
 Can be used for determining several meter reading units

 SAP AG

 The billing class is used to run checks between the master data and billing master data. In this way
you can be sure, for example, that a residential customer installation cannot be allocated a
nonresidential contract rate category.
 The billing class can also be use as statistic criteria in sales statistics.

© SAP AG 12
Billing Class: 2

Billing Class: 2

Installation
Rate
Category

Billing Class Portion

Rate

Meter
Rate Type Reading
Unit R

 SAP AG

 The billing class is used in the following entities:

Installation
Rate
Rate category
Rate type
Portion
Meter reading unit
 This enables you to allocate the different billing master data to different billing classes. This means
that each time the billing class is used, a mutual check is carried out for permissibility and
consistency. The check is performed in connection with the division.
 The billing class is optional in the meter reading unit, portion and rate type.

© SAP AG 13
Billing Modules: 3

Billing Modules: 3

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 14
Definition of a Rate Type

Definition of a Rate Type

 The rate type classifies

 registers
 devices
 flat rates
 reference values

for billing.
 In conjunction with the rate category, the rate type is
used for determining the rate.

 SAP AG

 The rate type is usually entered in register. Rate types include on-peak rate active energy, off-peak
rate active energy, on-peak rate reactive energy, off-peak rate reactive energy, gas consumption, water
consumption.
 In exceptional cases, a rate type can also be allocated the following objects:
Device For devices without registers (e.g. audiofrequency ripple control receiver), this rate type
can be used to find a special rate with which a device-dependent rental price is
calculated.

Facts To define a special rate which cannot be derived from registers. Or to determine a rate for
flat-rate installations without built-in devices.

Reference Values
e.g. for modeling of street lights

© SAP AG 15
Rate Type: 1

Rate Type: 1

 Is valid for a particular division (obligatory) and billing class

(optional)
 Use of the rate type can be permitted for:
 Registers
must be specified for registers relevant to billing
 Devices
for example: rental price for devices that do not have
registers relevant to billing
 Rate category facts
for example: flat rates
 Installation facts
for example: flat-rate installations
R

 SAP AG

 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
this way, you specify 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, then you enter the rate type
in the installation facts, but not in the rate category.

© SAP AG 16
Rate Type: 2

Rate Type: 2

Register Device

Rate Type

Rate Category
Installation

 SAP AG

 The rate type is usually maintained at register level. However, in certain cases it can maintained at
device level or in the installation facts. The rate type can also be entered in the rate category.

© SAP AG 17
Billing Modules: 4

Billing Modules: 4

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 18
Prices for Billing

Prices for Billing

Central
Price
Management

Price
Key

Prices

 SAP AG

 The price key serves as the actual name of a price; the price key is also called “price”.
 The actual values are stored in the prices.
 The price key also contains a currency key. This means that if you use different currencies for billing,
then 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 19
Price Categories

Price Categories

 Quantity-based price
for quantities and consumption values
 Flat rate
fixed amounts per unit of time
(consumption flat rates and flat-rate amounts)
 Rental price
charge for supplying the customer with a measuring
device (such as a meter) for a certain period of time
 Time-based price
for example: for demand values and connection loads

 SAP AG

© SAP AG 20
Price Types

Price Types

 Standard price
One price not dependent on a quantity

 Block charge
One or more prices dependent on a quantity

 Scale charge
One price dependent on a quantity

 SAP AG

 The price type specifies how the particular price is to be used.

 In addition to standard single prices, scale and block charges can also be applied.
 The scale price involves graduation (“scaling”) of the price. Certain sequential quantity ranges (for
demand and/or energy) are defined. If one quantity range is exceeded, the price for the next quantity
range applies for the entire quantity. In this way, higher consumption can be cheaper than lower
consumption.
 The block price involves a “blocking” of the price. Certain sequential quantity areas (for demand
and/or energy) are defined for which certain prices apply. This means that different prices are used for
the same quantity. In this way, higher consumption can be prevented from being cheaper than lower
consumption.

© SAP AG 21
Header Data for the Price Key

Header Data for the Price Key

 Transaction currency
 Billing class
 Division
 Rounding parameter
 Price adjustment clause
 External price

 SAP AG

 Several price contributions in different transaction currencies can be entered for one price key. The
relevant transaction currency for billing is entered in the business partner‘s contract account.
 The price key is defined more exactly with the three components:
Price key
Price category
Price level
 The price level is only used for rental prices
 Price adjustment clauses can be defined for all prices. Defining authorization restricts the use of
individual prices.
 Rounding parameters are only needed in the following situations: price discount or using the price
adjustment clause.

© SAP AG 22
Quantity-Based Price

Quantity-Based Price

Quantity-
Based
Price

 SAP AG

 Quantity-based prices are dependent on a quantity that is supplied, for example: energy prices.
 Quantity-based prices have no direct time reference. Exception: the price is a block or scale price. In
this case, for example, you may want the blocks to be adapted to a reduced billing period.
 To define a quantity-based price, base values are required for
- A unit of measurement
- A quantity base. The corresponding calculations are performed in the system using these base
values.
Example: Price per 1 KWh
Price per 1 cbm

© SAP AG 23
Adjusting Price Blocks to Billing Periods

Adjusting Price Blocks to Billing Periods

Quantity-related price

Time basis: 365 days

Price block adjustment activated
Interval lower limit: 350 days
Interval upper limit: 375 days

Adjustment of blocks/scales to
billing period, e.g. 340 days
Price
PriceBlocks
Blocks Price
PriceBlocks
Blocks
00--3000
3000 00--2795
2795
3000
3000--5000
5000 2795
2795--4658
4658
5000
5000--10000
10000 4658
4658--9315
9315
R

10000
10000--9999999999
9999999999 9315 - 9999999999
9315 - 9999999999
 SAP AG

 You can adjust the blocks/scales for quantity-based prices if the billing period differs from the basic
time specified in the price key.
 If you want the blocks/scales to be adjusted, you have to set the Adj.PBlcks indicator (adjust price
blocks). If the adjustment is to be dependent on an interval, you must also set the interval lower and
upper limits.

© SAP AG 24
Time-Based Price

Time-Based Price

Time-Based
Price

 SAP AG

 Time-based prices depend not only on a quantity but also on a time period.
Example: Demand prices
Connection loads
Reference values
 Base values for a time basis and a time category are required in order to define these prices. The
corresponding calculations are performed in the system using these base values.
Example: Price per 1 KW per 12 months
Price per 1 cbm per 365 days

© SAP AG 25
Flat Rate

Flat Rate

Flat Rate

 SAP AG

 Flat rates are levied if values are not measured, for example, if using a meter would be
uneconomical. Flat-rate amounts are time-based prices without quantity reference.
Example: street lighting

© SAP AG 26
Rental Price

Rental Price

Rental
Price

 SAP AG

 The rental price is the charge for supplying the customer with a measuring device (such as a meter)
for a certain period of time.
 The price level is used in the case of rental prices to differentiate prices with the same price class. In
this case, the price key takes on the function of a price class. This means that the permissible values
for the price key are defined in the check table for the price classes; you must maintain these values in
Customizing before you create prices.
 Price classes are allocated to the device category. This price class is transferred into the installation
structure when the device is installed and can be overwritten in exceptional cases.

© SAP AG 27
Price Adjustment Clause

Price Adjustment Clause Company

Company
Bill
Bill xyz

Basic Price
2.00

Addition Multiplication

+ Price x
Adjustment Clause
1.50

Final Price Final Price for Final Price

3.50 the Customer 3.00

 SAP AG

 The price adjustment clause establishes the price adjustment factor by which the base price is
multiplied. You enter the price adjustment clause in the price for quantity- and time-based prices, and
also in the flat rates. If a price adjustment clause is allocated to a price master, then the corresponding
price is changed only indirectly, that is, via the factor. In this way, the same price increase can be
applied to all prices having the same price adjustment clause. This process contains components for
both adding and multiplying.

© SAP AG 28
Billing Master Data: 2

Billing Master Data: 2

 Individual components
 Modeling of the billing logic
 Facts
 Dynamic rate determination

 SAP AG

© SAP AG 29
Flexible Structure of Billing Rules

Flexible Structure of Billing Rules

Variant
Variant Pool
Pool
QUANTITY x
QUANTITY FACTOR
FACTOR QUANTITY
QUANTITY
Calculates
Calculates x%
x% of
of aa quantity
quantity

.. .. .. Variant
Variant Pool
Pool

.. .. .. ACTIVE_KWHx 0.5
ACTIVE_KWH 0.5 
 ACT_50%
ACT_50%

NUMBER
NUMBER OF
Calculates
OF DEMAND
Calculates N
DEMAND PEAKS
N peak
PEAKS
peak averages
averages
DEMAND
DEMAND REACT_KWH
REACT_KWH --ACT_50%
ACT_50% BILL_REACT
BILL_REACT

DEMAND x PRICE
DEMAND PRICE   BILLING
BILLING LINE
LINE ITEMS
ITEMS BILL_REACT x $0.06
BILL_REACT $0.06 BILLING
BILLING LINE
LINE
Valuates
Valuates demand
demand with
with aa price
price ITEMS
ITEMS

.. .. ..
QUANTITY
QUANTITY -
QUANTITY
QUANTITY QUANTITY
QUANTITY
Difference
Difference of
of two
two quantities
quantities Contract
Contract text:
text:
.. .. .. The
The reactive
reactive energy
energy that
that exceeds
exceeds 50%
50%
of
of the
the active
active energy
energy is
is valuated
valuated using
using aa
.. .. .. separate
separate price.
price.
x
QUANTITYPRICE
QUANTITYPRICE BILLING
BILLING LINE
LINE ITEMS
ITEMS R

Valuates
Valuates energy
energy with
with aa price
price

 SAP AG

© SAP AG 30
Billing Modules: 5

Billing Modules: 5

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 31
Operand

Operand

 Individually determined
symbolic name or
description for the
assigned values that are
used as input and output
parameters in variant
programs

 SAP AG

 An operand is allocated to one operand category. Operand categories are defined by SAP and cannot
be changed by the customer.
 Operands are defined by the customer. It is important that you consider the key assignment before
you create operands.
 An operand is assigned to one division.

© SAP AG 32
Examples of Operand Categories

Examples of Operand Categories

Operand Category Name

AMOUNT Amount
DEMAND Demand (general)
FACTOR Number with decimal places
QUANT Quantity (general)
QPRICE Quantity-based price
REFVALUE Reference value
SEASON Season
TPRICE Time-based price

 SAP AG

 Operands create the link between the values to be billed and the variant programs.
 An operand is allocated to one operand category and one division. The operand categories are
preprogrammed and they define the function of the respective operand. Those operand categories
which are required as input and output operands are specified in the variant programs.
 Approximately 20 different operand categories are defined in the system.
 The operand categories are predefined by SAP and cannot be changed.

© SAP AG 33
Indicators for Operand Categories

Indicators for Operand Categories

 History

 Season-based

 Obligatory/optional value

 Usage

 Unit of measurement

 Access control

 SAP AG

 With the History indicator (historical operand values supported), you can control whether or not the
operand values can be maintained, i.e. whether or not the values can be entered at different times.
 The unit of measurement is the measuring value of a dimension.
 With the Season indicator (season permitted for operand), you can control whether or not season-
based values can be maintained for operands of this category.
 The Optional and Required indicator (optional/required replacement value permissible) determines
whether or not replacement values can be used for this operand.
 The usage indicators define where operands of this category can be used.
Examples: Installation, Rate category

© SAP AG 34
Rate Structure: Operands

Rate Structure: Operands

Operand Operands Operand

Categories Values

• Predefined • Determined • Provide

individually operands
• Control with values
processing • Serve as the
via variant parameters • Define actual
programs for variant values
programs

 SAP AG

 Operands can be provided with values in the following objects:

Rate facts
Rate category facts
Installation facts
Dynamic determination at billing runtime

© SAP AG 35
Parameters for Operands

Parameters for Operands

 Operand use

 Division

 Operand access

 Rounding

 Weighting key

 Demand control

 Franchise fee control

R

 SAP AG

 The operand use shows whether this is a register operand (operand used to enter the consumption of
the register in the rate), a normal operand (e.g. a price operand), or an operand used to represent the
bill printout history (data transferred from the old system).
 Operands are generally for a specific division.
 Rounding consists of two combined fields:
Rounding and Rounding type.
Rounding is carried out as follows:
If you specify a positive value, rounding is carried out to that number of decimal places. If you
specify a negative value, rounding is carried out to that number of pre-decimal places.
The rounding type indicates the rounding principle: rounding up, down, or to the nearest whole
number.
 The demand control is used to define how many demand values of a register are to be taken into
account during billing.
 Using the franchise fee control, you specify the type of calculation for the franchise fee.

© SAP AG 36
Weighting

Weighting
Determination of expected values (e.g. meter readings) by
means of:
 Linear weighting
 Weighting of energy feeding
 Weighting of degree days
 General weighting

Consumption

General weighting
Degree days
Energy feeding
Linear
Jan Feb .... Nov Dec
R

 SAP AG

 The energy feeding volume per period is used for weighting for the periodic distribution of
consumption and calculating a weighted average in thermal gas billing.
 For the weighting of degree days, you define temperature regions with similar temperatures. For
these areas and for each degree day, you then specify the degree day coefficients.
 General weighting can be set individually. You can define both the period and the weighting values.
 The register operand determines the weighting of the consumption registers. As soon as a rate type is
allocated to a meter, weighting is determined via rate type --> rate determination --> rate --> register
operand --> weighting key.

© SAP AG 37
Linear Weighting

Linear Weighting

 In addition to defining a different weighting

procedure, you can specify a fixed, linear
portion as either an absolute value or a
percentage.

Consumption Total

Degree days

Linear
Jan Feb .... Nov Dec

 SAP AG

 The portion indicated as a percentage refers to the period consumption.

 You specify the fixed values for the linear or percentage portion during device installation.

© SAP AG 38
Access Control for Operands

Access Control for Operands

 All values are considered

 The value at the end of the rate period is valid

 The value on the key date is valid

 The value at the end of the billing period is

valid

 All values in the month-based billing period

 SAP AG

 The key date for month-based billing is defined in the meter reading unit.
 Using the access control you specify how certain values are determined from the facts (rate facts, rate
category facts and installation facts). The access control determines the prorations carried out in the
billing process.

© SAP AG 39
Access Control: Example 1

Access Control: Example 1

03/01 28/01
Demand 10 kW
29/01 3/08
11 kW 09/03 14/03
Last day
12 kW 15/03 of month

03/01 05/02 13 kW
Rate 1
06/02 30/03
Rate 2

03/01 30/03
Bill. Period

All values are considered :

03/01 28/01
Demand 10 kW
29/01 05/02

11 kW
06/02 08/03
11 kW
09/03 14/03
12 kW 15/03 30/03
R

13 kW

 SAP AG

 In this example, every demand from the installation facts is taken into consideration. In addition,
proration is carried out due to the rate change.

© SAP AG 40
Access Control: Example 2

Access Control: Example 2

01/03 01/28
Demand 10 kW
01/29 03/08
11 kW 03/09 03/14
Last day
12 kW 03/15 of month

01/03 02/05 13 kW
Rate 1
02/06 03/30
Rate 2

01/03 03/30
Bill. Period

The value at the end of the billing period is valid

01/03 02/05
Demand
13 kW
02/06 03/30
13 kW
R

 SAP AG

 In this example, only two time slices are created by the rate change. For both time slices, however,
the demand value at the end of the billing period from the installation facts is used.

© SAP AG 41
Allocation of Operand Values

Allocation of Operand Values

Installation Facts
Hierarchy

have priority over

Rate Category Facts

have priority over

Rate Facts and Rate Fact Groups

 SAP AG

 Operand values are generally stored in the rate facts and are therefore valid at the rate level.
However, specifications for multiple rates can also be made in the rate category facts and in the
installation facts, and these have priority over the rate facts.
 At the fact level, you can enter replacement values instead of fixed operand values. This makes
allocation of operand values flexible.
 An historic overriding of operand values is also possible. For example a certain installation can be
allocated another price key for just one month. In the other months, the values can be taken from the
rate facts.
 If, during billing, no operand value can be determined, billing is aborted and the error is reported in
the billing log. Exception: the rate step is marked in the rate as an optional rate step.
 You define general operand values in the rate facts and rate category facts and you store individual
values at the installation fact level (e.g. installed demand, connection loads, ordered demand).

© SAP AG 42
Billing Modules: 6

Billing Modules: 6

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 43
Variant Programs: 1

Variant Programs: 1

 Are small, independent ABAP/4

programs

 Perform elementary calculation steps

 Are used in combination to model the

billing rules in the rate

 SAP AG

 Variants are small, independent programs

 Variants perform elementary calculation steps. Many variants calculate values relevant to billing and
therefore generate billing line items. Other variants convert values and make the results available to
subsequent variants.
 These variant programs can be combined in any way, enabling complex billing rules to be
represented.
 You can also create your own variant programs to represent special, non-standardized calculations.

© SAP AG 44
Variant Programs: 2

Variant Programs: 2
ABAP/4
Function Modules

function isu_quanti01.

Include ievarbasic. Output

Data: ...... Operands
.....
Input If wprei-preisart = ‘2’.
Operands loop at ......
.....
endif. Billing
Line Items
endfunction.

 SAP AG

 In most cases, variants have input and output operands which represent the parameters included in
the variant. These operands belong to a particular 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 45
Examples of Variant Programs

Examples of Variant Programs

COMPUT01 Subtraction of two amounts

DEMAND01 Valuation of a demand using a price
DISCNT01 Quantity discount, percentg. or abs. amount
IF01 Condition: If Quantity1 >,>=,= Quantity2
ELSE Start of a NOT operation for an IF variant
ENDIF End of an IF nesting
INFACT01 Writing of a demand in the installation facts
QUANTI01 Valuation of a quantity with a price
QUANTI05 Writing of info lines for the quantity
R

 SAP AG

 The system contains a whole range of variant programs.

 A simple evaluation function helps you to select the variants you need for the billing rule.
 The keys of the variant programs have a particular semantic. So, for example, all variants which
begin with QUANTI deal with consumption/quantities to be billed.
 The variants are grouped as follows:
COMPU* Arithmetic operation
DEMAND* Demand valuation
DISCNT* Discounts, surcharges
INFACT* Writing of values in the installation facts
IF/ELSE/ENDIF Conditions in rate
LUMSUM* Valuation of flat rates
QUANTI* Valuation of consumption/quantities
REFVAL* Valuation of reference values
SETTLE* Calculation of rental prices
UTILIT* Special billing features

© SAP AG 46
Billing Modules: 7

Billing Modules: 7

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 47
Rate Characteristics

Rate Characteristics

 Type of register use

 Value relevant to billing measured by a register (register operand)

 Calculation formula

 Specification of price operands for price determination

 Constants, factors, influencing values

 General ledger accounts

 Handling of billing line items

 SAP AG

 The consumption of the register is made available in the register operand. The register operand is
determined via the following chain: register --> rate category --> rate --> register operand.

© SAP AG 48
Rate

Rate

Rate

Operand Rate Steps

Operand Variant
Category Program

 SAP AG

 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 are determined with the rate:
How the measured consumption is extrapolated or broken down for meter reading data processing
and for proration
Which billing values are measured by a register
Which reference values are billed
In which calculation formula the measured values or reference values are included
Which prices are used
Which constants, factors and influencing factors are included in the calculation
To which G/L accounts the calculation results (billing line items) are posted
How the billing line items are dealt with statistically
To which division and billing class the rate is allocated.

© SAP AG 49
Rate Attributes

Rate Attributes
Rate Header
• Division
• Billing Class
• Permissibility
• Register-Related Data
• Notes

Rate Steps
• Variant Programs
• Sub-transactions
• Operands  Rate Facts
• Statistical Rate
• Franchise Fee Group
• Control Parameters

 SAP AG

 The register operand is entered in the header data. The consumption of the register is made available
in these register operands. The register operand is determined with the following chain: register -->
rate type --> rate --> register operand.
 Larger rates with several rate steps can be documented using the notes.
 The sub-transactions control the account determination but can also be used as statistics criteria.
 The statistical rate is used to distribute revenues and quantities of the individual rate steps over
different rates for evaluation in the sales statistics.
 The franchise fee group controls the calculation of the franchise fee.

© SAP AG 50
Transactions

Transactions
FI-CA SAP

Main Internal
Transactions IS-U Main Trans.
IS-U

IS-U Allocation
Transactions SAP
FI-CA
Internal
Sub- • Allocation to Sub-Trans.
Transactions • IS-U settings internal
• Debit/credit transactions • Default setting
• Account determ. • Interest key by SAP
• Tax determ. • Stat./non-stat.

Transactions describe the accounting transaction on

which the posting of a document line item is based R

 SAP AG

 A transaction is a combination of main and sub-transactions.

 Texts allocated to the main and sub-transactions describe the accounting transaction and are made
available for correspondence.

 Main and sub-transactions control both IS-U account determination and IS-U tax determination.

 IS-U uses internal main and sub-transactions, which are assigned by the system to the different IS-U
business processes, which they then control.
 The internal transactions represent only a minimum of all transactions available in the IS-U
functions. You can also maintain any number of transactions for manual postings.
 You can specify transactions in IS-U by means of certain characteristics such as the debit/credit
indicator, the interest key, and the statistics indicator.

© SAP AG 51
Account Determination: Receivables Account

Account Determination: Receivables Account

Contract/ Accounting
Contract Account Transaction
Account
Company code 0001 Determination For example, billing:
Division 01 (Posting Area R000)
Account Main transaction 0010
determination ID 01

Receivables
Account
Balance sheet
account 140500

(Receivables for R

energy supply)

 SAP AG

 The account determination ID can be found in the contract account for multiple-contract or contract-
independent postings, or in the contract.

© SAP AG 52
Account Determination: Sales Revenue Account

Account Determination: Sales Revenue Account

Accounting
Transaction
Transaction
For example, billing: Determination
Transaction
Main transaction 0010
Sub-transaction 0010 0010-0010

Contract/
Contract Account Account
Determination
Company code 0001 (Posting Area R001)
Division 01 Sales Revenue
Account Account
determination ID 01
Profit/loss
account 800010
(Revenue from
energy price:
R

electricity)

 SAP AG

 The account determination ID can be found in the contract account for multiple-contract or contract-
independent postings, or in the contract.
 In addition, the sub-transaction is required for sales revenue account determination.
 Additional account assignments (for example, cost center, plant) and the tax determination ID are
also determined through sales revenue account determination.

© SAP AG 53
Time Period Control

Time Period Control

 Calculate time period for an exact number of days

 Month-related time period dependent on a key date
 Month-related time period dependent on an interval
 Month-related time period dependent on a key date
(move-in/move-out to the precise day)

 SAP AG

 You can control how periods are to be calculated by means of the period control in the rate steps.
 The key date for month-related billing is entered in the meter reading unit.
 The intervals for month-related billing are entered in the portion.

© SAP AG 54
Variant Control

Variant Control
COMPUT01
COMPUT01
COMPUT02
COMPUT02
COMPUT03
COMPUT03
COMPUT04 Control Indicator
COMPUT04
COMPUT08 ••Operand
COMPUT08
QUANTI02
Operandupdate
update--Addition
Addition
QUANTI02 ••Operand
QUANTI08 Operandupdate
update--Overwrite
Overwrite
QUANTI08
QUANTI09
QUANTI09
QUANTI10
QUANTI10
QUANTI15
QUANTI15 Control Indicator
••Normal
Normalprocessing
processing
IF*
IF* ••Trigger
Triggerevent
event
••Abort billing
Abort billing

QUANTI*
Control Indicator
QUANTI*
DEMAND* ••Write
DEMAND* Writeinfolines
infolinesabout
aboutquantity
quantity R

 SAP AG

 With the variant control you can control the different variant programs. Control indicators are not the
same for all variant programs but depend on each variant program’s task.

© SAP AG 55
Billing Master Data: 3

Billing Master Data: 3

 Individual components
 Modeling of the billing logic
 Facts
 Dynamic rate determination

 SAP AG

© SAP AG 56
Billing Modules: 8

Billing Modules: 8

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 57
Fact Group

Fact Group

Operand
Value A

Fact
Rate
Group

Operand
Value B
Fact groups enable the use of different
operand values within one rate.

 SAP AG

 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.
 Using the fact group, you can assign different values to individual operands in the rate facts.
 A fact group must always be entered in combination with a rate type.

© SAP AG 58
Allocation of Operand Values

Allocation of Operand Values

Hierarchy

Price A
Installation Facts .55

Have precedence over

Price B
Rate Category Facts .60

Have precedence over

Price C
Rate Facts and Rate Fact Group .70

 SAP AG

 Operand values are usually stored in the rate facts and are therefore valid at rate level. Specifications
for all rates can also be determined in the rate category facts and the installation facts and have
preference over the rate facts.
 At rate category fact level, replacement values can be entered instead of fixed operand values. With
these replacement values, flexible allocation of operand values is possible.
 You can also historically override operand values. In this way a different price key can be allocated
to a certain installation, for example, for just one month. In the other months the values from the rate
facts are used.
 If, during billing, no operand value can be determined, billing is aborted and the error is reported in
the billing log. Exception: the rate step is marked in the rate as an optional rate step.
 You define general operand values in the rate facts and rate category facts and you store individual
values at the installation fact level (e.g. installed demand, connection loads, ordered demand).

© SAP AG 59
Individual Rate Category Data and Installation Facts

Individual Rate Category Data and Installation

Facts
 You can override the data in the general rate category
and in the facts to allow for customer-specific
agreements.
 The rate type, and therefore the rate, can also be
specified in the facts.
However, only rate types for which the appropriate indicator is set can be
used in the facts. These rate types cannot be maintained at the device or
register level.

Indiv.
Indiv.Rate
RateCategory
Category
Installation
InstallationFacts
Facts

Rate
RateCategory
Category
Rate
Rate
R

Rate
RateType
Type

 SAP AG

© SAP AG 60
Billing Modules: 9

Billing Modules: 9

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 61
Billing Schema: 1

Billing Schema: 1

 Is valid for a certain division

 Is valid for a certain billing

class

 Contains one or more rates

 Determines the sequence of

the rate steps for billing

 SAP AG

 Rates, variant programs, and operands are entered 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.

© SAP AG 62
Billing Schema: 2

Billing Schema: 2

 Dependent on the rate

category in the installation

 Can be overridden by the

installation facts or the rate
category facts (rate category
is kept)

 SAP AG

 The schema is determined from the rate category that is entered in the installation. In certain
exceptional circumstances the schema can be overridden at the installation facts level.

© SAP AG 63
Schema Attributes

Schema Attributes

Schema Header
•Division
•Billing Class
•Billing Block
•Notes

Schema Steps
•Rates
•Control Indicator
•Sort Key

 SAP AG

 When a schema has been changed it is automatically blocked, and this billing block has to be lifted
by the clerk.
 A schema is always allocated to a certain billing class and division. This checks the permissibility of
different billing master data against each other.
 A schema is made for a particular customer group. If too many schema steps are contained in the
schema, which are not processed for each customer, it results in unnecessary run time.
 The schema must contain all rates that can be billed together in an installation: e.g.
On-peak rate active energy
Off-peak rate active energy
On-peak rate active power

© SAP AG 64
Sorting for Bill Printout

Sorting for Bill Printout

 Presort keys are for sorting billing line items before

printout.
 Billing line items with the same presort indicators
comprise a group.
 Billing groups are sorted in ascending order according
to the presort key.
 Function modules are used for sorting within billing
groups.
 Presort keys must be allocated to all document lines in
the schema.
R

 SAP AG

 The presort keys are allocated in the schema of every billing or information line item and specifies
how individual billing line items are sorted for bill printout.
 You have to take all schemas into consideration. Thus for example, if an electricity and gas bill is to
be created, then the presort keys in the electricity and gas schemas should be checked against each
other.

© SAP AG 65
Billing Modules: 10

Billing Modules: 10

 Billing class
 Rate type
 Price
 Operand
 Variant program
 Rate
 Fact group
 Schema
 Rate category
R

 SAP AG

© SAP AG 66
Rate Category: 1

R a te C a te g o ry : 1

 V a lid fo r o n e d iv is io n o n ly
 B e lo n g s to a s in g le b illin g c la s s
 C o n ta in s o n e v a lid b illin g s c h e m a
 C o n tro ls p ro c e s s in g o f m e te r re a d in g d a ta
 C o n tro ls b illin g ; in co n ju n c tio n w ith th e ra te ty p e ,
th e ra te c a te g o ry is u s e d to d e te rm in e th e ra te

 S A P AG

 Classification of an installation for billing. This is used with the rate type to determine the rate.
 Rate determination
Rate type + rate category = rate

© SAP AG 67
Tariftyp

Rate Category: 2

Division
Billing Schema

Billing Class Rate Category

Outsorting
Group

Notes
R

 SAP AG

 The rate category contains data which controls the processing of meter reading data for all rates. This
could include:
billing schema
control of the final billing and flexible backbilling
budget billing control
outsorting checks
prior period control
 Along with this data, other data relevant to billing is also saved in the rate category. This could
include agreed quantities, demand, prices or flat rates. For flat rate services (such as cable services or
lighting), the consumed quantity is not measured. It is therefore necessary to define replacement
values which are used for evaluation (e.g. the number of cable connections or lighting with a certain
connection load).

© SAP AG 68
Billing Master Data: 4

Billing Master Data: 4

 Individual components
 Modeling of the billing logic
 Facts
 Dynamic rate determination

 SAP AG

© SAP AG 69
Rate Determination

Rate Determination

Rate
Rate
Category
Category

Historical Rate
Rate

Rate
RateType
Type

 SAP AG

 Rate determination
Rate type + rate category = rate
 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.

© SAP AG 70
Rate Use

Rate Use
Business Objects
Relevant to Billing
Billing Master Data
Installation
Structure
Register Rate type (e.g. energy price)

Device Rate type (e.g. no register)

Rate category (e.g. no register)

Installation
Rate category (e.g. flat-rate installation)

 SAP AG

 The rate is comprised of a combination of the rate type and the rate category.
 The rate type is usually maintained in the register. In certain cases, it can also be maintained at
device level or in the installation facts. In addition, the rate type can be entered in the rate category
facts (for example, if a device does not exist).
 If reference values are used, the rate type is stored in the installation facts.

© SAP AG 71
Universal Billing Engine

Universal Billing Engine

Customer- and Rate Data Procedural Data
Installation-Related Data

Prices and Schema I

Rate Facts E
Contract Rate Var.Prog.Values
Rate 1
X
- Step 1 VarProg. A x1 E
Rate 1 - Step 2 VarProg. B
. .
x2
.
C
Rate 2 U
Installation - Step 1 VarProg. A x3 T
- Step 2 VarProg. C x4
Rate - Step 3 VarProg. D x5 I
Determ. .
.
.
.
.
.
O
Inst. Structure/ Rate n . . . N
. . .
Rate Cat. Facts/ Rate n
Install. Facts - Step 1 VarProg. A xxx

Execution
Quantity Validation Generation
Data Entry of Variant
and Conversion of Billing of Billing
Programs
Analysis and
R

According to Results Line Items

Proration
Schema
 SAP AG

 Dynamic rate determination finds the rate using the rate category and the rate type. This control is
specified in customizing. A rate can be allocated to different rate determinations. In this way,
individual rates can be used for different billing structures.
 Individual rates are then grouped together in different schemas.

© SAP AG 72
Initial Data Creation of a Rate

Initial Data Creation of a Rate

Rate
Ratetype
type

Operands
Operands(create
(createfrom
fromrate)
rate)

Link to fact
Prices
Prices(create
(createfrom
fromrate)

group
rate)

Variant
Variantprograms
programs
Rates
Rates Determine

Determine Rate
Ratesequence
Billing
Billingschema
schema sequence

Select Billing
Billingschema
Rate
Ratecategory
category schema

Allocate
Rate
Ratedetermination
determination Rates
Rates
R

 SAP AG

 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

© SAP AG 73
Contract (Residential Customer - Electricity)

Contract (Residential Customer - Electricity)

1. Customer without measured demand For annual consumption of less
than 10,000 kWh/year
Consumption Prices

Without off-peak regulation 0.24 Uni/kWh

With off-peak regulation

- On-peak rate 0.24 Uni/kWh

- Off-peak rate 0.11 Uni/kWh

Demand Price (fixed contribution per installation) 100 Uni/year

Rental Price See no. 3

2. Average Price Limitation

Energy Prices
- Maximum Price (on-peak rate) 0.48 Uni/kWh
- Off-peak rate 0.11 Uni/kWh

Rental Price See no. 3

3. Rental Prices
R

- Single-rate meter 50 Uni/year

- Double-rate meter 70 Uni/year
 SAP AG

© SAP AG 74
Master Data and Billing Master Data

Master Data and Billing Master Data

Business
Partner
Contract
Installation
XYZ0011

Installation Installation Structure

Facts Device Reg Rate type
EREFVAL=8kW 12345678 001 1001
12345678 002 1002

Rate Category
E1
Schema: Rate Determination
E1 Rate cat. Rate type Rate
E1 1001 E1_1
E1 1002 E1_2
Rate Facts
EQPRICE1=
E1_1_1...

Schema E1

Rate Variant Operand

E1_1 QUANTI01 EQUANT1 EQPRICE1
E1_1 REFVAL01 EREFVAL ETPRICE1
...

Rate Variant Operand

R
E1_2 QUANTI01 EQUANT2 EQPRICE2
...
...
 SAP AG

© SAP AG 75
Billing Master Data: Unit Summary

Billing Master Data: Unit Summary

 Billing is the central component of the IS-U system

for calculating demand from energy and water supply
to customers.

 The central billing engine enables you to model all

possible combinations of different billing steps.

 Rate determination allows for quick adjustment of

entire customer groups to the company’s new rates.

SAP
SAP AG
AG

© SAP AG 76
© SAP AG 1