Energy Billing PDD for TPL Project

Project
Trigger
PDD for
MSD.03.02
Energy Billing
Saichand Dade,
Srinivas Punati,
Kiran Kumar Potti,
Ajay C Mehta.
Date: 01/01/2009
Project Trigger
SAP ERP, ISU, EP and BI Implementation
Process Definition Document
MSD.03.02 Energy Billing
Version 1.0 (Draft)

January 2009
Blueprint Phase: Process Definition Documents
Sunday, July 17, 2016

Page 2 of 41
Document Control:
Author
File Name and Path
Created
Last Edited
Versio
n
1.0
Revision
Date
24.01.2009
Saichand Dade, Srinivas Punati, Kiran kumar Potti,

Ajay C Mehta
PDD_MSD.03.02_Energy Billing
Revision
Description
Initial Draft
Author/
Process Owner
Saichand Dade,
Srinivas Punati,
Kiran Kumar Potti,
Ajay C Mehta
Sign-Off
Target Readership
Project Team Members

Page 3 of 41
2
2.1
Introduction
What is the Business Blueprint?
The Process Definition Document is the main deliverable of the Business Blueprint phase. The
purpose of this document is to verify that a proper understanding of requirements has been
communicated. The blueprint also finalizes the detailed scope of the project.
2.2
Developing and Updating the Business Blueprint

The Business Blueprint will be created in the Business Blueprint Phase. This deliverable is a
central grouping of various disciplines. Blueprint deliverables and strategies will be the
fundamentals for development and management in the on-going phases of the project.
After sign-off as been obtained from the relevant parties involved, a copy of the Business
Blueprint will be stored for reference only.
2.3
Document Availability
This document is readily available to all staff on the project through a read only access to the
controlled environment or through a hard copy. Please note that the master copy is held in
electronic format under the document reference.
2.4
Document Sign Off

Process Definition Document will be submitted to process owners for final sign off. Process
owners are requested to respond with in three (3) business days from the date of submission,
after which a discussion on the changes required will be initiated. The document must be
signed-off within five (5) business days after the same is submitted to the process owner for the
first time. If no response is received from the Process Owner within five (5) business days, then
the document will be deemed signed-off.

Page 4 of 41
Document Sign-Off Sheet

Location: Ahmedabad/Surat/Bhiwandi
(Duplicate sign off sheet in case there are more than one location process owners involved for
signoff)
X
Torrent Power Limited:
Process Owner, Designation:
Torrent Power Ltd:

Team Lead:
IBM
Process Lead
Process Teams:
Trigger-TPL
Trigger-IBM
Aajay C Mehta
Saichand Dade
Jayendra patel
Srinivas Punati
Manish G Panchal
Kiran Potti

Page 5 of 41
Table of Contents
1
DOCUMENT CONTROL:............................................................................................................3
INTRODUCTION..........................................................................................................................4
2.1
2.2
2.3
2.4
WHAT IS THE BUSINESS BLUEPRINT?...............................................................................................4

DEVELOPING AND UPDATING THE BUSINESS BLUEPRINT.................................................................4
DOCUMENT AVAILABILITY...............................................................................................................4
DOCUMENT SIGN OFF.......................................................................................................................4
DOCUMENT SIGN-OFF SHEET................................................................................................5
TABLE OF CONTENTS...............................................................................................................6
PROCESS DESCRIPTION...........................................................................................................7
PROCESS DESIGN.......................................................................................................................9
6.1
6.1.1
6.1.2
6.1.3
6.1.4
6.1.5
6.1.6
6.1.7
6.1.8
6.1.9
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.12
BUSINESS PROCESS DESCRIPTION:...................................................................................................9

Create individual bill:...............................................................................................................10
Mass Billing:.............................................................................................................................11
Outsorting:................................................................................................................................12
Reverse billing document:.........................................................................................................12
Create manual billing:..............................................................................................................12
Simulation:................................................................................................................................12
Existing Billing process in TPL (Ahmadabad):........................................................................12
Existing Billing process in TPL (Surat):...................................................................................12
To be Process:...........................................................................................................................12
FLOW DIAGRAM..............................................................................................................................12
EXCEPTION AND VARIATIONS.........................................................................................................12
KEY PERFORMANCE INDICATORS...................................................................................................12
INTEGRATION POINTS......................................................................................................................12
INTERFACE......................................................................................................................................12
GAPS AND SOLUTIONS:...................................................................................................................12
CONFIGURATION:............................................................................................................................12
REPORTING REQUIREMENT:............................................................................................................12
CHANGE MANAGEMENT............................................................................................................12
AUTHORIZATION.........................................................................................................................12
AS-IS REFERENCE......................................................................................................................12

Page 6 of 41
Process Description
Enterprise Area:
Scenario:
Process Group:
Process:
MSD
MSD.03
MSD.03.02
MSD.03.02.01
MSD.03.02.02
MSD.03.02.03
MSD.03.02.04
MSD.03.02.05
MSD.03.02.06
SAP-ISU
Manage Billing and Invoicing
Energy Billing
Individual Billing
Mass Billing
Out sorting
Simulation
Reversals
Manual Billing (SMA, Dr/Cr)
Summary:
5.1
Contract Billing:
The supply and services provided by a TPL company are billed using
this component. It offers a range of billing procedures with a variety of
selection and control options. For example, the component enables:
Billing of different class of customers like LT, LTMD and HT

customers
periodic monthly and Bi-monthly billing cycles
Billing for electricity division.
Numerous bill forms.
Billing simulation.
Validation of billing documents and bills.

Page 7 of 41
Billing uses meter reading results to determine the evaluation basis

for schema execution. All calculations required for rate creation are
made during schema execution. Different billing periods are included
in the various billing procedures. All master and billing master data
can change during a billing period. The billing module ensures that all
billing-relevant changes that occur during a billing period are taken
into consideration. For example, a price change causes the system to
divide the total period into sub periods, each with the price valid for
that sub period. The system also divides the total consumption, which
produces the corresponding partial amount.
You can process all known period categories using different billing
procedures.
Creation
Creation of
of
Meter
Meter Reading
Reading Order
Order
Entry
Entry of
of
Meter
Meter Reading
Reading Data
Data
Billing Order
Billing Order
Billing
Billing
Invoicing
Invoicing
Billing Document
Bill
Bill
Printout
Printout
Print Document
Meter
Reading
Order

Page 8 of 41
This document, as mentioned earlier in the Section 2.1, records and

ensures that a proper understanding of requirements of the existing
process has been communicated and will be addressed by the TPL/IBM
Teams responsible, through the To-Be Processes. This PDD is therefore,
a basic detailing that becomes a ground framework for mapping them
to the relevant functionalities in the SAP system. Therefore, to get a
complete understanding / detailed information at a later point in time,
it is recommended that this PDD document be read with three other
Blueprint phase project documents. These other documents further
detail / deal with the TPL requirements and the configuration /
customizing required to support them. These documents will be
initiated and finalized later with-in the Blueprint Phase, after the
milestone of PDD sign-off is achieved. Any changes effected thereafter
will be required to be included in the PDD. The three other documents
of the Blueprint Phase are:
1. TPL_ISU Billing & Invoicing Key Data Structure document
2. TPL_ISU Billing & Invoicing Developments document
3. TPL_ ISU Billing & Invoicing Gaps and Solutions document
You may also need to refer other documents that detail the Change
and Authorization Management and Configuration Management.
These will be deliverables of the end of next Phase of the project
known as Realization.

Page 9 of 41
6
6.1
Process Design
Business Process Description:
Objective:
The actual contract billing (Energy Billing) is performed with various

components wise. Contracts are billed automatically. Alternatively you
can process and bill individual contracts manually. Billing process
resulted in the creation of billing documents.
Every contract in IS-U has a predefined date at which it is due for
billing. In order to process the actual billing in IS-U, several
preconditions have to be fulfilled.
Business Requirements:
Periodic billing Execution:

1. Billing order:
A billing order has to be generated for every contract with reason

periodic billing. Interim Billing orders can also be generated for any
customer if any fortnight billing or any interim billing is required (e.g.
for HT fortnight billing & Temporary supply billing etc.). This will be
created automatically while creating meter reading order relevant for
billing (e.g. periodical meter reading, Interim meter reading with
billing). Billing orders can be generated for single contracts or for
whole meter reading units as a mass generation process. It is pre
requisite for billing. It contains details like Scheduled billing date,
Portion and Installation. Once the contract/installation has been
successfully billed, the billing order is deleted.

Page 10 of 41
2. Meter Readings:
Meter reading results have to be entered into the system.The actual

process of periodic billing starts after the meter readings are entered
and valid.
Both these preconditions have to be fulfilled to make a
contract billable in IS-U. These are taken care by Device
Management while uploading the meter readings into system.
3. Billing :
After the billing order gets the status billable, billing can be
executed individually or mass which will generate billing documents
for each contract and transfers information to invoicing. The billing
document will contain details like, billed quantity, billing price data,
rate data, device data and meter reading data etc.
4. Invoicing:
After billing document generation that will be invoiced, in the invoicing

process, arrears amount, interest, discounts and taxes will be added
and invoice posts the amount in the corresponding accounts, prepares
print document.
Periodicity of Billing, Billing Portions, Scheduling:
Portions combine contracts that are to be billed together. Contracts
are assigned to a portion either indirectly via the meter reading units
that are specified in the installation associated with that contract or
directly in the contract.

Page 11 of 41
Portions and their parameter records (Monthly/Bi-monthly reading

dates) are the basis to generate dates for meter reading, billing, in
general the time schedule for billing.
For more details on Portions please refer PDD MSD.01.01
Manage Schedule Master data.
6.1.1
Create individual bill:

Use this transaction if a billing document has to be created for only
one contract, Installation or contract account. It is possible to
manipulate the level of processing. The choices are to generate the
billing document, the invoicing document or to print or display the bill
instantly.
It is possible to perform checks that are similar to the mass billing
process, individual simulation (EASISI) and individual overall check
(EASICH). Since this functionality is standard, no configuration will be
discussed. In order to create an individual bill a scheduled order has to
be selected. Based upon the data in this order the individual bill will
be produced.
6.1.2
Mass Billing:
This transaction performs the mass billing for all the selected billing
orders that are ready to be billed. It is only possible to bill an order
when a plausible meter reading result is entered. The result of this
transaction is the creation of billing documents. Correct billing
documents serve as input for the invoicing process.

Page 12 of 41
It is possible to make a selection of installations according to multiple

criteria. It is recommended to run this transaction in batch. The
criteria needed to select the Installations to be billed will be the
portion. The criteria used can be saved in so called variants to reuse
them every time a billing cycle is performed.
SAP ISU provides two transactions that can be used to check the data
before the actual billing cycle is performed, mass billing simulation
(EAMASI) and mass overall check (EAMACH). The first can be used to
perform a simulation of the billing run with the actual meter reading
data and Price data. After the result is checked and everything is in
order the actual billing run is performed. The second transaction is
used to check if the configuration within ISU is entered correctly. If
some data is missing which lead to situation in which an installation is
not billable, this is shown to the user.

Page 13 of 41
6.1.3
Outsorting:
When the billing orders are picked up by either the mass billing or the
individual billing process, the outcome (amount) of the calculation is
checked against certain limits. These limits can be implemented for
different out sorting check groups.
Default a billing out sorting check group will be linked to the rate
category. If an out sorting check group is specified on contract level, it
overrides the one assigned to the rate category. An executive or
employee can display the out sorted billing document and can check
line items. He can release that document for further processing or he
can reverse the document for necessary corrections.
6.1.4
Reverse billing document:

If the analysis of the out sorted billing document points out that there
is something wrong with, for example the meter reading data the
billing document has to be reversed before changes are made. Using
this transaction the user is able to select one or more billing
documents and reverse them.
Reversal will be done if the bill is incorrect. These are two types of
reversals happening in SAP IS-U.
1. Billing Reversal
2. Invoice Reversal
Billing reversal:

Page 14 of 41
Billing document can be reversed more than once as long as it has not
been invoiced. The executive/employee can reverse the billing
document and carry out additional activities such as changing the
meter reading result. Billing order will be restored whenever reversal
takes place. Then the contract can be billed again.
Reversal will based on the reasons, these may be as follows:
Meter reading is wrong
Meter is defective
Wrong rate is applied
Incorrect billing period
Others
Invoice reversal:
There are two times at which reversal is possible in the system.
Reversal can occur after billing or after invoicing. There are two
possibilities of reversal after invoicing Adjustment reversal and Full
reversal.
Refer PDD MSD.03.03 invoicing for more details.
6.1.5
Create manual billing:

This transaction is used to create manual Debit/credit memos. We can
bill contracts manually using this component. For example, you can:
Generate billing documents for a new contract.

These documents can be credit memos or receivables that you
can include in the next consumption billing or create as
separate, independent bills.

Page 15 of 41
Use manual billing alternatively or in addition to automatic

billing.
Manual billing supports the following functions:
Automatic price determination
Proration in the case of tax, duty or price changes
We can create billing documents manually for a contract independent

of automatic scheduling. You can invoice manual billing documents
separately or together with automatic billing documents.
In case of TPL this transaction is used to settle the Debit/Credit
balance of customers. It is the requirement of TPL that in case of a
debit/credit balance in customer account it will settled with the next
invoice. According to this debit/credit memos will be created in the
system that will be appear as a line item on the invoice.
6.1.6
Simulation:
Simulation is a tool to preview an invoice before the actual invoice is
issued. This is performed mainly for checking and reference purpose,
e.g. to check invoice presentation or to check billability after tariff
change etc.
There are two types of simulations they are, Billing Simulation and
Simulation.
Billing simulation and simulation can be used to check the result of an
actual billing and invoicing to be carried out later, without deleting
billing orders or creating invoicing orders. Both simulation types

Page 16 of 41
therefore enable you to execute billing without making any accounting

changes.
Billing simulation enables you to test automatic billing without
deleting billing orders and creating invoicing. You can repeat a billing
simulation any times, as often as you wish. As is the case for
automatic billing, you can process any selection of contracts. In
contrast to billing simulation, a simulation can also be carried out if no
billing order exists. In this case, missing meter reading results are
extrapolated (Estimated). A successful simulation concludes with the
creation of a simulated billing document.
Just as is the case for automatic billing, the simulation types Billing
simulation and Simulation link the general and billing master data to
invoicing. In most cases, simulations are not carried out periodically,
but according to need to check whether individual contracts can be
billed, for example.
You can then invoice the simulation billing documents and you receive
a simulated print document.
Since a billing simulation represents as automatic billing, the
prerequisites for automatic billing apply to a billing simulation. A
simulation does not require any billing orders or meter reading results,
these are extrapolated at runtime. If meter reading results have
already been entered at the time of the simulation, then these serve
as the basis for the calculation. If the same period is analyzed, then
the two simulation types are the same and they provide identical
results.
Billing simulation provides an amount that would be to pay per
contract if billing were actually executed, where as Simulation

Page 17 of 41
provides the amount, following extrapolation of the meter reading

results. In addition, both simulation types provide information about
the cause of an error that would occur in the case of actual billing of
an incorrect billing construct.
6.1.7
Existing Billing process in TPL (Ahmadabad):

In normal Energy billing process, after uploading the Meter reading results to
the system, billing is done as per the current tariff.
Special cases:
1. Closed Premise assessed billing:
In regular billing if the consumption determined is for closed premise

assessment then the following steps are carried out for closed
assessment billing.
1. Normal calculation procedure for the consumption recorded as
per previous billing cycle.
2. Posting of calculated amount in to debtors account and consider
in company revenue, but it is kept in Closed Assessed Revenue
Account.
3. When actual consumption recorded in next cycle, Bill will be
calculated for 120 days mode in case of Bimonthly Billing and 60
days in case of monthly billing and slab benefits are given. Here
we are required to reverse the earlier invoice.
4. If actual consumption recorded after 2 cycles (120 days or 60
days), no slab benefits will be given but bill will be calculated as
per normal 60 days mode in case of Bi monthly and 30 days
mode in case of monthly billing. Here we do not reverse fixed
charge and meter rent but we reverse the consumption of
closed assessment billing.

Page 18 of 41
2. Stop & Defective meter assessed billing:
In Case of Stop meter or defective meter, Bill will be generated as per

the recorded consumption in case of defective meter, and with zero
consumption in case of stop meter. After changing the meter a debit
or credit note will be raised based on the previous period consumption
or based on new meter consumption whichever is suitable. A Stop
meter or defective meter assessment credit or debit note period is
maximum 90 days in case of Residential and agriculture customers
and 180 days in case of other customers as per GERC norms.
In
calculation of stop meter assessment debit memos consumption will

be calculated excluding meter rent and credit memos that units
already billed will be deducted. Reversal of assessed debit or credit
notes may happen on genuine basis with necessary supporting
papers.
3. Left out assessed services billing:
In case of left out services (Water logging /civil disturbance) bill will be
generated
as
per
the
estimated
consumption.
When
actual
consumption recorded then estimated bill will be reversed and billing

will be done for 120 and 60 days for Bi-monthly and monthly cycles
respectively.
4. HT billing for Cantonment area (MES services):
MES Bills are prepared considering the Recorded Demand as Contract
Demand, Power Factor 90% is considered irrespective of actual power
factor calculated. Consumption of the billed LT Services located in MES
area is deducted from HT Consumption. There are about 90 services

Page 19 of 41
separately billed in cantonment area. These 90 services are under 14

HT services.
Here HT services billed on monthly basis and LT services are billed on
by monthly basis. Although these 90 services segregated under 14 HT
services, total consumption of LT services deducted from one HT
service only and does the billing.

Page 20 of 41
5. HT Agriculture service (Dastaan):

HT-90 service is given under BHP Agriculture tariff. Here HT bill is
calculated as per normal HT tariff rates and calculation under BHP
Agriculture tariff is also calculated (for Eight hours working per day)
per annum and which is divided by 12 months to calculate monthly
payable bill. The difference between HT bill and BHP bill is considered
for Eight hours working per day to calculate subsidy recoverable from
Govt of Gujarat. The above subsidy amount is deducted from HT bill to
calculate Bill payable amount.
6. HT Wind power concessions:
In case of wind mill owner who supplies power to UGVCL and in turn
UGVCL give us credit in import bill for 96% of units provided to the
GRID. Here we calculate HT/LTMD consumption after deducting the
credit given by the UGVCL. HT/LTMD bill is calculated as per HT/LTMD
tariff for net consumption.
7. HT Billing (In case of 2 meters):
In case where Electricity duty concessions are given for certain type of
plant, we fix 2nd sub meter to calculate consumption. Here we
calculate consumption of main and sub meter separately .Here we
have two types of Govt duty. One is for sub meter and second one is
for differed consumption (main meter consumption sub meter
consumption). The reading and consumption of sub meter are advised
by consumers at the end of month in prescribed format and the units
should be deducted manually at the time of billing for calculation of
Electricity Duty.

Page 21 of 41
8. HT Billing with Multiple Panels:

In some of the HT services where demand load is very high and which
cannot be feed by one feeder, then we give multiple feeder supply. We
install required devices to calculate consolidated demand, energy
consumption, TOU charge and PF penalty charges or credits.
9. LT Agriculture BHP Tariff:
Here LT bill is calculated as per normal LT Agriculture tariff rates and
calculation under BHP Agriculture tariff is also calculated (for Eight
hours working per day) per annum and which is divided by 12 months
to calculate monthly payable bill.
The difference between LT
Agriculture bill (for eight hours) and BHP bill is considered for Eight
hours working per day to calculate subsidy recoverable from Govt of
Gujarat. The above subsidy amount is deducted from LT bill to
calculate Bill payable amount. In case of bricks manufacturers
additional charges (which ever in force) will be collected.
10. Gram Panchayat subsidy:
Gram panchayat subsidy is provided on Motive power meter which is
used to supply water. Consumption recorded on this meter is fully
subsidised by Govt of Gujarat. Gram panchayat will be required to pay
energy bill for lighting meter only.
11. Companys own consumption:
The Govt duty on energy bill is different. It is calculated paisa/ per unit
instead of percentage basis. Vacant company quarters will be billed as
per normal practice.

Page 22 of 41
12. The Debit/Credit memos generated in case of:

1 Customer Complaints.
2 Stop meter assessment bill.
3 Meter Reader complaint.
4 Wrong Rate applied (Ex: In case of category change).
5
Change in Govt Duty.
6 BHP benefit to Agriculture customers.
6.1.8
Existing Billing process in TPL (Surat):

In normal Energy billing process, after uploading the Meter reading
results to the system, billing is done as per the current tariff through
Mass Process. Some cases are considered as a special case (Ex: In HT,
Wind Farm Generation Unit Credit) and we do Individual billing.
Special cases:
1. Closed (Lock) Premise assessed billing:
In normal energy billing if the consumption determined is for closed
premise, then assessment billing considered as per the following
steps.
1. 1st Month - Normal calculation procedure for the consumption
recorded as per previous billing cycle.
2. 2nd Month (and subsequent months ) If reading received,
Calculation of chargeable units are as under :
a. Chargeable units ( if positive ):

Page 23 of 41
i. Total units = Current reading Last available regular

reading
ii. Chargeable units = Total units charged units
(previous month)
iii. Calculate bill as per tariff applicable without giving
slab benefits.
b. Chargeable units ( If Negative):
i. Total units = Current reading Last available
readings
ii. Chargeable units = Total units charged units
(previous month)
iii. Here
this
Calculation
will
is
be
to
negative.
be
done
Ignoring
this
considering
bill
ZERO
consumption.
iv. This will continue till consumption become positive.
In this case Bill amount will be adjusted in next energy bill.
3.
2nd Month - If reading not received, than charge as per last

actually recorded non Zero consumption (With in 6 month).
All closed assessed bills will be considered as revenue.

2. Stop meter/Defective meter assessed billing:
1. In case of Stop Meter: If reading reason is Meter Slow or Meter

Defective, bill is generated with the estimated consumption.
2. In case of Meter Change :
a. Total consumption = Old meter consumption + New
meter consumption.

Page 24 of 41
b. Prorated consumption= (New meter Consumption / no of

days) * actual billing days.
c. Whichever is higher consumption by comparing above
two consumptions is considered.
3. Pending (Left out services):
Bill is not issued only in case where reading date and

connection date are same
All stop/defective meter assessed bills will be considered as revenue.
3. HT Wind power concessions:

In case of wind mill owner who supplies power to GEB and in turn GEB
give us credit in import bill for 96% of units provided to the GRID. Here
we calculate HT consumption after deducting the credit given by the
GEB. HT bill is calculated as per HT tariff for net consumption.
4. HT Billing (In case of 2 meters - for calculation of Govt

Duty):
In case where Electricity duty concessions are given for certain
type of plant/premise, we fix 2 nd sub meter to calculate
consumption. Here we calculate consumption of main and sub
meter separately .Here we have two types of Govt duty. One is
for sub meter and second one is for differed consumption (main
meter consumption sub meter consumption).
6.1.9
To be Process:
1. Closed Premise assessed billing:
Dynamic Periodic Control a standard SAP ISU functionality will be
enabled to meet TPLs requirement for closed premise billing.

Page 25 of 41
Dynamic Periodic Control:

This functionality can be used to settle the billing documents
generated in estimated period.
In regular meter reading whenever a closed premise is reported,
meter reading for that period will be estimated as per standard SAP
ISU estimation process (refer PDD MSD.05.05. Meter reading
Validations and Estimations). Billing will be done as per estimated
consumption and posting of these estimated charges will be in
revenue account.
When an actual meter reading is recorded
DPC will do the billing, taking reading from previous actual to current
actual and will credit the selected charges raised for all estimated
billing documents, in current month billing document.
This process will be followed for any number of estimated periods.
Billing of estimated consumption in case of civil disturbances and
water logging etc. will be as per closed premise billing only.
In case of genuine lock (permanently closed services) billing will be
done as per available meter readings. (For meter reading process
in this case please refer PDD MSD.05.05. Meter reading
Validations and Estimations).
Dynamic periodic control will only configured for following billing
classes in TPL
ADLT, ADMD and STLT

Page 26 of 41
2. Stop & Defective meter billing:

When any stop or defective meter is reported, billing will be done as
per the recorded consumption. If meter reading not available then
billing will be done with zero consumption (To be provided by the
device management) and in some cases where meter reading is not
available bill will not be raised. For this cases meter readings should
be implausible and user will decide whether to release it for billing or
not.
For more details on validations of meter readings please refer
PDD MSD.05.05. Meter reading validations and estimations.
In case of first bill after changing the stop or defective meter, billing
will be done on basis of total consumption recorded in old meter and
new meter.
A separate provision will be made to raise a credit or debit bills under
stop meter assessment billing through SAP ISU Manual billing process
with necessary development as per the requirement of TPL.
Steps involved in stop /Defective meter assessment process.
1. All meter replacements for any reason will be done through creating
CS order
After replacement of such meters the same order will be routed to
respective department for stop/defective assessment process.
2. Responsible employee/executive will take a decision whether to
carry out assessment or not base on the consumption history of the

Page 27 of 41
service, lab inspection reports, load survey reports, site inspection

results and accuchecking results available if any.
If it is possible to raise stop/defective meter assessment bill,

then a task will be assigned to same order and routed to
responsible person.
If it is not possible to raise stop/defective meter assessment

bill then that order will be closed.
If any further inspection is required to take a decision, then a

task will be added in the same order and routed to
responsible person and will change the status of order to
pending.
The responsible person who received this order will perform

the site inspection and will return the order after entering the
results.
After evaluating the inspection results the same order either

can be routed to assessment adding a separate task or can
be closed without assessment.
3. On receiving the order the employee responsible will do

stop/defective meter assessment billing. A billing document will be
generated after executing the stop/defective meter assessment.
4. Stop/defective meter assessment (DR/CR) billing will be carried out
through SAP ISU manual billing process. A new screen will be
developed for selecting base period and assessment period and to

Page 28 of 41
calculate consumption on %creeping (forward or backward) based on

MTL test report.
5. A provision will be given to workout to be charges units as per %
error. Assessor will be able to change the to be charged
consumption based on number of days considering the vacations and
Diwali holydays and seasonal variations etc.
6. Selection of base period will be as per assessor choice and GERC
guide lines. Assessment period will be restricted to 90/180 days as per
respective rate category and as per GERC guide lines.
7. After completion of billing of stop/defective meter assessment,
concern person will assign a new task in the order and send it to the
respective approving authority based on number of units assessed.
8. On receiving the order, Responsible approving officer will check the
billing document and release the lock for invoicing after necessary
changes, in change billing document mode. Printing of calculation
sheet can be taken.
9. After releasing for invoicing the approving officer will close the
order. Created billing document can be invoiced separately or can be
jointly invoiced with subsequent month billing. If invoiced separately
and the customer failed to pay the amount then the subsequent
month periodic bill will be a notice bill.
10. A letter will be printed and send to customer after invoicing.

Page 29 of 41
11. If customer approached for any change request in stop/defective

meter assessment bill. Concern officer can create another CR/DR bill
as adjustment and reason for creating that can be stored in free text
given in billing document.
12. Same process will be followed for all orders which will come to
accounts department for stop/defective meter assessment, like orders
received from MTL through customer complaints and any other
sources. A separate field will be provided to user to capture the %
error and to calculate the chargeable consumption.
3. Billing in disconnection periods:

In case of disconnection without meter removal, billing will be done as
per the recorded consumption for first month and for subsequent
month if consumption is zero, bill will be raised for other than energy,
FPPPA and government duty charges. If any consumption is recorded
in disconnection period normal bill will be raised for recorded
consumption (with all charges).
In cases where disconnection was done with meter removal, billing will
be done for the recorded consumption in that month (with all
charges). For subsequent months bill will be raised only fixed charges
and will continue for six months (in both cases). After six months
billing will be done for zero amounts.
4. Appling of Government Duty Percentage:

Page 30 of 41
Applicable government duty percentage will be maintained in rate

category facts, as shown below.
Rate
category
Description
Govt.
Duty
AD_RGP
AHMD Residential General
20%
AD_RGP_SEP
AD_GLP
purpose
AHMD Resi Gen Purpose SEP
20%
AHMD
General
Lighting 25%
AD_IGP
Purpose
AHMD
Industrial
10%,0%
AD_CGP
Purpose
AHMD Commercial General
AD_LTP1
AD_LTP2_ID
AD_LTP2_CM
AD_CINEMA
AD_LTPAG
AD_STRLGT
Purpose
AHMD LTP1
AHMD LTP2 Industrial
AHMD LTP2 Commercial
AHMD Cinema
AHMD LTP Agriculture
AHMD Street Light
AD_TEMP_LT
AD_AMC_LT
AD_AMC_STL
AHMD Temporary Supply LT

AHMD AMC LT
AHMD AMC Street Light
AD_LTMD1
AD_LTMD2_I
AD_LTMD2_C
AD_AMC_LTM
AHMD
AHMD
AHMD
AHMD
D
AD_HTMD
AHMD HTMD
AD_HTPS
AD_AMC_HT
AD_TEMP
AHMD HT Pumping Stations

AHMD AMC HT
AHMD Temporary Supply HT
General 25%
LTMD1
LTMD2 for Industrial
LTMD2 for Commercial
AMC LTMD
_HT
25%
Govt.
Duty
(Variable)
-
10%,0%
20%
0%
15%
10%
25%
10%
25%
0%
To be maintained in
Installation facts
25%
Needs to maintain
percentage
Government Duty in
Installation Facts
20%
0%
15%
10%
25%
10%
Needs to maintain
percentage
Government Duty in
Installation Facts
15%
0%
Needs to maintain
percentage
Government Duty in

Page 31 of 41
ST_RESI
ST_COMM
ST_GENERAL
ST_LTP
ST_LTMD
ST_AGL
ST_TEMP
ST_HTMD1
ST_HTMD2
Surat
Surat
Surat
Surat
Surat
Surat
Surat
Surat
Surat
Residential Purpose
Commercial Purpose
General Purpose
LTP
LTMD
Agriculture
Temporary Supplies
HTMD1
HTMD2
Installation Facts
20%
25%
20%
10%
10%
15%
5%
25%
15%
25%
0%
When any particular contract has different government duty

percentage other than government duty percentage mentioned in rate
category for such customers, the value of percentage government
duty has to be maintained in installation facts for same operand.
For example:
If a customer in AD_CGP rate category has different percentage
government duty (other than 25% which will be maintained in rate
category facts). Say, a dhobi has a different government duty
percentage (10%) even though he is AD_CGP rate category, for such
customers a separate government duty percentage has to be
maintained in installation facts level.
Note: for company premises government duty will be calculated based
on billed consumption. Charges of government duty as follows
1.
Residential purpose
0.20Rs/kwh
2.
Commercial
0.40Rs/kwh
5. Billing of HT MES Cantonment services:

All the conditions of billing for HT MES cantonment area services will
be configured in respective schema. The requirement of deduction of

Page 32 of 41
consumption of all LT services existing in that area (private

bungalows) from one HT service will be done through development of
variant program.
As per the development all the LT services (Private Bungalows) in
cantonment area will be tagged separately. Developed variant
program will be used in schema designing which will get the total
consumption of all LT/LTMD MES cantonment services (which are
tagged) and deduction of this consumption will be done.
6. Billing when Price changes in previous dates:
Whenever there is a price change occurs in previous dates, all the
effected changes need to be recalculated and posting of the changes
should be done in current month as a debit or credit amount. To meet
this requirement Adjustment reversal functionality will be used.
I.
As per adjustment reversal, a billing document can be reversed

without reversing the invoicing document.
II.
Do necessary changes and execute billing again.
III.
Execute invoicing for these billing documents along with current

month billing document.
To do these adjustment reversals in mass process a program will be

developed.
7. Billing for services having Wind Power compensations
All requirements for billing services having wind power compensation
will be configured in respective schemas. Wind Power units banking
(storage) will be done in

Page 33 of 41
SAP Material management and payment of wind power units will be

done in SAP FICO. (For more details please refer PDD
MFCB.07.01Manage Power Purchase from Wind power
generators and power purchase through Open Access).
8. Agriculture Services:
Agriculture services will be billed as per the company agriculture tariff
(rate category) AD_LTPAG. All the agriculture customers having
government subsidy will be flagged separately and BHP tariff (Rate)
will be activated and will be billed as per that tariff. BHP subsidy will
be configured as per the existing calculation logic.
9. Government Duty Deferment:
Calculation logic of deferment government duty will be developed in
respective schemas and posting in to concern ledgers will be done
through invoicing.
Deferment time limit and percentage of deferment and amount limit
needs to maintained in customer master data in Utility installation
facts.
In case of amount limit assessed bills should not be generated.
(For more details on account maintenance please refer PDD
MSD.04.05 payments)
10. Billing Process in case of Rate category changes:
In case of rate category changes within a billing period, calculation of
charges will be done as per time slice.
For example:

Page 34 of 41
Billing period is from 17.04.2009 to 16.06.2009 and rate category has

changed on 15.05.2009 from RGP to CGP. Billing will be done as
1.
17.04.2009 to 14.05.2009 under RGP tariff
2.
15.05.2009 to 16.06.2009 under CGP tariff
Billing calculation will be done automatically by taking time slice into

consideration.
11. Revenue Guarantee billing:
Revenue guarantee/Special security deposit will be accepted at some
% of service line cost or consumption of units per KW of contracted
load at the time of new connection.
For more details please refer PDD MSD.02.01. New connection
LT and MSD.02.02 New connection HT
Normal period of guarantee revenue will be in terms of units
(consumption) or in terms of company revenue for 24 months.
Company revenue =
Fixed charges + Energy charges + FPPPA for
LT services and
For HT
Company revenue =
time of use charges
Demand charges + energy charges + FPPPA +

+ PF adjustments.
Operands showing cumulative consumption and company revenue

have to be maintained in installation facts.
On completion of revenue guarantee period, if consumption is less
than guaranteed consumption then the amount for balance units will
be calculated and debited in the regular bill. If company revenue
generated is less than the guaranteed amount then difference amount
will be debited in the regular bill.

Page 35 of 41
(For more details on refunds please refer PDD MSD.04.02

Refund process.)
12. Other Billing Process:
All the special cases other than mentioned above will be configured as
per the TPLs requirements.

Page 36 of 41
6.2
Flow Diagram
Start
Create meter
reading/Billing
orders
Upload to Data
Loggers
Enter meter
readings in Data
loggers
Download Data
loggers to
System.
Implausible
Check readings &release
Apply Validation
With corrections
Make necessary
Changes in meter
readings
Without corrections
Plausible
meter readings
Execute
Mass/Individual
Billing
Correction required
Make necessary
changes
Other than meter

readings
Document Outsorted
Display document
Check Bill Document
Reverse
Yes
No
No
Execute
Mass/Individual
Invoicing
Release

Page 37 of 41
Invoice Document
Printing
6.3
End
Exception and Variations

While creating technical master data for every customer some
installation facts should be maintained like Contract demand,
Connected Load, Percentage of chargeable govt duty etc.
1 In case Agriculture customers those who are eligible for
subsidy including HT customer a separate fact (check box)
should be maintained in installation facts
2 In case HT services a separate fact (check box) MES
should be maintained in case of MES cantonment services
as billing calculation procedure is different in case of MES
services.
3 In case of Gram panchayat services separate subsidy fact
(check box) should be maintained for those services which
covered under subsidy.
4 In case of sub meters where two or more % Govt duty are
applied need to maintain separate govt duty percentages
for main meter and sub meters in installation facts.
5 In case of Company Own Consumption units and its Duty
calculation is based on paisa/unit instead of % basis.
6 In case of LT service in cantonment area a separate fact
should be maintained in installation facts
6.4
Key Performance Indicators
6.5
Integration Points
SAP ISU-DM:
1. MSD. 05.05. Meter reading estimations & Validations
2. PDD MSD.01.01 Manage Schedule Master data.

Page 38 of 41
SAP FICO:
1. MFCB. 07.01. Manage Power Purchase from Wind power
generators and
Power purchase through Open
access.
6.6
Interface
6.7
Not Applicable
Gaps and Solutions:

Sl.
No
Gaps
1.
In HT Wind power
concessions, Updating
of consumption which
is to given as
concession from MM.
Needed
2.
In Manual billing
process which will be
used for creating and
debit and credit notes.
The provision of
selecting base period
for determining the
assessed consumption.
Needed
Mass Processing of
Adjustment Reversals
in case of price
changes
Calculation of total LT
MES services
consumption.
Designing of letter and
calculation sheet in
SMA
Needed
4
5
Workaround
Enhancements
Needed
Needed

Page 39 of 41
6.8
6.9
Configuration:
Document types
Number ranges for document types
Configuration of rates and schemas as per existing billing

calculation procedures
Reporting Requirement:
1. Rate category wise, Price slab wise Component (charges) sales
and revenue report.
2. Percentage wise Govt duty revenue report
3. Agriculture services wises subsidy units and revenue report
4. Wind power subsidy units report service wise
5. Orders status of stop/defective meter assessment
6. List of supplementary bills raised, revenue and sales
6.10
Change Management
1. Closed meter assessment billing:
In closed assessment billing Ahmedabad and Surat are following
different procedures as discussed above. Both Ahmedabad and
Surat should follow same process. Dynamic periodic control
2. Price Block Adjustments:
Price Block adjustment would be enabled for both Ahmedabad
and Surat. Lower limits and upper limit for Bi-monthly will be 54

Page 40 of 41
and 66 days respectively and 25 to 35 days in case of monthly

billing cycles.
3. Stop meter assessment billing:
Both Ahmedabad and Surat should follow same procedure.
6.11
Authorization
Transactions
T-Code
Execute Individual bill
EASIBI, EA00
Display Billing document
EA22
Execute
individual
overall check
Execute Mass Billing
Execute Mass Billing
Simulation
EASICH
Execute mass overall

check
Individual Simulation
EAMACH
Create Manual Bill
EA16
Change Manual bill

Display manual bill
Outsorting
EA17
EA18
EA05
6.12
EAMABI, EA38
EAMASI, EA39
EASISI, EA00
Roles
Manager (IT/FI)
Asst Manager
(IT/FI)
Executive II
/ I (IT / FI)
System
operator
(IT)
Y
Y
Y
Y
Y
Y
Y
Y
As-Is Reference
As-Is.SD.07.02 Energy billing

Page 41 of 41

Energy Billing PDD for TPL Project

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Energy Billing PDD for TPL Project

Caricato da

Copyright:

Formati disponibili

Project

Version 1.0 (Draft)

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Saichand Dade, Srinivas Punati, Kiran kumar Potti,

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Developing and Updating the Business Blueprint

Document Sign Off

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Document Sign-Off Sheet

Torrent Power Ltd:

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

WHAT IS THE BUSINESS BLUEPRINT?...............................................................................................4

DOCUMENT SIGN-OFF SHEET................................................................................................5

BUSINESS PROCESS DESCRIPTION:...................................................................................................9

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Billing of different class of customers like LT, LTMD and HT

periodic monthly and Bi-monthly billing cycles

Billing for electricity division.

Numerous bill forms.

Validation of billing documents and bills.

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Billing uses meter reading results to determine the evaluation basis

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

This document, as mentioned earlier in the Section 2.1, records and

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

The actual contract billing (Energy Billing) is performed with various

Periodic billing Execution:

A billing order has to be generated for every contract with reason

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Meter reading results have to be entered into the system.The actual

After billing document generation that will be invoiced, in the invoicing

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Portions and their parameter records (Monthly/Bi-monthly reading

Create individual bill:

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

It is possible to make a selection of installations according to multiple

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Reverse billing document:

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Meter reading is wrong

Wrong rate is applied

Incorrect billing period

Create manual billing:

Generate billing documents for a new contract.

Blueprint Phase: Process Definition Documents

Sunday, July 17, 2016

Use manual billing alternatively or in addition to automatic

Manual billing supports the following functions:

Automatic price determination