SAP ISU

1. SAP & ISU Overview

2. Creating the Master data (BMD & TMD)

3. SAP ISU Device Management

4. SAP ISU Contract Billing

SAP & ISU Overview
• Overview on ERP
• SAP R3 Architecture
• SAP Project phases
• System landscape
• Overview on SAP ISU
ERP Overview

 It is an industry term for the broad set of activities that helps an

organization manage its business.

 Its goal is to facilitate the flow of information so business

decisions can be data-driven.

 ERP s/w suites are built to collect and organize data from various
levels of an organization to provide management with insight into
key performance indicators(KPI’s) in real time.

 A KPI is a business metric used to evaluate factors that are

crucial to the success of an organization

 It helps administrator monitor and manage critical components of

a business through series of interconnected executive
SAP Overview

System Application and Products in SAP has a very high level of integration
 data processing  among its individual applications

It is a company as well as an ERP Provide customers with the ability to

 software  interact with a common database for a
comprehensive range of applications

Started in 1972 by five former IBM SAP ECC-6(Enterprise core

 employees  computing) is the latest version of SAP
System Landscape

sandbox

Developme Productio
Quality
nt n
 FEATURES

Basic functions  Device Management


• Manages addresses and regional • Manages the installations, meter reading, and
structures the certification of all devices for a utility
• Generate schedules for meter reading, company
budget billing and billing.

 Billing
• Billing the standard divisions: Electricity, gas,
Master Data water/waste water, district
 heating, and multimedia service
• Manages data that remains fixed for long
periods of time.
• Business partners, contracts, contract
 Invoicing
accounts, connection objects (buildings
• Group services and invoice them on one bill.
and real estate) and the premises, • Also use Invoicing to calculate and charge
installations, and device locations duty, fees, and taxes.
Creating the Master data (BMD & TMD)
• Business Master Data • Technical Master data
• Business partner • Connection Object
• Contract Account • Premise
• Contract • Installation
Master Data

 Business master data

 Business partner
 Contract account
 Contract

 Technical master data

 Connection object
 Premise
 Installation
Business Master Data
Business Master Data: Any master data that is used for billing customer for the services are grouped under business data
• The customer’s account: the • An agreement between the
management of the customer business partner and the utility
• Business Partner is driven by the contract company
• A person or a legal entity account • Links a contract account to an
• billing method, payment installation
with whom you have a
method, collection method • It is created automatically
business relationship • Account in which posting data when move-in is done
• Could be Person or for contracts or contract items
organization or a group to for which the same • Transactions:
whom utility services are collection/payment ES21 : change
provided agreements apply are ES22 : Display
processed.
Transactions: •
FPP1- Create • Transactions:
CAA1- Create
FPP2 - Change CAA2 - Change
CAA3 – Display
FPP3 – Display
• Contract
• Contract account
Technical Master Data
Technical Master Data: Any master data that is used for actually providing the services are grouped under Technical
data
apartment or factory. • These are locations within the
Connection object:
• A premise can have several utility connection objects where devices
• Combined with the premise,
installations. can be installed.
constitutes the link between the
• The premise is allocated to a • This means that the exact
installation for billing and the
postal regional structure. connection object and to the location of an installed device is
address of that connection determined using the device
• It is usually a building, but can
object. location
also be a piece of property or
other facility, such as a fountain Transactions:
or a construction site. Transactions:
Transactions ES60 - Create
ES55 – Create ES61 - Change ES65 - Create
ES62 - Display ES66 - Change
ES56-Change
ES67 – Display
ES57 – Display
• Premise:
• Enclosed spatial unit that is
supplied with energy, such as an Device Location:
Technical Master Data
• Installation: Groups together the devices and registers that belong to the same division and are allocated to the
same Premise and that are therefore billed together. One premise can have several different installations. These
Installations can refer to the same or different divisions.
• Transactions:
ES30 - Create
ES31 - Change C.O
B.P
ES32 - Display

C.A Premise

Move-in D.L

Contract Installation POD

Device
Category

Device
Device installation
SAP ISU Device Management
• Creating Device
• Device installation
• Reading meters
• Overview on AMI
Introduction
• Device

• Manages technical data, installations, meter readings, and the inspection and certification of device.
• IS-U/CCS Device Management includes device technology, device installation, meter reading as well as the inspection and
certification of devices.
Device Technology- Device category and Device
• Device category:

 Grouping together of devices with the same technical characteristics (data).

 Examples include single-rate meters and double-rate meters.
 Device category corresponds to material in the
• Materials Management (MM) application component.

• Transactions :
• Eg01- Create
• Eg02- Change
• Eg03- Display
Device

 Devices are physical objects.

 The device is identified by a unique material and serial number combination to distinguish it from other pieces of
material that may have the same serial number.

 Device corresponds to equipment in the Plant Maintenance (PM) application component.

• Transactions :
• iq01 : Create
• iq02- change
• Iq03 – display
MRU and Scheduling

Portion: The portion groups utility contracts according to regional and organizational criteria for billing purposes.
Transactions:
• E41B : create portion
• E41C : change portion
• E41A : display portion
• E41E : delete portion

Meter reading unit: A meter reading unit groups together installations (and the devices and registers installed in them)
according to regional criteria for meter reading purposes.
Transactions:
• E41H : create MRU
• E41G : change MRU
• E41F : Display MRU
• E41I : delete MRU
Scheduling: Scheduling groups the sub-division of the service territory into portions (billing units) and meter reading units
in the system, and generates dates for the following functions:
 Meter reading
 Billing
 Creation of budget billing amounts

Transactions:
•EA43 : Portion or MRU create
•E43A : create Portion and/or MRU
•EA3B : create All meter reading units of a portion
•E40B : Change Schedule records
•E40A : display schedule records
•EA44 : Delete schedule records
•EA44M : Delete multiple entries
Device Installation
• Device
 Allows to Install, remove, and replace devices
 we establish or terminate a link between a device and a device location (technical view) and an installation (billing
view).

Device Install:
 In this component an initial or additional installation of a device in different ways is possible.
 In the case of a technical installation , a device is linked to a device location. In the case of a billing-related installation ,
the device is linked to a utility installation. A device must first be installed in a device location before it can be allocated
to several installations.
 Full installation enables you to link a device to both a device location and a service installation in one step.
• Installation

A device can be installed in the following ways:

• Technical installation only, for example if a meter is not to be billed. This would apply in the case of a control meter or a
meter that belongs to the utility company.
• First technical, then billing-related installation, for example if
Meters in an apartment building are installed first and assigned to apartments later, Both steps are carried out by different
agents
• One technical installation and several billing-related installations. This would apply in the case of a pressure regulator or
an ARCR that controls several installations.
• Full installation, as in the case of a single-family home.
Transactions:
• EG33 : Technical installation
• EG34 : Billing related installation
• EG31 : Full installation
• EG51 : Technical reversal
Terminology
 Advanced Meter System (AMS) - Head end system and network that connects the meter with the MDUS.
 Meter Data Unification System (MDUS) – System that stores and processes detailed meter data, provides the data to other
subscribing systems and users, stores non-energy event data, and executes/relays remote meter processes/calls from the
CIS.
 Advanced Meter Capability Group (AMCG) – Assigned to a meter, this grouping indicates which advanced meter remote
capabilities are supported by the meter.
 Advanced Meter System Capability Group (AMS CG) – Assigned to a meter, this grouping indicates which advanced meter
remote capabilities are supported by the AMS that the meter connects with.
 Advanced Meter Capability Group Determination Group (AMCG DG) - Assigned to a device category, this determination
group restricts which advanced meter capability groups (AMCGs) can be assigned to the related devices.
 Advanced Meter System Determination Group (AMS DG) - Assigned to a device category, this determination group restricts
which advanced meter systems (AMS) can be assigned to the related devices.
SAP ISU Contract Billing
• Billing Introduction. • Rental Billing
• Billing Master Data Creation • Streetlight Billing
• Creating Individual Bill / Mass bill
• Billing procedures and special function.
• Invoicing Introduction.
• RTP Billing
Billing - Introduction

 The Utility services of a company are calculated in IS-U Billing.

 Billing is based on the universal Billing Engine.
 Billing period is flexible based on monthly, season based, Interim etc.
 In billing, the most important business objects are Installation and device while in invoicing it is Contract Account.
 Billing is flexible for all the divisions like electricity gas and water.
Bill Creation Process
Bill Creation Process

Plausible Meter
Readings received for
billing

Bill
Billing OK Invoicing OK Print out

Outsort Outsort

Checking
OK OK
Of Billing Release Checking
Release
Of Invoice
Document
Document
Not
OK Not
OK

Reversal

Reversal
Billing Master Data

 Billing master data controls contract billing.

 This master data stores the rate structure that contains the billing rules.
1. Billing Class:
• Classifies the installation for billing.
2. Rate Type:
• Used to classify Registers, Device , Rate category and Installation for billing.
3. Price:
• The actual values are stored in the price.
• Price Type : Standard , Block and Scale price.
4. Operand:
• Operands link value to be billed and variant programs.
5. Variant Program:
• Variant programs are small, independent ABAP programs and perform elementary
calculation steps.

6. Rate:
• It stores the billing rules which are executed during the billing run.

7. Fact Group:
• It enables different operand values to be used within one rate.

8. Schema:
• Structure that defines the order in which the variant program for rate must be executed.

9. Rate category:
• Classifies the installation for billing, contains one valid billing schema.
• Rate category + Rate type during Rate determination = Rate.
Create Individual Bill

T-CODE: EASIBI
Billing v/s Invoicing

• In IS-U, the billing process includes Billing and Invoicing.

• In Billing a bill document is created for each contract.
• In Invoicing, the billing documents of a contract account are grouped
together into an Invoicing document.
Billing Procedure
1. Periodic Billing:
• Periodic billing is consumption billing that is performed on a regular basis this can
be every month, every two, three, four, or six months, or annually.

2. Interim Billing:
• Interim billing is not subject to the scheduling function.
• You can initiate it at any time in response to a customer inquiry.
• The subsequent periodic billing begins at the time of the interim billing.

3. Final Billing:
• Final billing is initiated for a customer move-out, a service territory transfer, or
manually when requested
Billing Special Function
1. Billing Simulation : T-CODE : EA00
• Checking Billing and Invoicing without actually billing a site.
2. Joint Invoicing: T-CODE: EASIBI
• Invoicing two or more contracts together.
3. Reversing a Bill document: T-CODE: EA20
• Reversing a bill document created.
4. Reversing a Print document: T-CODE: EA13
• Reverse both bill and print document.
5. Billing Out sort: T-CODE: EA05
• Tolerance limit of a bill amount.
Invoicing - Introduction

 Group Invoicing orders and billing documents from contracts in a contract account into a joint bill.
 Post documents in sub ledger Accounting
 Process budget billing plans
 Creates Open item in FPL9.
 Supports determination and charging of taxes, charges and duties.
 Prepares data for Bill printout.
Billing v/s Invoice Out sort