03 - AECS - SAP - ISU - Device Management - Bootcamp - 2016 - V1.0

AECS IS-Utility Bootcamp
Device Management Overview
Strategy | Consulting | Digital | Technology | Operations

Copyright © 2015 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.
Introduction
• Name
• Background
• SAP Experience
• Current Project and your role
• Expectations
• What have you heard about SAP IS-Utility?
Copyright © 2016 Accenture. All Rights Reserved.

Objectives
At the conclusion of today’s session, you will be able to:
 Describe the Characteristics of a Device

 Describe Common Energy Terms Used by Utilities
 Describe Device Movement
 Describe Meter Reading Units & Portions
 Describe the Overview of Meter Reading
 Describe the Overview of Meter Reading Validation
 Describe the concept of Meter Reading Estimation
 Describe the concept of Energy Data Management

Agenda
• Device Management Overview
• Device Technology
• Device Movement
• DM – Meter Reading
• DM – Meter Reading Estimation
• Energy Data Management
• Workshop

Key Concepts
• Industry Solution Utilities / Customer Care & Service System (IS-U

CCS)  SAP Product
• IS-U- Industry Solutions for Utilities.
• CCS- Customer Care Services
• IS-U CCS- Customer oriented software for customers of a utility

company.
• The greatest advantage IS-U CCS is that, it is an Integrated

system.

Functional Areas of CCS
CCS
Customer
Customer Device Relationship
Billing Finance
Service Management Management

Device Management
Device Management
Technical Device Device

Meter Reading
Master Data Relationship Movement
• Connection Object • Scheduling • Device characteristics • Installation

• Premise • Validation i.e. Register Group, • Replacement
• Device Location • Estimation Winding Group, Device • Removal
• Installation • Manual input of Category, Device
periodic & aperiodic • Maintain device
meter reading relationship

Interaction with other Modules
Device Management Billing

Customer Service • Utility Installation • Billing Period
• Business Partner • Meter Installation, • Rate
• Contract Account Removal, Replacement • Consumption
• Service Orders • Scheduling
• Meter Readings Financial Contract
Accounting
• Security Deposit is
based on installation
type

Agenda
• Device Movement
• Workshop

Device Technology Overview
Material
Description
SIE-DTZ 0815
Register Register
Group
Meter
reading
Device Category
Data
Device Number Device Data

(Serial Number)

Device Characteristics
• Device Characteristics covers entering and managing various

properties of devices in the system.
– Basic Device Category : Defines the type of Device based on its

primary usage. Like Meters and Transformers.
• Example meters are used to measure usage of energy
• While Transformers are used to step up and step down current and
voltage
– Device Category : Groups devices as per more specific characteristics.

Like 1 Phase meters, 3 Phase meters and CT/PT operated Meters.
– Devices : They identify the actual meter or transformer in the system.

Device Characteristics
Basic Device
Category
for example, meter, METER
Transformer
Device Category
for example, single phase
meter
1 Phase Meter 3 Phase Meter CT/PT Meter
071 61 92
0 539 802
0 716 192
125.256.01 071 61 92
053 98 02
0 539 802
125.256.01
Devices 125.256.01

Device Category
• Groups devices that have the same technical

properties (the same data) Basic Device
Category
• Is classified by the basic device category for example, meter
• Corresponds to the material in the Logistics

(LO) component Device Category
• Can also be a combination of different basic for example,
double-rate meter
device categories
071619 2
053980 2
071619 2
053980 2 125.256.01
0716192
125.256.01
Devices 0539802
125.256.01
0716192 0716192
0539802 0539802
125.256.01 125.256.01

Definition of Device Category
Device Category
- Groups together devices

with the same feature
- Managed as Materials
with material numbers

Definition of Device
Device Category
Device
- Is an instrument used for measuring

consumptions, processing data or
controlling and protecting other
equipment's
- Managed as pieces of equipment's

with serial numbers

Definition of Register
Device Category
Device
- Used to meter consumption, Register

energy etc. Is the actual
equipment or the display of the
electronic device
- Identified as a register number in

the device

Device Relationship
• Every Device Category has a related Register Group or a Winding

Group attached to it.
• Register Groups : Defines type and number of registers for a

meter.
• Winding Groups : Defines relationships between primary and

secondary coils of a transformer.
Register Winding
Group Group
Device
Category

Register Group
Technical Groups for Device Category – Register Group
l Registers:
 Measure consumption and energy
 Can exist physically or as a display
in electronic devices
l Register Group:
 Groups together the registers of a
device
 Can cover several divisions REGISTER
categories
 Can be assigned to several device
categories
 Reference register relationship
 Register group data is merely default
data and values can be changed as
pleased during an installation or
modification

Register Data
General
• Register category Meter Readings
• Register type (time zone)
• Pre-decimal places • Meter reading recorded
• Decimal places • Estimated meter reading
• Multiple allocation
• Quantity unit
• Register code, such as Meter Reading
reactive energy or active • Reason
power Register • Type, meter reader
• Transformation ratio • Date
• Status
Register relationships
• Number of meter reading
results per meter reading • Relationship type
• Indicator: nonmetering • Relationship register(s)
register • Operation code
Technical Data Process Data

Units of Measurement
• The Core SAP and industry standard, they sit under the R3 IMG
(Implementation Guide)
 Implementation Guide for R/3 -> General Settings -> Check Units
of Measurement
• Example:
– kW : Kilowatt  electrical output = 1000 W
– kWh : Kilowatt hour  electrical (active) power demand =
1000 Wh
– kV :Kilovolt  unit for voltage = 1000 V
– Kvar: Kilovar  electrical (reactive) power = 1000 var
– Kvarh: Kilovar hour  electrical (reactive) power = 1000 varh
– m³ : Cubic meter  gas volume

Dimensions
 KWh (kilowatt-hour):  The basic unit of electric energy used to measure

consumption. Think: Odometer
 Demand (kW):  ‘Active/real’ electric power. Instantaneous measure of

demand on electricity. Think: Speedometer
 Reactive Power (kVARH):  ‘Reactive power’. Measure the amount of power

wasted due to reactive properties of the equipment (i.e.
motor). Think: Wasted Energy
 Power Factor:  Measure of how effectively electricity is being

converted. Think:
Kvarh
0 to 1
Kwh

Create / Change / Display Register Group
• SAP MENU PATH – Utilities Industry -> Device Management ->

Technology -> Register Groups
– Create Register Group – Transaction EG04

– Change Register Group – Transaction EG05
– Display Register Group – Transaction EG06

Create Register Group - Data
Field Description Field Content Action

Register Group Your Initial_123
Division Cat 01 Enter
Search Term
RC - (Register Category)
AF –(Reactive, apparent or active registers)
RT – (Register Type)
DP – (Decimal Places before the decimal point)
PD – (Places after the decimal point)
UM – (Unit of Measurement)
RI – (Register Identification)
Reg. Factor

Create Register Group cont.

DT – (Register Display Type)
No - (Number of MR)
Register Code

Introduction to Device Category
• Serial number:
Sie-970701-503
• Manufacturer: Siemens
• Production year: 2002
• Valid from 07/01/2002
• Serial number:
AEG-980101-125
• Manufacturer: AEG
• Production year: 2005
• Valid from 01/01/2005
• Serial number:
LGY-980701-300
• Manufacturer:
Device Landis&Gyr
Single-rate meter that is subject to certification
Plastic housing and external seal • Production year: 2007
Six pre-decimal places, one decimal place
• Valid from 07/01/2007
Device Category

Basic Device Categories
• Meters measure consumption-dependent resources (that is,

electricity, gas, water, heating)
• Transformers (such as, voltage transformers, current

transformers)
• ARCRs (audio frequency ripple control receivers) transmit

information across the grid (for example, to control switching of
rates in the case of off-peak storage heaters)
• Remote meters enter consumption values over distances (for

example, meters that can be read via modem)

Device Category Attributes-Function Class
Define Function Classes
• Function classes are entered in the master record of a device category and
provide a classification of the device categories as well as devices in the
category with regard to their function.
• In addition to the function classes, it is possible to reduce the device

categories using the classification criterion construction class with regard to
the description. A corresponding function class must first be maintained in
order to completely define a construction class.

Device Category Attributes-Construction Class
Define Construction Classes
• In this activity you define the construction class dependent on the function
class and division category. In combination with function classes,
construction classes categorize device categories according to description
and function.
• It is possible to use one function class in several construction classes, but

you cannot define different functions for one construction class.

Construction Class & Function Class
Function Class
Trivector
Meter
Construction Class
Analog Digital
Device Category
Cat. Cat. Cat. Cat. Cat. Cat.
1 2 3 7 8 5

Device Category Data
Basic Data General

• Description
• Description of material • Function class
• Price rating • Construction class
• Allocated documents • Price class
Certification
Device • Certification requirement
Category • Certification periods
• Inspection point group
Planning
• Register group
• Procurement planning • Winding group
• Costing • Type of measuring and
• Forecasting transformation ratio
• Command group
MM Data IS-U Data

Windings
• Windings:
– Define the transformation ratio of transformers
– Are divided into primary and secondary windings
• The winding group:

– Groups windings that apply to the same device or device
category
– Contains at least one primary and at least one secondary
winding
– Is required if transformers are used

Winding Group
• A winding is a wrap of wire in a transformer that steps down the

current flowing through to the meter.
• A winding group is a group of windings which applies to one or
more devices or device categories. This group contains at least
one primary and one secondary winding.
• Winding groups are required in order to create device categories
from the basic device category "transformer.”
• The PT/CT ratio is the quotient of the primary current and the
corresponding secondary current, and of the primary voltage and
the corresponding secondary voltage, of the windings.
• The PT/CT ratio is used to determine the billing factor (that is, the
quotient of the PT/CT ratio and the transformation ratio). The
transformation ratio is calculated using the current and voltage
values stored in the register group (for each register) and in the
device category

Create / Change / Display Winding Group

Technology -> Winding Groups
– Create Winding Group – Transaction EGW1

– Change Winding Group – Transaction EGW2
– Display Winding Group – Transaction EGW3

Create Winding Group

Winding Group * Your Initial_(LCT / CT / PT) Enter
Search Term
Transform type *
Winding Category
Winding Type
T Voltage – Primary
– Secondary
T Current – Primary
– Secondary
Primary winding indicator
Secondary winding indicator

Elements of Device Category
Technical groups can only be allocated to device categories belonging

to certain basic device categories
Material
MM Component
Register Input/Output
Group Device Group
Category
IS-U Component
Command Inspection
Group Point Group
Winding
Group

Elements of the Device Category: Valid
Combinations
Relevant to billing
Register Winding Command Input/Output Inspection
Not relevant to billing Group Group Group Group Point Group
Meter
Transformer
ARCR
Remote Meter
Counter
Corrector
Pressure Regulator

Creating Device Categories without a Reference
Material

Creating Device Categories with a Reference
Material

Create Device Category in Material
Management
• SAP MENU PATH – Logistics > Material Management >

Material Master > Material
– Create Material – Transaction MM01

– Change Material – Transaction MM02
– Display Material– Transaction MM03

Create / Change / Display Device Category

Technology -> Device Category
– Create Device Category – Transaction EG01

– Change Device Category – Transaction EG02
– Display Device Category – Transaction EG03

Create Device Category

Device Category * Your Initial_(MTR / LCT / CT /
PT)
Division * 01
Basic Device Category * Meter / Transformer Select
Do you ant to create a material in MM? Yes
Device Category Description *
Function Class
Construction Class
Register Group / Winding Group *
Type of Measurement *
Certification Requirement *

Create \ Maintain Function & Construction Class
• To maintain function classes, choose:

IMG Path -> UTILITIES -> DEVICE MANAGEMENT -> TECHNOLOGY ->
DEVICE CATEGORY -> DEFINE FUNCTION CLASSES
– Example: Three-phase current 1 | 01
• To maintain Construction classes, choose:

IMG Path -> UTILITIES -> DEVICE MANAGEMENT -> TECHNOLOGY ->
DEVICE CATEGORY -> DEFINE CONSTRUCTION CLASSES
– Example: Direct 10/30 220 0001 02
Direct 10/40 220 0001 01

Device
• Measures consumption
• Processes data
• Identified by material and serial
numbers
• Managed in PM as equipment.

Basic Device Characteristics

Elements of Device
General
• Equipment type General
• Inventory • Material and serial no.
number • Descript., user-defined
• Reference data text
• Location data • Time slices
Activities Activities
• Maintenance orders Installation and removal
• Service orders
• Messages
Device Modification and disconnection
Certification
• Capacity planning Meter reading
Plant Maintenance Device-Specific Data

• Maintenance plant • Group data, prod. year
• Maint. planning plant • Manufacturer, cat. desc.
• Maint. planner group • Ownership status
• Main work center • Certification data
PM Data IS-U Data

Create / Change / Display Device

Technology -> Device
– Create Device – Transaction IQ01
– Change Device – Transaction IQ02
– Display Device – Transaction IQ03
List Editing (Mass creation)
– Create Device – Transaction IQ04
– Change Device – Transaction IQ05
– Display Device – Transaction IQ06

Create Device

Device Category (Material) Device Category created by you
Device (Serial Number) * Your Initial_(MTR / LCT / CT /
PT)
Category “ I “ IS-U Equipment Enter
Manufacturer
Construction Year *
Valid from date *
Register Group / Winding Group * Default from Device Category
Inspection Relevance * “03” Transfer
Press Enter and
Save

Device Classification
• Classification enables you to classify devices and device

categories according to user-defined
characteristics.
• It is a central function within the logistics component of R/3
• It provides scope to perform device analysis according to specific

characteristics.
• Classification can be performed at 3 stages

 Creating / Maintaining Device Categories
 During new goods receipt
 Maintaining of devices

Classification Objects
A class is a group of objects that have the same

Class or similar properties.
An object is a classifiable unit (for example,

Object
material, supplier).
A characteristic describes the properties of

Characteristic an object (for example, meter constant, tracking
indicator, pulse constant).
Characteristic Specification for a characteristic (for example,

Value 5 rev/min, X, 100 pulses).

DM Integration with MM
LO Device Category Requisition

IS-U (Material)
Purchase Order
PM
Goods Receipt
Installation Serial Number = Device

Structure Device Number (Equipment)
Installation Device Inventory

Removal (MM Warehouse)
MM
Goods Issue

Numbers In Device Management
• As the device category is based off a material record and the device
is based on the equipment record, we will review those standard
R/3 data objects. We will also review some of the IS-U extension
related to each.
• The material number is equal to the device category number.

However, the device category fields managed in the material record
are not the same as those maintained in the device category
record. The latter pertain specifically to the IS-U extension of the
standard material record.

Numbers In Device Management
• The material number (Materials Management MM)

– Corresponds to the device category number in IS-U
– Is unique
• The serial number (Materials Management MM)
– Corresponds to the device number in IS-U
– Is not unique in the system
– Is unique within a material or group material
• The equipment number (Plant Maintenance PM)
– Corresponds to the consecutive internal device number for differentiating
devices with the same number
– Is different in every client

Device Procurement
• If you do not wish to implement the Materials Management (MM)

application component, you can create devices directly in IS-U.
You can either create individual devices or use list editing for mass
processing. In both cases the devices are created in the Plant
Maintenance application component (PM) as pieces of equipment
with IS-U enhancements. However, the devices are not maintained
for inventory management in the Materials Management
application component. Therefore, you cannot use the Materials
Management application component for functions such as
ordering, purchasing and inventory management on a quantity and
value basis.
• If you use MM functions, you have to create the devices via goods
receipt in the Inventory Management (MM-IM) component.
The warehouse management system in the Logistics application
component allows you to model more complex warehouse
structures, such as high rack storage areas, in the system.

Serial Number Management
• Material serialization allows you to track objects individually.

• Serial numbers are tracked throughout different business
transactions in Logistics such as:
– Goods receipt
– Goods issue
– Stock transfers
– Sales orders
– Delivery notes
– Service notifications
– Service orders

Review
• Device Management constitutes
– Technical Master data

– Device Relationships
– Meter Reading
– Service Orders
• Technical Master Data is information required for installing a device on

customer site.
• In Device Relationship device related information is maintained.
– Information of devices include information like basic device category,

device category, register groups or winding groups.

Summary of T-Codes
Register Group Material Winding Group Material

(Meter) (Transformer)
EG04 MM01 EGW1 MM01
Device Category Device Category

EG01 EG01
Device Device
IQ01 IQ01
Device Group Full Installation Installation
EG27 EG31

Checkpoint
• Functional Areas of IS-U
 Activity : Name the 4 main Functional areas of IS-U
• Technical Master Data

 Name the 4 core areas of Technical Master Data & the hierarchy
• Device Management Technology

 How many core Device Management areas can you name?
• Register Groups
 When creating a Register Group what level of detail do you
require?
• Winding Groups
 When creating a Winding Group what level of detail do you
require?
• Device Categories
 What is the prerequisite for a device category?
 Can multiple device categories share the same Register Group?

Discussion
• From the ISO Units of Measurement how many can be defined? How are
they categorized?
• Can you create a Device Category for meter without a Register Group?
• What are the different types of registers defined?
• What is the mandatory information while creating device category for

transformer?
• What are the two main Technical Groups for Device Category?

Exercises - 1
1. Find two installations (Electricity & Gas) (ES32), with these characteristics
mentioned below:
• Connected
• With a valid contract
• With a meter installed
2. Create Device Characteristics for Electricity and Gas Meter

• Create Material
• Create Register Group
• Create Device Category
3. Create a new device (IQ01) following these steps:

• Same material from installation’s meter
• Create the device with a valid from date in the past so
you can install it in the past
• Fill in device characteristics that you have created

Agenda
• Device Movement
• Workshop

Device Movement: Business Scenario
Technology Order MM
Goods MM-IM
Goods Receipt MM-WM
Issue
Stock Goods
Retirement Transfer Issue
Inspection
and Installation
Certification Device
Installation
Meter Removal or
Reading Replacement

Device Movement
• Once Technical Master Data is created in the system, a device can

be installed at a device location.
• A service order is created in the system based on which various

activities will be performed.
• Device Installation constitutes two parts
– Technical Device installation

– Billing Related Device Installation
• Once a device is technically installed and billing-related installation is

also performed it is said to be ‘fully’ installed.

Device Installation
• Technical Installation refers to attaching a

device at a device location.
• It refers to the physical installation of a
device.
• Billing- Related Installation refers to
preparing a device that is technically
installed for billing.
• A device will not be billed until billing-
related installation for the device is not
performed.
• Once a device is installed technically and
billing-related, it is said to be fully installed
•We will perform ‘Full’ installation of a
device in a single step

Device Installation
Fields Relevant to Installation

Device Installation
Installation - Period Consumption

Device Installation
The Utility Installation Structure

Device Movement
Device Group
Group of devices that comprise a logical unit
Examples of device groups:

A l Transformer groups are made up of
B current and voltage transformers linked
to each other. Transformer groups have
a single transformation ratio.
C
l Two integrated water meters installed
together. These meters measure
consumption separately. The
consumption from these meters can be
shown separately on the bill, but is
Device
DeviceGroup
Group usually billed together
In this way, devices that belong together to a device group cannot accidentally
be removed or installed separately. Any replacement has to be expressly confirmed

Create / Change /Device Group

Installation -> Device Group
– Create Device Group– Transaction EG27

– Change Device Group– Transaction EG28
– Display Device Group– Transaction EG29

Create Device Group

Device Group * Your Initial_DG
Group Type “0003”
Key Date Current date Enter
Device Serial Number 1 CT serial number (created by you)
Device Serial Number 2 PT serial number (created by you) Enter and Save

Device Installation

Installation -> Device Installation ->
– Full Installation – Transaction EG31

– Technical Installation – Transaction EG33
– Billing-related Installation – Transaction EG34
– Technical Reversal Installation – Transaction EG51

Device Installation – Technical

Device Location / Connection
Object
Activity Date Enter
Device (serial number) Note: Other device
in device group is
also transferred
Activity Reason Next Device
Note: CT and PT in a device group Enter and Save
need to be technically installed
together

Device Installation – Technical

Device Location / Connection
Object
Activity Date
Device (serial number)
Activity Reason
Meter Reading
Period Consumption
Number of days Enter and Save

Installation – Billing related

Utility Installation
Activity Date
Activity Reason
Meter Reading Same as technical installation
Rate Type
Fact Group Enter and Save

Device Replacement
• A device can be replaced with a

device from the same or similar device
category.
• Replacement of a device can be done
based on various reasons.
•These reasons will be mentioned in the
system.
•One example where replacement
would be triggered is if a faulty meter is
found at site and same is reported by
the meter reader.

Device Replacement

Installation -> Device Replacement ->
– Full Replacement – Transaction EG30

– Technical Reversal Replacement – Transaction EG52

Replacement – Full

Device Location / Connection Object
Activity Date
Old Device (Serial Number)
New Device (Serial Number) Enter
Activity Reason
Old Device (Final Meter Reading)
New Device (Initial Meter Reading) Enter and Save

Device Removal
• Device Removal has to be done

technically and billing-related both.
• A device needs to removed bill-
related first and then technical removal
can be performed.
• Once a device is removed bill-related
and technically then device is said to
be fully removed.
• At time of device removal, we need
to enter readings for the device.
•We will perform ‘Full’ removal of a
device in a single step

Device Reversal
Reversal of Installation / Removal / Replacement

Device Removal

Installation -> Device Removal ->
– Full Removal – Transaction EG32

– Technical Removal – Transaction EG36
– Billing-related Removal – Transaction EG35
– Technical Reversal Removal – Transaction EG53

Removal – Full

Device Location / Connection Object
Activity Date
Activity Reason
Final Meter Reading Enter and Save

Summary-Installation/Removal
Process Steps Detailed Steps Reversal
Technical Technical Technical

Full Installation Installation Installation
(EG31) Reversal Reversal
(EG33) (EG50)
(EG51)
Installation
Billing Related Billing Related

Installation Removal
(EG34) (EG35)
Full Removal Billing Related Billing Related

(EG32) Removal Installation
(EG35) (EG34)
Removal
Technical Technical Technical

Removal Removal Reversal
(EG36) Reversal (EG50)
(EG53)

Summary - Replacement
Process Steps Detailed Steps Reversal

Removal Installation
(EG35) (EG34)
Technical
Removal
(EG36)
Full Technical Technical
Replacement Replacement Replacement Reversal
(EG30) Reversal (EG50)
(EG52)
Technical
Installation
(EG33)

Installation Removal
(EG34) (EG35)

Discussion
• What is periodic consumption?
• Give example of fields relevant to device installation.
• Identify different business reasons for device installation, removal

and replacement.
• Identify combinations for device groupings.
• Describe Scenarios of Device Reversal

Exercises - 2
1. Change user status of old device to DISP (available) (IQ02).
2. Check if the installation has pending MR orders / billing orders and if so,
reverse it (EL37)
3. Replace installation’s meter 2 days after the last billing document

(EG30).Enter MR results for both meters
4. Reverse device replacement

1. Billing related removal for new equipment (EG35)
2. Technical Replacement Reversal (EG52)
3. Billing Related Installation for old equipment (EG34)

Agenda
• DM - Technology
• DM - Installation
• Workshop

Meter Reading Process Overview
Meter read schedule Create Meter Download to MR read

reached Reading Order handheld
Corrections
Validations Fast entry / Upload

Integration of Scheduling with Regional Structure
l Shows the order meter reader reads devices from a Meter Reading Unit
l Possibility of monitoring whether there are unassigned devices to meter

reading sequence
Meter
Reading City District 1
Unit A
Street 1
Connection
Street 2 Object 1
Connection Device
Street n Object 2 Location 1
Connection Device Device 1

City District 2 Object n Location 2
Device
Location n Device 2
City District n
Device n

Scheduling - Route Sequence
Meter Reading Unit

City District
Street
Connection Object
Device Location
Device
Connection Object 1
Device Loc.
1 Street 1
Device 1
Device 2
Street route defines the sequence in which the devices in a service

territory are to be read. Doing this can optimize the meter reader’s
route.
Scheduling
• Before actual meter reading process begins, it needs to be scheduled.
• A Factory Calendar is maintained, which specifies the working days and

holidays for the year
• Scheduling needs for both meter reading and billing.
• Scheduling is creation of schedule dates for meter reading and billing.
• For scheduling Schedule Master Records are to be created
• Schedule Records are created on the basis of schedule master records and
creation of schedule records is an annual activity.

Scheduling - Factory Calendar
• The creation of scheduled, service orders and meter reading orders is
based on the Factory Calendar which is set up in the system.
• Factory Calendar is made up of public holidays and company assigned

holidays.
• These holidays can be

1. Fixed public holidays e.g., Independence Day, New Year Day, etc.
which have same date every year or
2. Non fixed holidays for example Holi , for these holidays input is given
before the beginning of each year
• There could be multiple Calendars:

o Public Holiday
o Default SAP Holiday Calendar
o Company’s Calendar

Scheduling - Factory Calendar
Non-Fixed Holiday
10th May 2009
All non-working days

are denoted by red
color
Fixed Holiday
31st December every Year

Scheduling : Portion
Portion 1 Portion 2
• Group of contracts to be Billed 25/1/09 Billed 26/1/09
billed on the same day.

• Portion is sometimes
termed as Cycle.
MRU 1
MRU 3
• Control billing schedule.
• Determines frequency of
the periodic billing.
• Possibly assigned to
MRU 2 MRU 4
several meter reading unit.

Scheduling – Meter Reading Units
• Group of utility Installations that

are in the same region and
read by a certain date.
Meter Reading Unit

• MRU is sometimes termed as
as Book No.
• Make up a Meter Readers’
route for a particular day.
• Form the basis for meter
reading.

Geographical View of Portions & MRU’s
Portions & Meter Reading Units

Scheduling – Schedule Records
Schedule Records
Portion Billing Budget Billing

Dates Dates
Parameter
Record
Meter Reading Meter Reading

Unit Dates
• The scheduling component is used for generating dates periodically

for meter reading, billing and budget billing control.
• The schedule master records for billing are stored in the portion, and
those for meter reading are stored in the meter reading unit.

Object Relationship Diagram

Scheduling - Schedule Records
 Schedule Records are used for planning and controlling the

following functions:
• Meter Reading Order Creation
• Schedule Billing.
 Some Important Scheduling Parameters are
• Schedule Meter Reading Date
• Schedule Billing Date

Scheduling : Meter Reading and Billing Period

Scheduling – Generation of Schedule Records
Schedule Master Records Schedule Records
PORTION-A 02/2003
PORTION-A PORTION-A 04/2003
PORTION-A 06/2003
Generation of
Schedule Records
MRU-A 02/2003
MRU-A MRU-A 04/2003
MRU-A 06/2003

Scheduling – Generation of Schedule Records

Exercises - 3
1. Create a new Portion (E41B)

2. Create a new MR unit (E41H)
3. Create schedule records (E1DY) for Portion created in question 1
4. Create schedule records for MR unit created in question 2 (E1DY)
5. Modify schedule records for MR unit created (E2DY), the scheduled date in
Jan-2015 should be changed to the next day.
6. Allocate the new MR unit for the installation used in Activity 1 (ES31).
Create a new time slice for installation 2 days after the last billing period
billing order
7. Allocate installation’s device on street route (EL40)
8. Update old MR unit (eliminate device from MR route)
9. Allocate device to MR route within new MR unit

Meter Reading Overview

Meter reading Order
Meter Reading Orders are:
 Prerequisite for a Meter Reading
 Display all data needed for meter reading:

 Meter Reader
 Date
 Address
 Expected meter reading.
 Can be printed or transferred to MDE, ITRON.
 Used for monitoring (tracking)

Meter Reading Order
 Periodic (scheduled) Meter Reading Orders are created according to the

meter reading schedule. They are typically generated as a mass order
creation in the daily batch schedule.
 An Interim (non-scheduled) reading is requested by creating a MRO

individually as required.
 The MRO can be for either a billable or a control read
 A MRO is created for each specific register on a device
 When a meter reading order is reversed, all objects that were generated
during creation and meter reading result entry are deleted (MRO, MR Result,
Bill order)

Meter reading reasons
 Periodic/Mass Meter Reading used for several MRU

 monthly, quarterly, yearly etc.
 Aperiodic Meter Reading :
 Interim Meter Reading = 09
 Service Territory transfer with Billing
 Control Reading = 10
 Meter Reading resulting from a process:
 Customer move-in
 Device Removal

Meter Reading Priority and Interval
Meter Reading Priority

• Priorities can be defined for individual meter reading reasons.
• Via these priorities you can define which meter reading reasons cause
suppression of meter reading orders if the meter reading interval already
contains other meter reading orders or results.
Meter Reading Interval
• Period in which only one meter reading and the related billing are to be
carried out.
• The meter reading interval is entered in the meter reading unit.
Blocking Meter Readings
• Blocking of meter readings for specific reasons can be configured in the
system.
• When you enter a blocking reason for an installation, the system does not
generate any meter reading orders for the registers allocated to the
installation during meter reading order creation.

Meter Reading Order - Data elements
Data Specific to Entry Time-Based Data

• Target reading date
• Entry number • Target billing date
• Check number
• Meter reading reason
• Planned meter reading
• Meter reader
• Control group Meter
• MDE number
Reading
Order Meter Reading Data
• Expected meter reading
• Expected consumption
• Upper limit of meter
reading
Data Environment

Meter reading order creation
 Individual (result of customer request)
 Mass
 As per schedule records for periodic meter reading.
 Standard Meter Reading categories:
 Utility company
 Customer
 Estimation

Meter Reading Download & Upload

Meter Reading Download Form
• Uses the Raw Data Interface (RDI) from SAP script
• Print workbench is used to define the RDI download form
• Spool: transfer to a spool or file (depending on configuration settings)
• IDoc interface (intermediate document): used for electronic data interchange

(EDI) between different computers and systems. SAP standard format for
electronic data exchange

Meter Reading Download Interface
• Generation of Meter Reading Orders will be done 1 days prior to actual

Meter Read start date (e.g. for all MRUs which are to be read on 16-20th of
a particular month the corresponding MROs will be generated on 15th of
that month).
• Generation of MROs will be a scheduled background job (i.e will be

automatically done in the system).
• Then segregated data as per Meter reader wise depending upon MRU and
Area code would be downloaded on the scheduled reading day.
• The meter reading orders in the file will be arranged as per the street route
defined in the system.

Meter Reading Upload Interface
• Daily collected meter reading would be uploaded to ISU from CMRI for
validation and screening in ISU.
• Once Meter Readings are uploaded into the system, they are checked for
certain pre-defined validation criteria. If a reading fails any of the criteria, it
become Implausible and it needs to be either released or marked for
provisional or sent for Re-read.
• There could be some cases where Meter Reader brings only the MR note,
all such cases in ISU called Open Meter Reading Orders, these may also be
needed to be marked as provisional or sent for re-read.
• All the above cases can be identified by Meter Reading Status in ISU.

Entry Of Meter Reading Results
 Requirements for Periodic Meter Reading
• Meter Reading Order
• Download of Meter Reading Order
• Upload of Meter Readings into the system

Entry of Meter Reading Results
 Mass entry for periodic meter readings

 Prerequisite: meter reading order creation
 Automatic: Upload using the standard transaction IDoc Type
and EDI Basis
 Manual: fast entry
 Without correction: implausible values are reset
 With correction: validation is possible
 Single entry
 Is possible without previous creation of meter reading order
 Used, for example, in the case of interim and control readings

Fast Entry: Key Fields
 Meter Reading
 Meter Reading Status
 Actual meter reading type, for example:

 Entry by utility company's installer
Entry of Meter Reading Results
 Entry via Internet
 Meter reader
 Notes from the meter reader

 Serve as additional information
 Used for outsorting during validation
 Aid in the correction of incorrect meter reading results
 Can initiate follow-up actions

Meter Reader Notes
 Meter Reading Notes are the Meter Reading Codes that are used
by the Meter Reader in the Current System.
 Meter Reader notes are entered into the system at the time of
entering the Meter Reading Results.
 For Example:
– Code 01 means the normal Meter Reading.
– Code 09 means meter was inaccessible due to some reasons.

Meter Reading Entry
• SAP MENU PATH – Utilities Industry -> Device Management

-> Meter Reading ->
– Single Entry – Transaction EL28

– Fast Entry without correction – Transaction EL20
– Fast Entry with correction – Transaction EL22
– Correction of Plausible reading – Transaction EL29
– Correction of Implausible reading – Transaction EL27
– Reversal of meter reading – Transaction EL37
– Monitoring of meter reading – Transaction EL31

Meter Reading Monitoring
Meter Reading Data

Meter reading
results
Unverified Processing
transfer billable
MDE station
reset
Independent Dependent
checks checks
Meter reading
sheet
Grouping of
registers of
different contracts,
installations
• Single entry
• Fast entry errors / check log

Manual Monitoring
 Monitoring of:
 Schedule records
 Meter reading orders
 Billing orders
How many implausible
Entry
 Meter reading of Meter
results Reading Results
meter reading results
did we have last week?
 Information regarding:
 Meter reading
 Status
 Meter reading reason
 Validation of meter reading results

Automatic Monitoring
• Automatic monitoring of missing and implausible meter reading results
• Follow up actions are started after specific periods depending on status,

meter reading reason and meter reading type
• Follow up actions are defined in SAP enhancements
• If a (further) follow up action is not defined, the result is estimated

automatically
Status 0 01/01: planned reading by customer
Status 1 05/01: reminder User-defined follow-

up actions
Status 2 09/01: meter read by utility company
Status 3 15/01: Automatic estimation

Meter Reading Correction
• Implausible meter readings are blocked for billing by the system

based on certain pre-defined criteria.
• These need to be sent for Re-Read and/or released by the

screening department.
• A Re-read order can be generated to again take readings for

certain meters.
• It is possible to estimate consumption after marking the cases for

estimated billing.

Meter Reading Reversal
• It is possible to reverse a meter readings entered if it not

processed for billing.
• During reversal of meter reading, meter reading order is deleted.
• Billing Order for that reading (if created) is also deleted.
• The Meter Reading Result is deleted.

Summary - Meter Reading
SAP
EL09 / EL01
Main Reasons for
Meter Reading
Reading
Order
01, 02, 03, 06, 09, 21,
Creation
22
EL28 EL16
Download
Manual Meter
Meter Reading
Reading Entry Reading
Order
ELMU
Upload Meter
Reading Results
Validation
EL31 EL27 EL18

Calculation
Monitoring of Meter Meter
and Billing
Meter Reading Reading
Reading Data Treatment Estimation

Meter Reading Validations
• Each meter reading result is checked for plausibility (validated)

• Checks can be configured for individual customers or groups (i.e. MR
validation classes)
• Configurable validations can be defined in Customizing

Meter Reading Validation
Meter Reading Validations fall into the following categories:
• Independent (Variable) Validations. These are validations that are performed

on a register without taking the reading of any other registers into account. The
‘Variable’ part of the name means that these Validations can be switched on or
off by Validation Class.
• Independent (Fixed) Validations. These are validations that are performed on

a register without taking the reading of any other registers into account. The
‘Fixed’ part of the name means that CCS always performs these Validations.
• Dependent Validations. These are validations that are performed on two

registers that have a relationship to one another (for example a power factor
validation must take into account the reading on a kWh register and its
associated kVARh register).

Meter Reading Validation
•What are the validation checks to determine whether or not a

reading is implausible?
•Sequential Checks:
•Check previous year consumption
•Check previous period consumption
•Check periodic consumption
•Exception: Recent changes to periodic consumption value

Fixed Validations
• Validation of previous meter reading

 Is the previous meter reading plausible?
 It is not possible to release a previous meter reading that is
implausible
• Validation of fixed-value deviation
 No consumption for inactive and blocked installations?
• Validation of resetting register
 Is the number of resettings correct?

Variable Validations
• Zero consumption
• Repeated customer meter reading/estimation

 Limitation regarding customer meter reading/estimation
• Absolute/relative/moving tolerance limits

 Comparison period: is the consumption in the expected interval.
• Usage hours compared to previous period/fixed value
• Maximum/minimum contract demand limit
• Meter overflow
 Is meter reading < previous meter reading?

Variable Validations
• Validation classes contain a pool of all possible validations of a

rate; validation classes are stored in the rate.
• Validation parameters, for example:

 Error class: warning and error messages
 Usage hours
 Permitted minimum and maximum demand
• Tolerance limits, for example:

 Error class
 Positive/negative deviation

Meter Reading Corrections
• Correct during entry
• Correct using individual transaction
• Correct plausible results
• Correct implausible results

 Correct
 Release without correction
 Reset
 Create Correction Order
 Estimate

Summary - Meter Reading & Validations
SAP METER READER

Individual Processing Massive Processing
EL31
EL01 EL09
MR Monitor
MR Order Creation
EL37
MR Reversal EL16
Download of MR
MR Order
Order
EL30 EL18 EL28 ELMU
MR
MR Entry (Manual) Upload of MR Results MR Result
Estimation
MR Validation
EL27
Treatment of
Billing and
Implausible
Invoice
MR Results

Exercises - 3
1. Create periodic MR order / billing order for the next available billing period
(EL01)
2. View MR history (EL31) before entering a MR result
3. Enter MR result / MR note (EL28)
4. Release implausible MR results if necessary (EL27)
5. View MR history (EL31) After entering a MR result
6. Simulated billing (EA00) and check if there’s no error
7. Change MR Reading (EL29)

Agenda
• DM - Technology
• Workshop

Meter Reading Estimation
• To estimate meter reading as accurately as possible when actual read is

not required or available
• Estimation is the process of determining the expected consumption for a

register on a specific date (i.e. “forecast period”).
• Estimation is a necessary process for Utilities as it facilitates legal,

operational, and billing requirements.
• Estimation also integrates very closely with the meter reading validation
processes

How IS-U Estimates
• Use of consumption history on installation as basis of estimation
• Depending on the data available, CCS can estimate in three ways:

 Consumption history
 Period consumption
 Reference value
• It is possible to customize an “overestimation factor”.

Estimation of Expected Consumption

Extrapolation Using Meter Reading Results
l Prerequisite: the actual meter reading result must best

reflect the consumption pattern in the period
Rate
Minimum
Weighting
Percentage
Procedure
Portion
Actual
Actual Expected
Expected
Meter
Meter Meter
Meter
Extrapolation
Reading
Reading Reading
Reading
Result
Result Result
Result
Installation Base
Period
Category

Weighting
l Determination of expected values (meter readings for example)

by means of:

Weighting
•Linear weighting
•The linear weighting procedure does not take seasonal fluctuations
into account. For linear weighting, the weighting units are distributed
equally over the year, whereby the system takes one weighting unit into
account for each day. The total of the weighting values is 365 for one
year or 366 for a leap year.
•Weighting of energy feeding or degree day weighting

•These weighting procedures takes seasonal fluctuations into account.
•User-defined weighting
•In addition to the weighting procedures defined by SAP, you can
define your own weighting procedures.

Base Period Category
Same period of last year Last period

Advantages: Advantages:
• More representative if seasonal • More representative if there is
factor is to be taken into account significant change in
• If same period of last year data is consumption pattern over the
not available, IS-U will switch to last 12 months
last period automatically
Disadvantages: Disadvantages:
• Less representative if there is Less representative if seasonal
significant change in consumption factor is to be taken into
pattern over the last 12 months account

Review
• Meter reading process starts with creation of meter reading orders
• Meter reading sequence can be defined in the system for easy

meter read
• Meter readings are validated on entry based on the parameters

(configured) set in the system
• Meter reading are estimated based on actual previous reads and

base period category.

Discussion
• Street Route and Scheduling form the basis for

______________________
periodic meter reading
• What are the different types of meter readings?
• What are the pre-requisites for the billing order?
• Is the billing order always created for every meter reading order?
• What possible activities can be performed on an implausible
reading?
• What possible activities can be performed on a plausible reading?
• What are the various objects that can be reversed?

Exercises - 4
1. Create periodic MR order / billing order for the next available billing period
(EL01)
2. View MR history (EL31) before entering a MR result
3. Enter MR note (EL28) and click on estimate button.
4. Release implausible MR results if necessary (EL27)
5. View MR history (EL31) After entering a MR result
6. Simulated billing (EA00) and check if there’s no error

Check point
 What is reactive power – VARH?
• ‘Reactive power’. Measure the amount of power wasted due to reactive
properties of the equipment (i.e. motor). Remember: Wasted Energy!
 What is a portion? Can the same portion encompass multiple MRUs?
• Portion determines when a customer is billed. Yes, the same portion can
encompass multiple MRUs – i.e. different routes but billed the same workday.
 What happens to a meter reading that has failed validation? What is an example of
a meter reading validation?
• A meter reading that has failed validation becomes an “implausible read” and is
blocked for Billing purposes by the system. Examples of meter reading
validation include checking for high / low consumption usage, unauthorized
usage, too many estimates, etc.
 What does MRO stand for and why is it created?
• MRO stands for Meter Reading Order, and it is created for either billable or
control reads.
 True or False – MRO is created for each specific register on a device.
• True. MRO is created for each specific register on the same device that
requires a reading.
Agenda
• DM - Technology
• Workshop

IS-U/CCS with EDM
Customer/
IS-U/CCS with EDM contract
data
EDI / XML Interfaces

Download Load to other Device
shape applications Management
AMR data
Data Repository
IMPORT / EXPORT
IMPORT / EXPORT
Signal
IS-U Energy
Load shape
meter
Download POD Invoicing
RTP / TOU
Data data
Entry Upload billing
Contract
Discrete
Meter data
A/R & A/P
reading
Meter Print
docs
Settlement
Data Entry EDI / XML Scheduling
Meter reading
by customer
IS-U/CCS
WWW component
Energy Data Management
• Energy Data Management (EDM) is a solution that fulfills requirements by

offering interval reading, settlement of energy quantities, scheduling, and billing
of interval energy consumption.
• Fully integrated into IS-U/CCS and can be installed in an existing SAP IS-U
system as a new component.
• Integrated into Intercompany Data Exchange (IDE), which allows for data
exchange in standardized formats and enables the integration of cross-
company business processes.
• Interfaces with automated meter reading systems

Three Pillars of EDM
• Energy Data Repository

(Historical profiles, Price
Profiles, Forecast profiles
stored in central DB)
• Settlement and scheduling

(Settlement runs,
schedules, load shapes)
• Real-Time Pricing/Time of
use pricing (Complex
Billing)

EDM Data Model

EDM Data Objects

Energy Data Management and Billing Process

EDM Components

Key Terms
• POD: Point to which a utility service is supplied.
• Service: It is rendered by the service provider.
• Service Provider: Company providing service to POD
• Profile: Time series data that contains values such as consumption

or prices for certain period.

Point of Delivery

Point of Delivery
• POD ID: It is an unique number used to communicate to external

system. If the customer changes utility company this number
remains the same.
• POD Roles:
 Deregulation POD: Automatically created when an installation is
created. It is used for communication purposes between different utility
companies in deregulated market. Used to identify customer in all data
interchange between different market participants
 Technical POD: It is used for technical communication( To exchange

meter reading results). Number used to identify the device in all data
interchange between the market participants. For example if a device
measures several points of delivery.

Profiles
What are profiles?

• Contains values such as consumption and prices for a certain period
• Composed of profile header and values
Data Stored within a profile

• Historical Data: Measured meter readings
• Forecast data: Estimated energy consumption or forecast of customer future usage
• Schedule data: Proposed energy to be consumed per supplier (Aggregation of
forecast and/or historical data)
• Conversion factor profile (such as gas law deviation factor)
• Rate/price/temperature time series
Characteristics of profiles
• Interval lengths
• UOM (kWh, kW, Price, Temperature, Factors, etc.)

Profile Data

EDM Profile Creation Process

Profile Header

Profile Categories
Five Predefined profile
categories:
• Elementary: Contains
values that are imported or
entered manually.
• Synthetic: Contains values
created for a customer
group. These values can be
grouped together according
to season, time of day or
day type.
• Formula: Contains values
created using pre-defined
formula and using other
profiles.
• Day: Contains values that
are measured at identical
intervals and that together
describe one day.
• Integral: Only used
internally within the system.

Profile Types

Profile Roles
The role determines which task
the profile carries out on
register.
Profile roles are used for:

• Import and export of profile
values
• In replacement value creation,
the role determines the
reference profile
• In settlement processing role
identify settlement parameters
• The profile of the data to be
processed is indentified using
the POD, the POD register
code and role category
• In RTP billing roles enable the
flexible allocation of profiles to
input parameters from the RTP
interface.
• In RTP rate, the role replaces
the register operand as the
source of consumption data.

Role Allocation
Example Profile
Roles:
1) Consumption
measured
2) Consumption
forecast
3) Agreed
demand
4) Price profile
5) Agreed
consumption
6) Agreed
consumption
On-peak rate
7) Agreed
consumption
Off-peak rate

Role Categories
• Measurement:
Profiles allocated to
this role category
describe
consumption
measured by an
interval meter
• Forecast: Profiles
allocated to this role
category describe
consumption forecast
by an interval meter
• Settlement: Profiles
allocated to this role
category settlement
are included in the
settlement process
• Not specified: Use
this category for roles
with unspecified
functions.

Importing Profile Values
Profile values can

be imported using
two procedures:
• BAPIs(Business
application
programming
interface):
Synchronous
communication
path
• IDOCs(Intermediat
e document):
Asynchronous
communication
path

Data models used to import profile values
Registers are
identified by
the following
objects:
1) POD
identification
2) Register
Code
3) Role
Category
4) Role of
profile
allocation

Profile Consistency check
Consistency checks
check the profile
values as they are
imported into the
system.
Example:-
• Missing and
overlapping
value
consistency
checks are
allocated to
consistency
check groups
• Consistency
check groups
are allocated in
profile header.

Profile Consistency Check
From-time To-time Value

Gap 00:00:00 00:14:59 10.000
From-time To-time Value check 00:15:00 00:29:59 9.000
00:00:00 00:14:59 10.000 00:30:00 00:44:59 10.200
00:00:00 00:14:59 10.000
00:15:00 00:29:59 9.000 01:15:00 01:29:59 10.010
00:30:00 00:44:59 10.200 01:30:00 01:44:59 11.000
Overlap 02:00:00 02:14:59 7.014
01:00:00 01:14:59 5.020
check
01:15:00 01:29:59 10.010
01:30:00 01:44:59 11.000 From-time To-time Value
02:00:00 02:14:59 7.014 00:00:00 00:14:59 10.000
00:15:00 00:29:59 9.000
Completeness 00:30:00 00:44:59 10.200
check 01:00:00 01:14:59
01:15:00 01:29:59 10.010
01:30:00 01:44:59 11.000
From-time To-time Value 02:00:00 02:14:59 7.014
00:00:00 00:14:59 10.000
00:15:00 00:29:59 100.000
Tolerance
00:30:00 00:44:59 10.200
check
01:00:00 01:14:59 5.020
01:15:00 01:29:59 10.010
01:30:00 01:44:59 11.000
02:00:00 02:14:59 7.014
Manage Profile Values
• Profile value
presentation(tab
le or graphical)
• Modification of
profile values

Manage Profile Values
Versioning
OLE integration

Formula Profiles
• Formula profile
contains values that
are determined on
basis of calculation
rule. Calculation is
mapped in formula
• A formula is a
calculation rule that
converts different input
parameters into output
parameters.
• Formula profile
calculation involves
following operations:
1. Addition for each
interval
2. Subtraction for each
interval
3. Average for each
interval
4. Multiplication with a
factor
5. Other
Synthetic Profiles
1) Used in some markets if
customer Consumption is not
determined using an interval
reading
2) It contains values generated
on predefined periods and
corresponding day. Customer
groups are assigned the
same synthetic profile.

Profile Value Processing
l Individual changes
l Mass changes
l Version creation
l Individual status
l Display as graph or table

Settlement Workbench
Planning and
controlling
Settlement Workbench Settlement runs
Settlement (Synthetic, analytical,and

Settlement document procedure so on)
Settlement
log
Settlement run Control (Simulation, actual)
Input parameter
Settlement process
(Determine total
Interim result Settlement step ...1
load shape)
Output parameter
Input parameter
Interim result Settlement step ... 2 (Subtraction
interval customer)
Output parameter
Input parameter
(Send results using
Interim result Settlement step ... n IDE)
Output parameter

Settlement
• Settlement in EDM means settlement of energy quantities. All input data

required for settlement comes from EDM Repository. For example we can
calculate the total load of a grid and send it to a market partner.
• Consumption data that is determined and managed in component SAP IS-
U-EDM is transferred during settlement. With the help of the processes
provided by component SAP IS-U-IDE, this data can be communicated to
other market participants.
• Settlement is used to calculate actual or forecast consumption for
settlement units. Consumption values are analyzed in small time intervals
and calculated as a profile.
• The input data required for settlement is taken either from Energy data
repository or formula calculation

Settlement
• The division of consumption values into time intervals (15 minutes, for
example) also takes place for consumption values measured without a load
shape meter (for example, annual/monthly consumption of residential
customers).
• The algorithm used to divide up consumption not measured in intervals, is

determined by the settlement process, which can be created as an SAP
Business Workflow from available settlement steps.
• Point of delivery plays a crucial role in settlement procedure. It is used in

allocation of consumption values in settlement unit

Settlement Procedure
• These procedures are defined into individual settlement steps that can be
executed sequentially or simultaneously.
• Settlement Units : A settlement unit is an object that corresponds to

settlement area. Settlement unit allows to control which consumption values
are selected for settlement. As a result of settlement one profile is created for
for every settlement unit within the settlement period.
• If the suppliers and distributors are managed in the same system the POD
(Point of Delivery) is required to be allocated. Settlement views separate
distributors and supplier view so that in every view a point of delivery is
uniquely allocated to a settlement unit.
• Settlement Document: Before starting settlement run a settlement document

is created.
• Header Data for settlement Document contains settlement period,

settlement mode, settlement procedure and selection variant.

Settlement Run
Provision of
results
8
Backbilling Settlement
1 document
7
Settlement
Exception procedure
2
handling and settlement
(alerts) 6
mode
3 Selection
5 variants
Technical and
run logs 4
Settlement
steps
Settlement Procedure
Step 1: Step 2:
Step 3:

Agenda
• DM - Technology
• Workshop

Workshop
Creating Device Category and Device

1. Create Register Group
2. Create Device Category
3. Create Device
4. Install Device(Technical +Billing Related)
Creating Scheduling Data
1. Create Portion
2. Create MRU
3. Generate Schedule Record
4. Allocate Route to MRU/Portion
Creating Meter Reading, Validation and Estimation
1. Create MRO
2. Enter Reading/Estimate
3. Validate Meter Reading
Question

Version Management
Prepared By Changed By Reviewed By Industry Industry

Owner Team
Radharaman Anupriya Nogesh Ankit A
Haldar Munjal Bharadwaj Sharma
Nivedita Priya M Singh
Kulkarni


03 - AECS - SAP - ISU - Device Management - Bootcamp - 2016 - V1.0

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

03 - AECS - SAP - ISU - Device Management - Bootcamp - 2016 - V1.0

Загружено:

Авторское право:

Доступные форматы

AECS IS-Utility Bootcamp

Device Management Overview

Strategy | Consulting | Digital | Technology | Operations

• Current Project and your role

• What have you heard about SAP IS-Utility?

Copyright © 2016 Accenture. All Rights Reserved.

At the conclusion of today’s session, you will be able to:

 Describe the Characteristics of a Device

Copyright © 2016 Accenture. All Rights Reserved.

• Device Management Overview

• DM – Meter Reading Estimation

• Energy Data Management

Copyright © 2016 Accenture. All Rights Reserved.

• Industry Solution Utilities / Customer Care & Service System (IS-U

• IS-U- Industry Solutions for Utilities.

• CCS- Customer Care Services

• IS-U CCS- Customer oriented software for customers of a utility

• The greatest advantage IS-U CCS is that, it is an Integrated

Copyright © 2016 Accenture. All Rights Reserved.

Copyright © 2016 Accenture. All Rights Reserved.

Technical Device Device

• Connection Object • Scheduling • Device characteristics • Installation

Copyright © 2016 Accenture. All Rights Reserved.

Device Management Billing

Copyright © 2016 Accenture. All Rights Reserved.

• Device Management Overview

• DM – Meter Reading Estimation

• Energy Data Management

Copyright © 2016 Accenture. All Rights Reserved.

Device Number Device Data

Copyright © 2016 Accenture. All Rights Reserved.

• Device Characteristics covers entering and managing various

– Basic Device Category : Defines the type of Device based on its

– Device Category : Groups devices as per more specific characteristics.

– Devices : They identify the actual meter or transformer in the system.

Copyright © 2016 Accenture. All Rights Reserved.

Copyright © 2016 Accenture. All Rights Reserved.

• Groups devices that have the same technical

• Corresponds to the material in the Logistics

Copyright © 2016 Accenture. All Rights Reserved.

- Groups together devices

Copyright © 2016 Accenture. All Rights Reserved.

- Is an instrument used for measuring

- Managed as pieces of equipment's

Copyright © 2016 Accenture. All Rights Reserved.

- Used to meter consumption, Register

- Identified as a register number in

Copyright © 2016 Accenture. All Rights Reserved.

• Every Device Category has a related Register Group or a Winding

• Register Groups : Defines type and number of registers for a

• Winding Groups : Defines relationships between primary and

Copyright © 2016 Accenture. All Rights Reserved.

Copyright © 2016 Accenture. All Rights Reserved.

Technical Data Process Data

Copyright © 2016 Accenture. All Rights Reserved.

 KWh (kilowatt-hour):  The basic unit of electric energy used to measure

 Demand (kW):  ‘Active/real’ electric power. Instantaneous measure of

 Reactive Power (kVARH):  ‘Reactive power’. Measure the amount of power

 Power Factor:  Measure of how effectively electricity is being

Copyright © 2016 Accenture. All Rights Reserved.

• SAP MENU PATH – Utilities Industry -> Device Management ->

– Create Register Group – Transaction EG04

Copyright © 2016 Accenture. All Rights Reserved.