SAP Help IsU Device Management PDF

Device Management
PDF download from SAP Help Portal:

http://help.sap.com/erp2005_ehp_07/helpdata/en/57/91d0533f8e4308e10000000a174cb4/frameset.htm
Created on December 19, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
© 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC Page 1 of 96
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Table of content
1 Device Management
1.1 Technical Device and Connection Data
1.1.1 Register Group
1.1.1.1 Sample Register Relationship
1.1.2 Input/Output Group
1.1.3 Command Group
1.1.3.1 Creating Command Groups
1.1.4 Winding Group
1.1.5 Device Category
1.1.5.1 Device Category Creation
1.1.5.2 Creating Device Categories in IS-U
1.1.6 Equipment
1.1.6.1 Device Creation
1.1.6.1.1 Inspection Relevance
1.1.6.2 Creating Devices in Plant Maintenance
1.1.6.3 Creating Devices in Inventory Management
1.2 Device Installation
1.2.1 Device Information Record
1.2.2 Device Grouping
1.2.3 Installing, Removing or Replacing Devices
1.2.4 Device Installation
1.2.4.1 Device Installation
1.2.5 Device Removal
1.2.5.1 Device Removal
1.2.6 Device Replacement
1.2.6.1 Device Replacement
1.2.6.2 Replacement of Device Group with Another Device Gr
1.2.6.3 Replacement of Device Group with Smaller Device Gr
1.2.6.4 Replacement of Device Group with Larger Device Gro
1.2.6.5 Repl. of Dev. Group with Dev. Grp with Special Tec
1.2.6.6 Replacement of Devices in a Device Group
1.2.6.7 Replacement of Device Group with Complex Device
1.2.6.8 Replacement of Complex Device with Device Group
1.2.7 Reversal of Technical Installations, Removals and Replacements
1.2.7.1 Reversing Device Installations
1.2.7.2 Reversing Device Removals
1.2.7.3 Reversing Device Replacements
1.2.8 Device Modification
1.2.8.1 Device Modification
1.2.8.1.1 Entry of Meter Reading Results During Modification
1.2.8.1.2 Allocation of Different Device Category via MM-IM
1.2.8.1.3 Allocation of Different Device Category via PM
1.2.9 Installation Structure
1.2.9.1 Device Allocation
1.2.9.1.1 Creating Device Allocations
1.2.9.2 Rate data
1.2.9.3 Register Relationship
1.2.9.4 Period consumption
1.2.9.4.1 Period Consumption and Usage Factor Concepts
1.2.9.5 Logical Register Number
1.2.9.5.1 Changing Logical Register Numbers
1.3 Reading Meters
1.3.1 Base Period
1.3.2 Weighting Procedure
1.3.2.1 Examples for Mixed Weighting
1.3.3 Extrapolation
1.3.3.1 Extrapolation for Consumption Registers
1.3.3.2 Extrapolation for Demand Registers
1.3.3.3 Extrapolation for Resetting Registers
1.3.3.4 Extrapolation with Billing Factor
PUBLIC Page 2 of 96
1.3.3.5 Proration of Meter Readings
1.3.3.6 Extrapolation of Demand from Billing
1.3.4 Meter Reading Organization
1.3.4.1 Street Route
1.3.4.1.1 Maintain Street Route for Meter Reading Unit
1.3.4.2 Planning Meter Readers
1.3.4.3 Mass Changes to Meter Reading Units
1.3.5 Meter Reading Order
1.3.5.1 Meter Reading Order Creation
1.3.5.1.1 Single Order Creation
1.3.5.1.2 Mass Order Creation
1.3.5.1.3 Meter Reading Control
1.3.5.1.4 Reversal
1.3.5.2 Order Output
1.3.6 Meter Reading Result
1.3.6.1 Entry of Meter Reading Results
1.3.6.1.1 Upload
1.3.6.1.2 Fast Entry With/Without Correction
1.3.6.1.3 Single Entry
1.3.6.1.4 Assessing
1.3.6.2 Correction of Meter Reading Results
1.3.6.2.1 Upload
1.3.6.2.2 Correction of Plausible Meter Reading Results
1.3.6.2.3 Correction of Implausible Meter Reading Results
1.3.6.3 Validations
1.3.6.3.1 Independent Validation
1.3.6.3.2 Dependent validations
1.3.6.4 Estimation
1.3.7 Reversal
1.3.8 Monitoring
1.3.8.1 Monitoring of Meter Reading Results
1.3.8.2 Device Overview
1.3.9 Quantity Determination
1.3.9.1 Quantity Determination During Meter Reading
1.3.9.1.1 Important Notes
1.3.9.1.2 Notes About the Time of the Changeover
1.3.9.1.3 Concepts
1.3.9.1.3.1 Change Meter Reading Results
1.3.9.1.3.2 Quantity Determination Trigger Concept
1.3.9.1.3.3 Check for Final Determined Consumption in Technical Transactions
1.3.9.1.3.4 Estimation Procedure
1.3.9.1.3.4.1 Extrapolation
1.3.9.1.3.4.2 Interpolation
1.3.9.1.3.4.3 Interaction - Estimation and Actual Meter Reading
1.3.9.2 One-Off Activities for Changeover
1.3.9.2.1 Check Company-Specific Starting Point
1.3.9.2.2 Defining the Quantity Determination Procedure
1.3.9.2.3 Defining the QD Procedure for Existing Installations
1.3.9.3 Activities in Production Operation
1.3.9.3.1 Process Quantity Determination Trigger
1.4 Device Inspection
1.4.1 Device Inspection
1.4.2 Sampling Procedure
1.4.2.1 Sampling Procedure
1.4.2.1.1 Official/Internal Lots
1.4.2.1.2 Lot Compilation
1.4.2.1.2.1 Compiling Lots
1.4.2.1.2.2 Deleting Devices or Device Categories from Lots
1.4.2.1.3 Determination of Lot Devices
1.4.2.1.4 Drawing of Sample Devices
1.4.2.1.4.1 Drawing Sample Devices
1.4.2.2 Sampling Procedure for Canada
PUBLIC Page 3 of 96
1.4.3 Periodic Replacement
1.4.3.1 Creation of Periodic Replacement Lists
1.4.3.2 Work Order or Notification Creation
1.4.3.3 Work Order Printout
1.4.4 Certification
1.4.4.1 Certification
1.4.4.2 Seal Extension
1.4.5 Recording Device Inspection Data in Quality Management
1.5 Country Specific Functions
PUBLIC Page 4 of 96
1 Device Management
Purpose
This component manages technical data, installations, meter readings, and the inspection of devices.
If you have activated the Advanced Metering Infrastructure business function (ISU_AMI_1) and you are in an advanced metering infrastructure, you can find
more information under Advanced Metering Infrastructure .
Integration
The following table lists the standard application components that must be integrated into device management before you can manage devices.The device, device
category, and device number in the Utilities Industry (IS-U) component correspond to equipment, material, and the serial number in the standard system:
Names in IS-U and the Standard System
Name in IS-U From component Name in Standard System
Device Plant Maintenance (PM) Equipment
Device Category Logistics Basic Data (LO-MD) Material
Device Number Logistics Basic Data (LO-MD) Serial Number
The device number is created in MM with the Goods Receipt function and transferred to the device. The device number can also be generated when you create
a device in IS-U. 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. The equipment number is the same throughout the system.
Integration of IS-U with MM, LO and PM
MM is also used for the following functions in device flow:

MM Functions for Device Flow
Function Component
Procurement Purchase Requisition and Purchase Order from (MM-PUR)
Delivery Goods Receipt from Inventory Management (MM-IM)
Outward Movement (such as scrapping or sales) Goods Issue and Return Delivery from MM-IM
Stock Transfer Goods Issue and Return Delivery from MM-IM
Equipment records are created automatically at goods receipt .Therefore, functions of the PM application component are used, including standard ordering
functions and creation of maintenance plans or task lists. Billing is then carried out with the Sales and Distribution (SD) component.
For more information, see:
PM: Equipment
LO-MD:
Serial Number Management

MM-PUR:
MM-IM:
Goods Receipts for Purchase Orders
1.1 Technical Device and Connection Data
PUBLIC Page 5 of 96
Purpose
This component manages technical and connection data of devices:
Note
A connection may be the input and output of a transformer, for example. This type of connection should not be confused with the connection of a connection
object to the supply line.
1.1.1 Register Group
Purpose
This component groups together the registers of one device category or one device, including technical data (such as number of digits and type of display) and
billing data (such as rate usage type). Registers meter consumption and demand. Registers can be actual physical devices or displays in electronic devices.
Features
You can manage registers of different division categories in one register group. You can allocate a main division category to the register group. At least one register
of the register group must be in the main division category.
1.1.1.1 Sample Register Relationship
Use
This function allows you to allocate a sample register relationship to a register group.
Features
You have the following options when using this function:
You can create several sample register relationships for each register group. You can use any sample register relationships possible within a register
group.
When you install devices you can adopt the sample register relationships of the register group and create them as functional register relationships.
If you change an existing sample register relationship, there is no effect on installed devices.
Processing and checks are the same as those for normal Register Relationships .
1.1.2 Input/Output Group
Purpose
This component groups together the inputs and outputs of a device category or device and provides technical data of these devices. Inputs and outputs are
interfaces for devices. Remote meters have several pulse inputs and a modem interface.
1.1.3 Command Group
Purpose
This component allows you to define commands and group them together. A command is a signal sent by the utility company that triggers a switching procedure
in a ripple control receiver.
Example
For example, the command group for street lights might consist of the commands switch-on , decrease demand , and switch-off .
1.1.3.1 Creating Command Groups

Prerequisites
You have created the appropriate commands for the command group.
Procedure
To create a command group choose Utilities industry Command/comm. group Create command group
1.1.4 Winding Group

PUBLIC Page 6 of 96
1.1.4 Winding Group
Purpose
This component groups together windings of one device or device category. Windings define the transformation ratio (of transformers, for example) and are divided
into primary and secondary windings. A winding group contains at least one primary and one secondary winding.
You can define a text field for the winding demand in Customizing under Define Winding Demand.
You can deactivate checks for maximum current and voltage in Customizing. To do this, go to Technology Winding Group Define System Parameters for
Winding Groups .
Implementation considerations
This component is optional. It is only required if you use transformers.
1.1.5 Device Category
Purpose
This component manages device categories. Each device belongs to a certain device category. The device category groups together all devices with similar
features (for example, price class, register group, or certification data).
The various device categories can then be allocated to the following basic device categories :
Counter
Transformer
Power transformer
Audiofrequency ripple control receiver
Remote meter
Counter
Corrector
Pressure regulator
Sensor
Other
One device category can also be a combination of different device categories.
Integration
The device category corresponds to the material in the Logistics Basic Data (LO-MD) application component.
For more information, see LO-MD:
Material Master
1.1.5.1 Device Category Creation

Use
This function allows you to create device categories in the Utilities Industry (IS-U) component.
Integration
This function is integrated with the application components Logistics (L0) and Materials Management (MM).
The IS-U device category is an extension of the Material master in the Basic Logistics Data (LO-MD) application component. You maintain the material master in
the Materials Management (MM) application component.
Features
You have the following options for creating a device category:
You can create the material master in MM first .
When you do this, a material master for IS-U is automatically created in the background.
Subsequently, you must extend this material master in IS-U as a device category with IS-U-specific data.
You can only create the material master as a device category in IS-U.
When you do this, a smaller version of the material master is created automatically in the background for MM. However, this material master does not allow you to
use all of the functions of MM.
If you want to use all of the MM functions available, you must extend the material master you created in IS-U later in MM.
Note
If you use MM, we recommend the first option above.
Prerequisites
You have maintained the following in IS-U:
PUBLIC Page 7 of 96
Register groups
Input/output groups
Command groups
Inspection point groups (optional)
Winding groups (only required for transformers)
1.1.5.2 Creating Device Categories in IS-U

Procedure
1. Choose Utilities industry Device management Technology Device category Create.
You branch to the initial screen for creating device categories.
2. Enter the required data and choose a basic device category to be allocated to the device category. Chose Continue .
If a material exists for the device category specified, you branch to the screen Create Device Category: General Data. Go to step 3.
If no material exists for the device category specified, the Create MM Material dialog box appears.
Here you can create a material in MM in the background. Processing is then continued on the next screen for device category maintenance.
3. Enter further data for the device category and if necessary add additional basic device categories. Save your data.
You branch to the initial screen for creating device categories.
Result
The device category was created in IS-U. In addition, a material master was created in the background.
If you want to use all of the MM functions available, you must extend the material master you created in IS-U in MM.
1.1.6 Equipment
Purpose
This component manages the equipment of a utility company.
Integration
The equipment is uniquely identified in the system by the following:
The equipment number in PM
The combination of serial number and material number in the Logistics Basic Data (LO-MD) component
The Technical Objects component (PM-EQM): Equipment
The Logistics Basic Data component (LO-MD):
Material Master
The Purchasing component (MM-PUR):
Purchase Requisitions
Purchase Orders
The Inventory Management component (MM-IM):
Planning Goods Receipts
Goods Receipts for Purchase Orders
Goods Receipts for Orders
Other Goods Receipts
Goods Issues
Transfer Postings and Stock Transfers
1.1.6.1 Device Creation
Use
This function allows you to create devices in the Utilities Industry (IS-U) component. For each device, a master record with IS-U-specific data is created in
addition to a corresponding piece of equipment in the Plant Maintenance (PM) application component.
Integration
This function uses many functions from the Plant Maintenance (PM) application component.
Prerequisites
You have created the appropriate device category for the device.
PUBLIC Page 8 of 96
Features
You can create devices
In IS-U via the Technical Device and Connection Data (IS-U-DM-TD) component.
You do this by using the Create material serial number function in PM that was enhanced for IS-U.
The device is only created as a piece of equipment, but the material stock in the Inventory Management (MM-IM) application component is not updated.
You can create several devices simultaneously via list editing.
In MM-IM via goods receipt
You can create any number of devices with different device categories.
The material stock is updated accordingly.
You can assign any default entries to the fields in the Create IS-U data dialog box, which appears when you create a device. To do this, use function module
EXIT-SAPLE10R_002 in enhancement EDME10L1.
You can now use function module EXIT_SAPLIPW1_008 from enhancement IQSM0008 when you create a material serial number and equipment. This means
that every time you create a device, the corresponding combination of material and serial number undergoes further user-defined checks.
1.1.6.1.1 Inspection Relevance
Use
You use this function to determine whether a particular device, such as an external device, is to be included in a Sampling Procedure.
Prerequisites
You have established settings for inspection relevance in Customizing. To do this, go to Utilities Industry Device Management Inspection Sampling
Procedure Define Inspection Relevance of Devices .
1.1.6.2 Creating Devices in Plant Maintenance

Prerequisites
The appropriate device category for the device has been created.
Procedure
Note
To create several devices at once in the Plant Maintenance application component, choose Utilities Device management Technology Device
List editing Create .
1. Choose Utilities industry Device management Technology Device Create.

2. You branch to the initial screen for creating material serial numbers.
3. Enter the material number, and if necessary the serial number and the equipment category used for IS-U devices. Chose Continue .
4. The Enter IS-U data dialog box appears.
5. Enter the required data. Choose Transfer .
6. You branch to the screen Create material serial number: IS-U data.
7. Enter the required data.
8. Save your data.
Result
The device has been created as a piece of equipment in the Plant Maintenance application component.
Note
The material stock of the Inventory Management (MM-IM) application component was not updated.
1.1.6.3 Creating Devices in Inventory Management
Prerequisites
The appropriate device category for the device has been created.
Procedure
1. Choose one of the following menu paths:
Utilities Industry Device Management Technology Device Inventory Management
Logistics Materials Management Inventory Management
1. Choose Goods Movement Goods Receipt and select the appropriate type of goods receipt.
PUBLIC Page 9 of 96
The Enter Goods Receipt: Initial Screen appears.
Note
The type of goods receipt you choose is dependent on your previous processing steps. For example, if you have created an order for the devices to be
created, choose Goods Receipt For Order . In the most straightforward example, choose Goods Receipt Other .
1. Enter the required data. Choose Continue .

The Enter Goods Receipt: New Items screen appears.
1. Enter the material, quantity and any other data required. Choose Continue .
The Maintain Serial Numbers dialog box appears.
1. Choose Create Serial Number Automatically or enter the number manually. Choose Previous Screen .
2. The Enter IS-U Data dialog box appears.
3. Enter the required data. Choose Copy .
The Enter Goods Receipt: Collective Processing screen appears.
( )
From the Enter IS-U Data screen, you can access the classification system in which you can classify devices using your own criteria. Choose Classification .
1. Save your entries.
You can now enter additional devices as described above.
Result
The device has been created as a piece of equipment in the Plant Maintenance and Service Management (PM) component. The material stock in the Inventory
Management component (MM-IM) was updated.
Purpose
This component allows you to do the following:
Install, remove, and replace devices
You establish or terminate a link between a device and a device location (technical view) and an installation (billing view).
You can override certain system parameters defined by SAP for installation, removal or replacement. Establish settings as required in Customizing. To do
this, choose Device Management Installation Basic Settings Define System Parameters for Installation/Removal/Replacement .
Create device groups
Change rate data and technical data of devices that are already installed in a utility installation.
Integration
You can use the IDoc ISU_DEVICE_CHANGE to transfer data from external systems to the work process.You can enter one meter reading result per action.It is
currently not possible to process multiple meter readings.
If a meter reading is implausible, IDoc processing is not canceled.You can correct the reading.For more information, see Correction of Implausible Meter Reading
Results .
To transfer meter reading results to workflow for further processing, use the role ISU_MREADER for the agent.
Further information on IDocs:
For general information, see IDoc Interface/Electronic Data Interchange
For detailed information, see Using Documentation Tools
Here you determine which documentation you can display for a certain IDoc.
You can integrate functions for transferring devices prior to installation or after removal into device installation, removal and replacement. You have the following
options:
Installation and removal
You can enter the target plant and storage location as well as the movement type on the initial screen.
Device replacement
You can enter goods movement data (target plant and storage location and movement type) for device removal and installation. You can also enter other data
such as the cost center.
To activate these functions, you have to define parameter GOODSMVMT in Customizing under Installation System Parameters for
Installation/Removal/Replacement .
Device installation, removal, and replacement now contains the following enhancements:
EDMD1001 (user-defined default values for installation, removal and replacement)
This enhancement allows you to define default data for input parameters.
EDMD1001 (user-defined checks for installation, removal and replacement)
This enhancement allows you to implement your own input checks.
Meter Data Unification and Synchronization (MDUS) System Notification for AMI devices
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you:
PUBLIC Page 10 of 96
Install an AMI device (for example, a smart meter or advanced meter)in a new device location.
Make installation modifications to an AMI device
Remove an AMI device from a device location
1.2.1 Device Information Record
Definition
The device information record is an object in the IS-U system that enables the system to perform billing-orientated functions.
Use
When carrying out billing functions, the complete IS-U Device Management (IS-U-DM) does not have to be used. Instead, you can create a device information
record that only manages device data required for billing, for example, rate data, device allocations, register relationships and maintenance of logical registers.
About AMI-relevant device information records

If you are working within an advanced metering infrastructure, you can indicate that device information records are AMI-relevant. In this case the devices and
device information records have additional attributes: For more information, see Advanced Metering Infrastructure .
Remote disconnection and reconnection processes also apply to device information records.However, you can prevent remote disconnection or reconnection by
implementing a validation within the BAdI ISU_AMI_DISCONNECT .
Integration
There is no longer a connection to Plant Maintenance (PM) . Communication with other systems, such as importing consumption data, takes place via the point
of delivery.
1.2.2 Device Grouping
Purpose
In this component you can group together devices that form a logical unit. All devices in a device group must currently either be installed or not installed.
If you install or remove a device in a device group , all other devices in the group are automatically drawn for removal or installation. This ensures that devices that
belong together are not accidentally installed or removed. You must confirm the replacement of each device in a device group.
This component is optional. You should create a device group if, for example,
Current and voltage transformers are placed into transformer groups, resulting in a certain transformation ratio.
Two water meters are installed together as one integrated water meter.
Features
You can:
Maintain and display the history of the device group
When you do this, you can change the current time slice. You can decide whether the device group is to be prorated to the change date, that is, whether you wish
to start a new time slice. You can display change documents and creation data.
Inspect the device group
The system checks the device group for general and special restrictions. For more information, see the online help for the following fields:
Device group
Group type
Group category
Terminate the device group.
When you terminate a device group, all devices are removed from the group. The device group is empty and can be used for new devices.
Delete the device group.
When you delete a device group, it is deleted from the system entirely.
1.2.3 Installing, Removing or Replacing Devices
Procedure
Installing, removing or replacing a single device
1. Enter your device (enter both devices in the case of a replacement).
2. Enter the required data on the screen for either installation, removal, or replacement.
3. Save your data.
Installing, removing or replacing a device from a device group

Enter a device from the group on the initial screen. If you are replacing a device, enter a device from each group.
a) Choose Enter .
The rest of devices of the group are display in the worklist.
b) Choose Enter.
Process the work list.
Enter the required data for each device on the screen for either installation, removal, or replacement.
Save your data.
Installing, removing or replacing several devices

1. Do not enter a device, device category or division.
2. Enter the devices in the worklist or set the Rem. (removal) indicator.
3. Process the work list.
4. Enter the required data for each device on the screen for either installation, removal, or replacement.
5. Save your data.
Meter Data Unification and Synchronization (MDUS) System Notification for AMI devices
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you install, remove or replace an AMI
device (for example, a smart meter or advanced meter) in a new device location.
Purpose
In this component you can enter an initial or additional installation of a device in different ways.
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.
You can reverse a technical installation. For more information, see Reversal of Technical Installations, Removals and Replacements
Features
Installation includes the following functions:
Allocation of devices (e.g. transformer to meter)
Entry of periodic consumption
Entry of meter readings recorded at the time of installation
Creation of register relationships
Adopting Sample Register Relationships
Note
You can define a default measured pressure for technical installation. To do this, you have to establish settings in Customizing under Device
Management Installation Basic Settings Define System Parameters for Installation/Removal/Replacement and Contract Billing Special
Functions Gas Billing Volume Correction Factor Measured Pressures Define Measured Pressures.
Meter Data Unification and Synchronization (MDUS) Notification for AMI Devices
If you work within an advanced metering infrastructure (AMI) environment, t he system notifies the MDUS as soon as you install an AMI device (for example, a
smart meter or advanced meter) in a new device location.
Purpose
You can install devices in the following ways:
Technicalinstallation 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.
Fullinstallation, as in the case of a single-family home.
Prerequisites
When you enter the device installation, the device must not have been modified or changed in the system after the actual installation date. The entry in the system
must correspond to the actual history of the processes.
You enter the installation on 10/12. The installation took place on 10/08. A device modification or a change to the device data may not have been entered after
10/08.
You must perform a technical installation before you can perform a billing-related installation.
In the case of technical installations, the same prerequisites apply as for the installation of a piece of equipment ( Device ) in a functional location ( Device
location ) in the Plant Maintenance application component.
For more information see the following in the Technical Objects (PM-EQM) application component:
Functional locations
Equipment
Equipment at Functional Locations
Process flow
Device installation includes the following phases:
An installation order for a device or a device group is created in the Service Management (PM-SMA) application component. This may result from a company
requirement (such as a switching change) or an external requirement (new connection),
The installation order is executed and returned.
The removal of the device is entered in IS-U.
Here the device always undergoes a technical installation and if it is to be billed, it undergoes a billing-related installation.
For more information, see Installing, Removing, and Replacing Devices
Note the following:
If the device belongs to a device group, the entire device group must be installed in the case of technical installations and full installations.
In the case of technical and full installations you have to change the register group configuration.
Those registers are proposed for which the PR (Propose register during installation/replacement) field has been selected.
You can change the register configuration in Customizing under Change Register Configuration . You can the select any register in the register group.
Result
Technical installation
The device is installed in the device location. This corresponds to the installation of a piece of equipment in a functional location.
This enables you to use all PM functions for installed equipment.
The system stores technical data for the register.
Device relationships may have been created and a device location is created.
Billing-related installation
The device is allocated to an installation for billing.
The system creates billing-related data for the device and registers of the installation.
The device can be billed.
Full installation
The device is installed in the device location with respect to technical data
The device is allocated to an installation for billing.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you install an AMI device (for example, a
smart meter or advanced meter) in a new device location.
Purpose
You use this component to enter removal of devices. As in the Installation (IS-U-DM-DI-IN) component, removal is divided into technical removal, billing-related
removal, and full removal.
All rate data and relationships with other devices are prorated to the removal date (meaning the time slice ends). However, the data can still be traced.
Reference values are not prorated automatically. They can be manually prorated or deleted, however.
You can reverse a technical removal. For more information, see Reversal of Technical Installations, Removals and Replacements
Features
For more information, see Device Removal
Device Removal for One Day in Future

For interval meters, you can carry out a technical or billing related device removal for one day in the future.
In Customizing for SAP Utilities under Device Management → Installation → Basic Settings → Define System Parameters for
Installation/Removal/Replacement , select parameter REMOVEF1D – Remove, Install for Billing Intrvl Meter for 1 Day in Future .
You can also reverse the device removal for one day in the future.
Lot Membership and Certification

A device may lose lot membership or certification regardless of the activity reason. For more information, go to Customizing and choose Device Management →
Installation → Basic Settings → Define System Parameters for Installation/Removal/Replacement .
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you remove an AMI device (for example, a
smart meter or advanced meter) from a new device location.
Purpose
You can install devices in the following ways:
Technicalremoval only, if a device (such as a control meter) has undergone technical installation only.
Billing-relatedremoval only, if a device in an installation is no longer to be included in billing
First billing-related and technical removallater, for example if billing and technical areas in a utility company are managed by different employees.
One billing-relatedand several billing-related removals. This would apply in the case of a pressure regulator or an ARCR that controls several installations.
Fullremoval, for example in the case of a single-family home that is dismantled.
Prerequisites
When you enter the removal, the device must not have been modified or changed in the system after the actual removal date. The entry in the system must
correspond to the actual history of the processes.
You enter the removal on 10/12. The actual removal took place on 10/08. A device modification or a change to the device data may not have been entered after
10/08.
Before a technical installation can be performed,
The device must not have already undergone billing-related installation on the removal date
The device must not control any other device
No register of the device may be part of a register relationship that is automatically terminated
In the case of technical removals, the same prerequisites apply as for the removal of a piece of equipment ( Device ) from a functional location ( Device location )
in the Plant Maintenance (PM) application component.
Functional Locations
Equipment
Process flow
Device removal includes the following phases:
A removal order is created for a device or a device group in the Service Management (PM-SMA) application component. This results from a company
requirement (such as the dismantling of an object) or an external requirement (new connection).
The removal order is executed and confirmed.
The removal of the device is entered in IS-U.
If the device belongs to a device group, the entire device group must be removed in the case of technical and full removals.
If the last meter is removed from a device in an installation with a valid contract, the system issues either a warning or an error, depending on how you define
system parameters for installation/removal/replacement.
Result
Technical removal
The device is removed from the device location. This corresponds to the removal of a piece of equipment from a functional location.
The system prorates the technical data of the registers.
Billing-related removal
The system terminates billing-related allocation of the device to the installation.
The system prorates the billing-related device and register data of the installation
Full removal
The device is removed from device location with respect to technical data
The system terminates all billing-related allocations of devices to installations.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you remove an AMI device (for example, a
smart meter or advanced meter) from a new device location.
Purpose
This component allows you to enter the replacement of a device by another device with the same function from the same or similar device category. A device is
replaced instead of being both removed and installed if the following data is to be transferred to the new device:
Rate data
Register relationships
Device relationships
Register-related periodic consumption
Disconnected status
You can reverse a technical installation. For more information, see Reversal of Technical Installations, Removals and Replacements
Implementation Considerations
This component is optional because you can also replace a device with the Installation and Removal (ISU-DM-DI-IN or OU) components. However, if you use
these components, all links and register relationship are deleted. Therefore, it is often much easier to replace a device. For example, a replacement is necessary
if an installed device is damaged or if it is to be certified with the Device Inspection (ISU-DMIS) component.
Integration
You can transfer data to external systems using IDoc ISU_RPL_ORDER.
Here you determine which documentation you can display for a certain IDoc.
You can use enhancement EDMEG901 to change the predefined order and notification codes when work orders or notifications are created.
Features
In the case of a replacement, you can enter meter readings recorded at the time of installation or removal.
A device may lose lot membership or certification regardless of the activity reason.For more information, go to Customizing and choose Device Management
Installation Basic Settings Define System Parameters for Installation/Removal/Replacement .
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you replace an AMI device (for example, a
smart meter or advanced meter).
Purpose
This process enables you to replace devices.
Example
You replace a double-rate meter as part of a periodic replacement or due to damage.
Note
You can replace devices that have different measuring types. However, you may have to change the measuring types in the device allocation data.
Prerequisites
When you enter the replacement, the device must not have been modified or changed in the system after the actual replacement date. The entry in the
system must correspond to the actual history of the processes.
Example
You enter the installation on 10/12. The installation took place on 10/08. A device modification or a change to the device data may not have been
entered after 10/08.
The same prerequisites apply to the device to be removed as to the removal of a piece of equipment ( Device ) from a functional location ( Device location )
in the Plant Maintenance (PM) application component.
The same prerequisites apply to the device to be installed as to the installation of a piece of equipment (device) in a functional location (device location) in
the Plant Maintenance application component.
Functional Locations
Equipment
Process flow
Device replacement includes the following phases:
1. A replacement order is created for a device or a device group in the Service Management (PM-SMA) application component. This may result from a
company requirement (such as a switching change) or an external requirement (such as a change in use of the object).
2. The replacement order is executed and confirmed.
3. The replacement of the device or of all devices in a device group is entered in IS-U.
Note
There are different replacement scenarios for device groups, such as Replacement of a device group with another device group .
Note that replacement orders can only be created for single devices. This means that if the device belongs to a device group, the other devices are not
transferred to the order automatically as additional items.
Note
The system automatically checks and prorates the attributes (such as measured pressure, billing factor, or command) of existing device allocations. A
message is displayed if the system cannot check attributes automatically.You can go directly to the device allocation and check attributes manually. To
do this, choose Goto Device allocations .
Result
The new device adopts all relationships of the old device. If device categories of the devices do not match, it is possible that individual relationships were prorated.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you replace an AMI device (for example, a
1.2.6.2 Replacement of Device Group with Another Device Group

Purpose
This process can be used for replacing one transformer group with another transformer group, for example.
Process flow
Device group A is replaced with device group B. In this case, the devices to be installed adopt the tasks of the devices to be removed.
Replacement of a device group with another device group
( )
1.2.6.3 Replacement of Device Group with Smaller Device Group

Purpose
You can use this process to replace three devices in a meter board with two devices, for example.
Process flow
Device group A is replaced with device group B, which contains few devices. The devices to be installed, 1b and 2b, take on the same tasks as the 1a and 2a,
the devices to be removed. Device 3a is only removed.
Replacement of device group with smaller device group
( )
1.2.6.4 Replacement of Device Group with Larger Device Group

Purpose
You can use this process to replace two devices in a meter board with three devices, for example.
Process flow
Device group A is replaced with device group B, which contains fewer devices. The devices to be installed, 1b and 2b, take on the same tasks as the 1a and
2a, the devices to be removed. Device 3b is only installed with respect to technical data.
Replacement of device group with larger device group
( )
1.2.6.5 Repl. of Dev. Group with Dev. Grp with Special Tech.
Inst.
Purpose
You can use this process to install devices with different tasks in a meter board, for example.
Process flow
Device group A is replaced with device group B. The devices to be installed, 1b and 3b, take on the same tasks as the 1a and 3a, the devices to be removed.
Device 2a is only removed because the device to be installed, 2b, has another task.
Example
Devices 1a and 1b are active current meters, devices 3a and 3b are watt meters. The device to be removed (2a) is an ARCR, but the device to be installed
(2b) is a demand meter.
Replacement of device group with device group with special technical installation
( )
1.2.6.6 Replacement of Devices in a Device Group

Purpose
This process can be used for replacing an audiofrequency ripple control receiver in a meter board, for example.
Process flow
A device is replaced within device group A. The device to be installed (4a) has the same task as the device to be removed (1a). Device 4a is now part of the
device group. Devices 2a and 3a are not affected.
Replacement of devices within a device group
( )
1.2.6.7 Replacement of Device Group with Complex Device

Purpose
This process can be used for replacing a meter board with a complex meter, for example.
Process flow
Device group A is replaced with complex device 4. In this case, the device to be installed (4) has the same functions as the devices to be removed.
Replacement of device group with complex device
( )
1.2.6.8 Replacement of Complex Device with Device Group

Purpose
This process can be used for replacing a complex meter with a meter board, for example.
Process flow
Complex device 4 is replaced with device group A. The tasks of the complex device are transferred to the individual devices of the device group.
Replacement of complex device with device group
( )
1.2.7 Reversal of Technical Installations, Removals and

Replacements
Use
You use this function to reverse a technical installation, removal or replacement.
If you carried out both a billing-related and a technical installation, removal or replacement, see also:
Reversing Device Removals
Reversing Device Installations
Reversing Device Replacements
Prerequisites
The device must not have been installed for billing, that is, it must not be allocated to an installation.
Features
Full installation, removal or replacement

This function does not make changes to the data of the following objects:
Register relationships and reference values
Statistics records
Device allocations for controlling devices
Blocked devices
Device groups
The reversal does not take into account any device transfers you have carried out.
Reverse Installation
When you perform an installation reversal , the following is changed:
Technical installation in the Utilities Industry (IS-U) and Plant Maintenance and Service Management (PM) components are canceled. A removal is carried out
in PM at the time of installation.
The allocations of controlled devices (such as those controlled by ripple control receivers) are terminated.
The device location that you created during installation is not deleted.
Reverse Removal
A removal reversal results in the termination of a technical removal in the Utilities Industry (IS-U) and Plant Maintenance (PM) components. An installation is
carried out in PM at the time of removal.
Reverse Replacement
A reversal replacement results in the termination of a device replacement in the Utilities Industry (IS-U) application component In the Plant Maintenance and
Service Management (PM) component, the old device is automatically re-installed and the current device is removed.
Meter Data Unification and Synchronization (MDUS) System Notification for AMI Devices
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you reverse an installation,
replacement or removal of an AMI device (for example, a smart meter or advanced meter).
1.2.7.1 Reversing Device Installations
Use
This procedure enables you to cancel device installations
Prerequisites
You have executed a device installation that you want to cancel.
Procedure
1. Remove the device ( billing-related removal ) from all utility installations for each installation date.
You can find the installation dates under Utilities Industry Device Management Device Installation Installation Structure Rate Data or
Utilities Industry Device Management Technology Device.
2. Terminate any device allocations or relationships you have created.
3. Reverse the installation.
The device has now been technically removed.
4. If necessary, perform a stock transfer for the device removed.
To do this, choose Utilities Industry Device Management Technology Device Device Transfer via Serial Numbers or Device General
Inventory Management Goods Movement Transfer Posting .
Result
The device installation has been fully reversed. The device now has the status Removed again.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you reverse an installation of an AMI device
(for example, a smart meter or advanced meter).
Example
Initial Situation
Device D1 is technically installed at device location DL1 on the 01.01.2000.
A billing related device installation of device D1 is performed at installation 1 (Inst.1) on the first of February 2000.
A billing related device installation of the device D1 is performed at installation 2 (Inst.2) on the tenth of February 2000.
( )
Reversing Device Installations:
You want to reverse the device installation. Proceed as follows:
1. Execute a billing-related device removal of device D1 from installation 2 for the tenth of February 2000.
You have now reversed the billing-related installation in installation 2.
2. Execute a billing-related device removal of device D1 from installation 1 for the first of February 2000.
You have now reversed the billing-related installation in installation 1.
3. Reverse the installation.
( )
1.2.7.2 Reversing Device Removals
Use
This procedure enables you to cancel device removals.
Prerequisites
You have carried out a device removal that you want to reverse.
You must reverse any stock transfers you have carried out. The device must be available. To do this, choose Utilities Industry Device Management
Technology Device Device Transfer via Serial Numbers or Device General Inventory Management Goods Movement Transfer Posting .
Procedure
1. Perform the removal reversal.
The device has now been technically installed.
2. Create any device allocations or relationships you may have terminated.
3. Install the device ( billing-related installation) in all installations on the removal date.
4. You can determine the removal date in the following way:
Go to the Utilities Industry menu and choose Device Management > Installation > Installation Structure > Rate Dates
or
Go to the Utilities Industry menu and choose Device Management > Technology > Device in the Removal Date field.
Result
The device removal has been fully reversed (technically and billing-related. The device is installed.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you reverse a removal of an AMI device (for
example, a smart meter or advanced meter).
Example
Initial Situation
Device D1 was fully removed on the 10 February 2000; this means both technically removed from device location DL1 and billing-related from installations 1 and
2.
Reversing Device Removals:

You want to reverse the device removal. Proceed as follows:
1. Reverse the technical removal from device location DL1 for the 10 February 2000.
( )
2. Perform a billing-related device installation of device D1 in the installation 1 (Inst.1) forFebruary 10, 2000.
3. Perform a billing-related device installation of device D1 in the installation 2 (Inst.2) February 10, 2000.
( )
1.2.7.3 Reversing Device Replacements
Use
This procedure enables you to reverse device replacements.
Prerequisites
You have carried out a device replacement that you want to reverse.
You must reverse any stock transfers you have carried out. The device must be available. To do this, choose Utilities Industry Device Management
Technology Device Device Transfer via Serial Numbers or Device General Inventory Management Goods Movement Transfer Posting .
Procedure
1. Perform a billing-related removal for the installed (replaced) device from all installations on the device replacement date or each installation date.
You can determine the installation date via the Utilities Industry menu under: Device Installation Installation Installation Structure Rate Data or
Utilities Industry Device Management Technology Device .
2. Terminate any device allocations or relationships you have created for the newly installed device.
3. Perform the replacement reversal.
The new device is technically removed and the old device is technically installed .
4. Establish any device allocations or register relationships you require for the re-installed device
5. Execute a billing-related installation for the re-installed device in all installations on the device replacement date or on each removal date.
6. Perform a stock transfer for the device removed.
7. Perform a stock transfer for the device removed.
Result
The replacement has been fully reversed. The device now has the status Installed again.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you reverse a replacement of an AMI device
(for example, a smart meter or advanced meter).
Example
Initial Situation
Device D1 is technically installed in the device location DL1 on the January 01, 2000.
A billing related device installation of device D1 is performed in installation 1 on February 01, 2000.
A billing related device installation of device D1 is performed at installation 2 on February 10, 2000.
Replace device D1 with device D2 on March 01, 2000.
This replacement corresponds to a billing-related installation of device D2 on the 01 of March 2000 in device location DL1 and the installations Inst.1 and
Inst.2.
( )
This produces the following results for March 01, 2000:
( )
Reversing Device Replacements:
You want to reverse the device replacement. Proceed as follows:
1. Execute a billing-related device removal of device D2 from the Inst.2 installation on March 01, 2000.
You have now reversed the billing-related installation of device D2 in the installation Inst.2 on March 01, 2000.
2. Execute a billing-related device removal of device D2 from the Inst.1 installation for March 01, 2000.
You have now reversed the billing-related installation of device D2 in the installation (Inst.) 1 for March 01, 2000.
3. Reverse the device replacement.
( )
This produces the following results for March 01, 2000:
( )
4. Perform a billing-related device installation of device D1 in installation 1 for March 01, 2000.
5. Perform a billing-related device installation of device D1 for March 01, 2000 in installation 2.
( )
Purpose
You use this component to enter changes to a device. You can modify warehouse devices and devices installed in the grid.
If devices are already installed in the grid, the installation structure is adjusted as necessary.
This component is optional. You can use it for resetting device parameters as well as reprogramming, modifying, and reconnecting devices. Examples of
modification include:
Changing the register configuration of a device
Using a different winding of a transformer
Features
Modification includes the following functions:
Changing the device master data (such as register group or input/output group)
Changing set values (such as measured pressure or the command group)
Changing device-specific gas data (such as the altitude correction pressure)
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you modify an AMI device (for example, a
Use
This function allows you to change device data and register data. This function does not allow you to change device categories, however.
Prerequisites
Note the following:
The contract for the installation of the device must not have been billed before the modification date.
When you enter the modification, the device must not have been modified or changed in the system after the actual modification date. The entry in the
system must correspond to the actual history of the processes.
Example
You enter the modification on 10/12. The installation took place on 10/08. A device modification or a change to the device data may not have been
entered after 10/08.
Special prerequisites for modification
Activity Prerequisites
Change device data of current time slice The device has undergone technical removal.
Change technical data of registers in any time slice The device has undergone technical installation.
Activities
If you have changed technical register data, you must enter meter reading results for the corresponding registers.
To allocate another device category (material) to the device, go to one of the following application components, depending on where the device is managed:
Inventory Management (MM-IM)
Plant Maintenance (PM)
If you modify an installed device in the current time slice, you can change the device’s register allocation during the modification.
If parameters such as the measured pressure or the billing factor were changed for a device in a device allocation, the device allocations are adjusted as
necessary.
A message is displayed if the automatic adjustment is not possible. You can go directly to the device allocation and check and adjust the attribute
manually. To do this, choose Goto Device allocations .
If data of registers in register relationships has changed, you can branch to register relationship maintenance and adjust the data.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you modify an AMI device (for example, a
1.2.8.1.1 Entry of Meter Reading Results During Modification

Prerequisites
You have changed the technical register data.
Procedure
Choose Utilities industry Device management Meter reading Entry of meter reading results Single entry.
1.2.8.1.2 Allocation of Different Device Category via MM-IM
Prerequisites
The device you wish to modify is maintained in the Inventory Management (MM-IM) application component.
Procedure
1. Choose Logistics Materials management Inventory management.
2. Choose Goods movement Transfer posting
You branch to the screen for entering transfer postings.
3. Enter movement type 309 (transfer posting material to material). You must also enter a storage location and a plant. Chose Continue .
You branch to the screen for entering new transfer posting items. Here you can carry out all transfer postings.
Result
A different device category (material) has been allocated to the device.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you change the device category of an AMI
device (for example, a smart meter or advanced meter).
1.2.8.1.3 Allocation of Different Device Category via PM
Prerequisites
The device you wish to modify is not maintained in the Inventory Management (MM-IM) application component.
Procedure
1. Choose Logistics Plant maintenance Technical Objects
2. Choose Serial numbers Change and enter the serial number.Chose Continue .
3. Choose Serial data and then Edit Change material no.
The Change material serial number dialog box appears.
4. Enter the new material. Chose Continue .
Note
You may be notified of the system status of the device (piece of equipment).
5. Save your data.
Result
A different device category (material) has been allocated to the device.
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS as soon as you change the device category of an AMI
device (for example, a smart meter or advanced meter).
1.2.9 Installation Structure

Purpose
You can use this component to manage technical and billing data as well as period consumption of devices.
Features
Technical data
Device allocations describe dependencies of devices with other devices, such as meters controlled by ripple control receivers or a group of transformers
connected to a meter.
Register relationships describe the relationships between registers. The registers can belong to different contracts. The following
relationships are taken into account when creating a meter reading order:
Allocation of active registers to reactive registers for calculating the cosine phi
Serial switching of several registers (primary/secondary meter relationships)
Linking of registers to different usage types (on-peak/off-peak check)
Control relationships
Special relationships for allocating thermal gas factors
Logical registers describe the allocation of a certain task to a register and are most important in device replacement. The register of the old device must
have the same logical register number as the register of the new device because
billing data is copied to the new register
the billing component must recognize which register is to take over the role of the old device (especially in the case of demand values)
Billing data
Rate data is dependent on the installation and therefore can only be maintained if the device is allocated to an installation. You can maintain rate data such as:
The relevance of a register to billing
The rate type of a register
The price class
Period consumption
The period consumption is used to determine the expected meter reading of a register for a certain date if meter reading results
Are not yet available, such as in the case of initial data creation
Cannot be used, for example if there is a change of tenant
Are to be ignored, for example if the customer has a complaint regarding budget billing
1.2.9.1 Device Allocation
Use
This function enables you to allocate devices to one another and store additional attributes.
A distinction is made between controlled devices, such as meters, and controlling devices, such as a transformer switched in series.
Integration
You usually define device allocations on the initial screen for device installation.
The device allocation is terminated if one of the devices undergoes a technical removal, however when you reverse a device removal, any device allocations that
were terminated are restored.
Similarly:
if you reverse a device installation, any device allocations that were created are terminated.
If you reverse a device replacement, any device allocations that were created are terminated while any device allocations that were terminated are restored.
Meter Data Unification and Synchronization (MDUS) System Notification for AMI Devices
If you work within an advanced metering infrastructure (AMI) environment, the system notifies the MDUS system as soon as you generate:
a new allocation involving an AMI device (for example, a smart meter or advanced meter)
a new allocation involving registers belonging to an AMI device
The system also modifies the MDUS system when you allocate a profile to registers belonging to an AMI meter.
Prerequisites
The devices to be allocated to one another must have undergone a technical installation and have certain characteristics depending on the allocation type. Only
water or gas meters or pressure regulators may be part of a pressure regulator allocation. Only meters that measure indirectly can be in a transformer allocation.
Features
Device allocation is historical.
Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice
into two slices and maintain them.
Example
Time slice: 01/01/1996 to 12/31/1999
Period already billed: 01/01/1996 to 12/31/1999
The time slice is divided into two time slices: 01/01/96 to 12/31/1996 and 01/01/1997 to 12/31/9999.
The unlimited time slice is not in the period billed and therefore can be maintained.
It is also possible to define an allocation without an allocated device in order to store the attributes of the device allocation. For example, measured pressure can
be stored in a pressure regulator allocation although the pressure regulators do no exist in the system.
The attributes measured pressure for the pressure regulator allocation or billing factor for transformer allocations are relevant to billing and mandatory for gas
meters or meters that do not measure directly.
Device allocations can be defined at the register or device level of the controlled device. Metering devices (meaning devices with registers) are allocated at the
register level. Devices without registers are always allocated at the device level. The controlling device is always entirely allocated to the controlled device.
It is possible that a controlling device (such as a ripple control receiver) has been replaced during the time slice of the device allocation. In this case, the device
that is valid at the beginning of the time slice is displayed. You must also set the TM indicator (device not valid for the entire period). You can double-click on this
indicator to display the valid devices with corresponding validity periods. You can also display these devices by selecting the appropriate line and choosing
Extras History
It is also possible to define your own allocation types. To do this, you add new entries to the table of allocation types. These allocations are not relevant to billing,
however.
Activities
When you maintain billing-relevant device allocations, you must enter meter readings for the devices. In the case of sub-annual changes, you must enter meter
readings manually.
1.2.9.1.1 Creating Device Allocations
Prerequisites
The devices have undergone a technical installation.
You now wish to maintain device allocations.
Procedure
Choose Device installation → Installation structure → Device allocations → Maintain
You branch to the initial screen.
Choose a device location, installation or controlled device.
You can only choose an installation here if the controlled device has been allocated to an installation. You can choose whether the data is to be restricted to the key
date or whether the time slice valid for the key date is to be displayed.
An allocation already exists for the device in the unlimited time slice starting on January 1, 1998.
If you execute this function for the key date March 1, 1998 and choose the Prorate indicator, you branch to the new, unlimited contract starting on March 1, 1998.
The existing time slice is divided into two time slices, one ending on February 28 and one starting on March 1. You can make changes during the period of the
second time slice.
If you execute the function for the key date March 1 without prorating the time slice, you branch to the maintenance screen for the time slice valid on the key date.
In the example, the time slice valid on the key date is the original unlimited time slice starting on January 1.
You can also choose Time slices to display a list of time slices, select a time slice from the list or restrict a time slice.
The controlled devices are displayed on the maintenance screen. All of the devices selected are displayed along with the corresponding device relationships.
To make it easier for you to enter new relationships, an empty line is provided for each device and register.
Each device relationship at the register level is also displayed for purposes of information at the device level. If the RV indicator is set, the allocation is valid for
all registers of the device.
Enter the controlled device, the allocation type, the controlling device and the attribute for allocation. Choose Enter .
The text for the allocation type and the attribute description are displayed. You can also define allocations for controlled devices at the device level. The allocations
at the register level are then automatically generated and displayed. SAP recommends this procedure for devices with many registers. If necessary, you can
correct individual allocations after they are generated.
Once you have entered all allocations, save your data.
In the case of sub-annual changes, you must enter meter reading date for controlled metering devices. Choose Meter reading → Entry of meter reading results
→ Single entry. You branch to the initial screen.
Enter a meter reading result for the device on the date of the change.
Save your data.
1.2.9.2 Rate data
Use
The rate data of a device provides the basis for billing the device in an installation. Rate data exists at the device and register levels. Rate data at the device level
is required for device rental prices. Rate data at the register level is required for settlement of consumption and demand.
Rate data is divided into multiple-installation data and installation-specific data. Multiple-installation data is unique for all installations to which the device is
allocated. Installation-specific data is maintained independently of the installation.
Multiple-installation data might include the thermal gas billing procedure and the linear and percentage consumption portion. Installation-specific data might
include the indicator for relevance to billing, the rate type and the price class.
Integration
When a device undergoes a billing-related installation, it is allocated to an installation along with its rate data.
When the device undergoes a billing-related removal, its rate data is no longer stored historically.
Prerequisites
The device has undergone a billing-related installation.
Features
Rate data is maintained historically.
Time slices in periods that have already been billed can no longer be changed. These time slices can only be displayed. However, you can divide one time slice
into two slices and maintain them.
Multiple-installation data is displayed on one line with the installation-specific data. If you change multiple-installation data, this affects all installations to which the
register is allocated.
If you must maintain the rate data of a register in several installations at once, then you can only enter multiple-installation data in the first line of the register. In the
subsequent lines for the register that apply to other installations, the multiple-installation data is only displayed.
Activities
In the case of large changes to rate data (such as changes to the indicator for billing relevance or to the consumption portion), meter readings must be entered for
the devices. In the case of sub-annual changes, you must enter meter readings manually.
1.2.9.3 Register Relationship
Use
The function allows you to map the relationship between two or more registers.
You find the transactions for register relationships in the Utilities Industry menu under Device Management → Installation → Installation Structure → Register
Relationships
Prerequisites
The device must first undergo a technical installation.
Activities
The meter reading results of the registers in question must be determined.
Deleting Registers from the Existing Register Relationship

If you want delete the registers of a device from an existing register relationship, you cannot enter this device in the initial screen of the Change Register
Relationships transaction. If you do enter the device to be removed, the system issues the message EN478 (at least one register must correspond to initial data)
when you try to save the data.
Enter one of the following objects instead:
Another device from the register relationship
The device location where the devices are installed
The installation where the devices are installed
Make sure when you enter the device location or installation that there is at least one other device in the register relationship installed in the device location or
installation.
Limitations when Processing Register Relationships
General Limitations
All registers affected by the register relationship must be installed over the whole processing period. A register relationship can only exist once within a period.
Customizing Restrictions
You can find the Customizing settings for register relationships under SAP Utilities → Tools → System Modifications → User-Defined Function Enhancement
for Register Relationships
All devices effected by the register relationship must belong to a division for which the register relationship category is permissible.
See Define Permissible Register Relationships per Division Category in Customizing.
Only operation codes that have been defined as permissible for this register relationship category can be used The number of operation codes must be within the
range set in Customizing
See Define Operation Code per Register Relationship in Customizing.
If the UM field (units of measurement must match) is selected in Customizing, all registers in the register relationship must have the same unit of measurement.
See Define Types of Register Relationships in Customizing.
If the SA field (installations must match) is selected in Customizing, all registers in the register relationship must have been installed (billing-relevant) in the
same installation.
See Define Types of Register Relationships in Customizing.
Restrictions for Different Register Relationship Types
Restriction for Active/Reactive Relationship 01

Reactive and active registers must have the same register category. The system does differentiate between cumulative and balancing registers.
For the reactive register, enterreactive registerin the RA field (difference between reactive, apparent and active registers).
For the active register, enteractive registerin the RA field.
For the active register, enteractive registerin the RA field.
Restrictions for Serial Switching Relationship 02
Serial Switching only for Consumption Registers

Serial switching is only supported for consumption registers. Primary and secondary registers must therefore have the register categories cumulative or
balancingconsumption register.
Serial switching of demand registers is not possible. In demand registers, the measured demand peaks from primary and secondary registers do not necessarily
occur at the same time. The difference of demand from the primary register minus the demand from the secondary register does not match the demand that is to
be billed for the primary meter.
If you already have serial switching demand registers in your company, you must map these using special rates:
You can calculate the difference between primary and secondary register demand using the DEMAND02 variation.
If necessary, you can use DEMAN09 to multiply the demand difference with a reduction factor.
You must define your own type of register relationship if want both demand registers to be read at the same time.
You can define this in Customizing under: SAP Utilities → Tools → System Modifications → User-Defined Enhancements for Register Relationships →
Define Types of Register Relationships
Serial Switching of Different Secondary Registers

The primary meter can only be the primary meter in one serial switching relationship. You can allocate more than one secondary meter to one primary meter in a
serial switching relationship, however. If this is the case, the total of all secondary meter consumptions is subtracted from primary meter consumption.
Multilevel serial switching is also possible. A secondary meter can also be a primary meter.
To do this, you must create two serial switching relationships.
Reactive/Active Indicators
Primary and secondary reactive/active indicators must match.
Installation Allocation
During the serial switching period, all secondary meters must be installed (billing-related) in the same installations as the primary meter.
We also recommend that you select the N (register not billing-relevant) field in the primary meter installation.
You must enter a rate type for the secondary meters in the main meter installation. You must also do this when the field N (register not billing-relevant) is
selected.
( ) Example 1:
Device D1 is allocated to installation A.

Device D2 is allocated to installation B.
You want to create a register relationship with D1 as the primary meter and D2 as secondary meter. Proceed as follows:
Step 1:Allocate device D2 to installation A.
Rate data from installation A:
Device Register Rate Type Register Not Billing-Relevant Rate
D1 1 RA '' RT10
G2 1 RA X RT10
Rate data from installation B:
Device Register Rate Type Register Not Billing-Relevant Rate
G2 1 RB '' RT50
Step 2:Create the register relationship.
Device Register Operations Code
D1 1 3 (Primary register)
G2 1 4 (Secondary register)
When you bill installation A, the consumption from device D2 is subtracted from the consumption of device D1 in rate RT10.The consumption of device D2 is not
evaluated.
( ) Example 2:
In example 1, device D2 was allocated rate RT10 in installation A, and rate RT50 in installation B. This is only permitted if both rates have the same weighting
procedure, billing unit of measurement, and minimum portion. This is not the case for example 2.
Device D1 is allocated to installation A. Installation A is a commercial enterprise. Device D1 is to be billed using rate RT80. RT80 has linear weighting (weigh)
and billing unit of measurement (UM) MWh.
Device D2 is allocated to installation B. Installation B is a normal household. Device D2 is to be billed using rate RT50. RT80 has weighting of energy feeding and
the billing unit of measurement kWh.
Both devices must be switched after each other, with D1 as the primary meter and D2 as the secondary meter.
You can no longer allocate the same rate types to the devices D1 and D2 in installation A. Instead, you must enter a rate type for device D2 that determines a rate
compatible with the RT50 rate.
Rate data from installation A:
Device Register Rate Type Register Not Bill.-Rel. Rate Billing Unit of Weighting Procedure
Measurement
D1 1 RA '' RT80 MWh Linear
G2 1 RC X RT30 kWh Weighting of energy

feeding
Rate data from installation B:
Device Register Rate Type Register Not Bill.-Rel. Rate Billing Unit of Weighting Procedure
Measurement
G2 1 RB '' RT50 kWh Weighting of energy

feeding
Result
When you enter meter reading results for D2, the plausibility checks are always executed with the billing unit of measurement kWH and weighting of energy
feeding. The plausibility check and extrapolation of meter reading results from D2 are dependent on whether they refer to installation A or B. The indicator N
(register not billing-relevant) does not effect the entry of meter reading results.
When installation A is billed, both devices D1 and D2 are allocated to the rate RT80. The meter reading differences in consumption for both devices are converted
into MWh. The MWh consumption of the secondary meter is subtracted from the MWh consumption of the primary meter. Rate RT30 is not used for billing
installation A because the field N (register not billing-relevant) is selected.
If there has been a price change in the billing period, both registers undergo linear proration. This not completely correct but cannot be avoided. If different
weighting occurs, secondary meter consumption in a prorated time slice may be calculated higher than primary meter consumption.This can occur even when the
total primary meter consumption is larger than the total secondary meter consumption.As a result of this, we recommend that you avoid using different weighting
whenever possible.
Register Discount
You can also offer discount on registers that are serially switched. Note the order in which the serial switching and register discount are processed in billing:
Firstly, non-discount secondary register consumptions are subtracted from non-discount primary register consumption (=deduction consumption).
If a register discount is entered for the primary register, the deduction consumption is also discounted.
A register discount on the secondary register does not effect the primary register consumption to be billed.
If, for example, meter reading results from a secondary meter have to be changed due to transformation losses, you cannot use register discounts.If this is the
case, you must enter a suitable register factor for the secondary meter.The register factor is included in billing before the deduction consumption is calculated.
Restrictions in a Primary Rate – Secondary Rate Relationship

Primary and secondary registers must have the same register category.The system does differentiate between cumulative and balancing registers.
The entry in the BW field must be the same for the primary and secondary rate register.
Restrictions in Control Relationship 04

Register and control register must have the same register category.The system does differentiate between cumulative and balancing registers.
The entry in the BW field must be the same for the register and control register.
Restrictions in Volume Correction Factor Relationship 05

Both registers must have the same register category.The system does differentiate between cumulative and balancing registers.
The register that transfers the volume correction factor can only occur in one register relationship of the categories volume correction factor relationship and volume
correction factor calculation.
The register that inherits the volume correction factor can occur again in a register relationship as an operating volume register.
Restrictions in Volume Correction Factor Calculation 06

Both registers must have the same register category.The system does differentiate between cumulative and balancing registers.
The standard volume register can only occur in one register relationship of the categories volume correction factor relationship and volume correction factor
calculation.
The operating volume register can occur again in a register relationship as a volume correction factor inheriting register.
Restrictions in Resetting Relationship 07

The reset register must be a balancing register.
If a tax group has been entered for the resetting register, it must correspond to the tax group entered for the reset register.
The resetting register and reset register can only be present in one resetting relationship.
Restrictions in Pulse Relationship 08

Both registers must have the same register category. The system does differentiate between cumulative and balancing registers.
The entry in the BW field must be the same for the register and control register.
Restrictions in Usage Hour Relationship 09

Only watt registers and consumption registers can be used.
1.2.9.4 Period consumption
Use
In order to determine the expected meter reading for a register on a specific date, you need data on the metering patterns of the register or the consumption
patterns of the customer. You can take this information from previous meter reading results, from a predefined period consumption or from a predefined period unit.
The period consumption or the period unit is required to determine expected values for extrapolation if any of the following points apply:
A representative base period does not yet exist (for example, for meter readings after installation and move-in)
The consumption patterns of the customer have changed (for example, if the number of people living in the household has changed)
The physical conditions of the customer’s environment have changed (for example, by converting the measuring accuracy (register factor) of the meter
during the extrapolation period)
The calculation of meter readings and budget billing amounts to be extrapolated, has been influenced (for example, if the rate framework or the consumption
patterns of a customer have changed)
Integration
To enter a period unit or period consumption, choose Utilities Industry Device Management Device Installation Installation Structure Period
Consumption Maintain (transaction EL56) in the menu.
You can also find the period consumption in transaction Installation: all data (EG31). To do this, choose Utilities Industry Device Management Device
Installation Installation Full in the menu. It is mandatory to enter the period consumption during device installation as it represents the basis for
extrapolation if no meter reading results are available.
Features
To enter or change the period consumption, enter a contract, an installation or a device as well as a date in transaction Maintain Period Consumption and choose
Continue . On the next screen, a list of all registers will be displayed with their valid period values according to the date you entered. To display a register’s
metering pattern from the installation date, position the cursor on the relevant line and choose Maintain History . On this screen, period values and meter reading
results are displayed for the selected register.
When you change the period consumption, you must pay attention to the following points in order to keep settings consistent:
You must enter a period for which the new period consumption is valid. You must ensure that validity periods for the various consumption values do not
overlap and are without gaps from installation time to removal time or from installation time to infinity. The system performs the appropriate consistency
checks.
You should always enter or change the period consumption on the entry date of meter reading results, for technical installation, for installation relevant to
billing or the time of installation. Entries or changes must be complete by the day after at the very latest.
If you do not do this and you define the period consumption from a date that is more than one day after the last meter reading, the calculation of the expected
consumption for the forecast period is split into two subintervals. This may cause two period consumption values to be created for extrapolation and can lead to
distortion when determining the expected consumption. This can lead to distortion when determining the expected consumption.
Example:
( )
A period consumption value of 4500 kWh / year was entered on 01.02 This was changed to 2500 kWh / year on 12.15 (within the forecast period).
The sum of the weighting units for one year is 1000.
The expected meter reading is determined in the following way:
1. For the period 11.30. to 12.15, when the change was made, the expected meter reading is extrapolated based on the previous period consumption.
Determination of consumption per weighting unit by dividing the period consumption by the weight of validity period.
4,500 kWh: 1000 = 4.5 kWh
Extrapolation of consumption for period 11.30. to the date when changes to the period consumption were made on 12.15:
4.5 kWh 50 = 225 kWh
1. For the period from the change date to 12.31, consumption is extrapolated from the new period consumption.
Determination of consumption per weighting unit by dividing the period consumption by the weight of validity period.
2,500 kWh: 1000 = 2.5 kWh
Extrapolation of period consumption for the period from the change date on 12.15. to 12.31:
2.5 kWh50 = 125 kWh
1. Determination of the expected meter reading on 12.31. by adding the consumption values from the meter reading on 11.30:
1200 kWh + 225 kWh + 125 kWh = 1550 kWh
For the first subinterval, the period consumption valid from 01.02. (4500 kWh / year) is created. For the second subinterval, the period consumption valid from
15.12. (2500 kWh / year) is created. As the old period consumption no longer truly reflects the consumption patterns of the customer, the extrapolation results are
also distorted.
1.2.9.4.1 Period Consumption and Usage Factor Concepts
Consumption forecasts are used in various business processes, for example to create budget billing plans for schedule creation and settlement. When
determining these consumption forecasts, different algorithms are used in the different business processes so that the forecasts are not numerically identical.
While period consumption comes into effect for classical extrapolation, the automatically calculated usage factor is used in market communication for scheduling
and settlement.
Description of Problem
There is no function in billing that allows the consumption billed in invoicing to be transferred to the installation facts, the period consumption, and the usage factor.
Therefore, the data basis between the distributor and supplier systems cannot diverge. The leads to the need for clarification between market participants in
subsequent processes such as billing overtake and undertake amounts.
How does this relate to the concepts of period consumption and the usage factor?
Period Consumption
Period consumption is one of the main parameters of classical extrapolation. During extrapolation, the period consumption is calculated automatically and used
together with the manually set period consumption to determine the expected consumption value. The values are not persisted to the database. Period
consumption is register-related.
For more information, see Period Consumption
Usage Factor
The usage factor is installation-related. It refers to a standard load profile. The usage factor is automatically updated during billing and billing reversal and codes
the actual consumption. All values are persisted to the database. You can influence the forecasted usage factor that is used for invoicing and scheduling by
defining the interface methods of the Adjust Usage Factor business add-in (ISU_EDM_USAGEFACTOR) for your specific company.
1.2.9.5 Logical Register Number

Use
The logical register number links the actual register to the logical register.
The allocation of technical register to logical register occurs automatically during an installation relevant to technical data. You must maintain the logical register
number if you replace devices using the replacement function instead of the separate installation and removal functions.
Integration
A technical removal ends the history of logical registers unless they are passed on to another device.
Prerequisites
The device must have undergone a technical installation and have registers.
Features
The logical register number is maintained historically.
Time slices in periods that have already billed can no longer be changed. These time slices can only be displayed. However, you can obtain a maintainable time
slice by dividing one time slice into two slices.
If you do this, the selected registers for one key date and the registers for the previous day are displayed on one screen. The register is then allocated by copying
the logical register number of another register. The logical register number is symbolized by a four-digit dummy number.
Activities
During logical register number maintenance, you must enter meter readings for the relevant devices manually.
1.2.9.5.1 Changing Logical Register Numbers

Prerequisites
The devices have undergone a technical installation.
For purposes of billing, you must allocate old registers to new registers when you carry out a replacement, removal, or installation.
Procedure
1. Choose Device installation Installation structure Logical register number Change
2. You branch to the initial screen.
3. Choose a device location or an installation.
4. You can choose whether the data is to be restricted to the key date or whether the time slice valid for the key date is to be displayed.
You can also choose Time slices to display a list of time slices, select a time slice from the list or restrict a time slice.
The number of registers installed in the device location on the key date is displayed on the right side of the maintenance screen. The number of registers
installed in the device location on the day before the key date is displayed on the left side of the screen.
5. Allocate a register on the left to a register on the right by entering a dummy logical register from the left side for the corresponding register on the right side.
6. Repeat this action for several time slices, if necessary.
7. Save your data.
8. In the case of sub-annual changes, you must enter meter reading date for controlled metering devices.
9. Choose Meter reading Entry of meter reading results Single entry. You branch to the initial screen.
10. Enter a meter reading result for the device on the date of the change.
11. Save your data.
1.3 Reading Meters
Purpose
This component allows you to organize meter readings and meter reading results. Devices are either read periodically for periodic billing or aperiodically, such as
for control meter readings and readings at the time of device replacement, removal, or disconnection.
Devices can also be read for a certain activity, such as a move-in or a removal. In this case, the meter reading is triggered directly by the activity, and not by the
Meter Reading component.
Meter Reading Process
First, the meter reading order is created and printed as a meter reading document or downloaded to an external entry system. The meter reading results are either
entered manually or uploaded.They are then validated and corrected, if necessary. The results are then forwarded to the Contract Billing (IS-U-BI) component.
Integration
The following Business Application Programming Interfaces (BAPI) are available in the Business Object Repository (BOR) for selecting meter reading orders and
results:
MeterReadingDocument.GetList (select meter reading orders and results)
MeterReadingDocument.Upload (upload meter reading results)
For more information about BAPIs see the following documentation:
For general information, see the BAPI User Manual and the BAPI Program Manual
For more detailed information, see the documentation of the individual BAPIs.
1.3.1 Base Period
The base period is the period that contains all meter readings used as the basis for estimation.
The length of the base period results from a dynamic stop condition. The base period is representative - this means it is long enough if one of the following two
conditions is met:
The minimum length of the base period is covered
The weighting portion of the base period is greater or equal to the percentage minimum share in the rate
The system determines the base period by working back one at a time from the last meter reading result to previous meter reading results until one of the two
conditions is met.
Minimum Length of Base Period

The minimum length of the base period is defined as follows:
Minimum length of base period = Percentage minimum share * Period length of portion
You enter the percentage minimum share in the rate:
Menu for Utilities Industry Billing Master Data Define Rates .
You define the period length of the portion in scheduling:
Menu for the Utilities Industry Scheduling Scheduling Master Record Portion .
The period length of the portion determines the interval in which the corresponding contracts are billed.
Weighting Portion
The weighting portion of the base period must be greater or equal to the percentage minimum share.
You enter the percentage minimum share in the rate:
Menu for Utilities Industry Billing Master Data Define Rates .
The weighting portion results from the weighting procedure being used.
For more information about weighting procedures, see Weighting Procedures.
1.3.2 Weighting Procedure
During estimation, assumptions are made regarding the time-related distribution of the quantity on which the estimation is based. This distribution is described with
a weighting function y(t). Weighting procedures are internal procedures that are used during extrapolation and proration of existing meter reading results or period
consumption and period demand to determine the expected values. The weighting procedure also determines how representative the basis period is.
For more information about base periods, see Base Periods.
Features
The following weighting procedures are predefined in the system:
Linear weighting
Weighting of energy feeding
Degree day weighting
Sprinkling water portion
General weighting
User-defined weighting
You use the weighting procedures by specifying a weighting key. You define the weighting keys in Customizing under SAP Utilities Device Management
Meter Reading Weighting Procedures Define Weighting Key(s) .
For more information, see the documentation for the Customizing activity.
The weighting procedures predefined by SAP are described in more detail in the following sections. You can also use a mixed weighting in addition to these
procedures. For more information, see Examples for Mixed Weighting.
Linear Weighting
For linear weighting, the weighting units are distributed evenly over the year, whereby the system takes one weighting unit into account for each day. The total of
the weighting values is 365 days for one year, or 366 days for a leap year.
To use this weighting procedure, allocate it to a weighting key in Customizing. No further Customizing settings are required.
Weighting of Energy Feeding

This weighting procedure takes seasonal fluctuations into account. With weighting of energy feeding, you have the option to take average monthly energy feeding
quantities into account, or to determine the energy feeding quantities for each defined period and use these.
To use this weighting procedure, allocate it to a weighting key in Customizing. You also have to make the following Customizing settings:
Average Monthly Energy Feeding
Customizing for SAP Utilities under Device Management Meter Reading Weighting Procedures Weighting of Energy Feeding Define Average
Monthly Energy Feeding .
Energy Feeding per Period
Customizing for SAP Utilities under Device Management Meter Reading Weighting Procedures Weighting of Energy Feeding Define Energy
Feeding per Period .
Degree Day Weighting

This weighting procedure takes seasonal fluctuations into account. With degree day weighting, you have the option to take average monthly degree day coefficients
into account, or to determine degree day coefficients for an exact number of days and to use these.
To use this weighting procedure, allocate it to a weighting key in Customizing. You also have to make the following settings in Customizing for SAP Utilities under
Device Management Meter Reading Weighting Procedures Degree Day Weighting :
Define Temperature Areas
The temperature areas are used as criteria for differentiation during degree day weighting and thermal gas billing.
Depending on whether you want to take average monthly degree day coefficients or degree day coefficients for an exact number of days into account, you have
make settings in the following activities:
Define Average Monthly Degree Day Coefficients
Define Degree Day Coefficients
Example
To simplify the example, the same degree day coefficient has been defined for temperature area 0001 for every day of a month in Customizing under Define
Average Degree Day Coefficients :
Degree Day Degree Day Coefficient
01.01.- 01.31. 20.00
02.01.- 02.28. 18.00
03.01.- 03.31. 15.00
04.01.- 04.30. 10.00
05.01.- 05.31. 5.00
06.01.- 06.30. 1.00
07.01.- 07.31. 1.00
08.01.- 08.31. 5.00
09.01.- 09.30. 10.00
10.01.- 10.31. 15.00
11.01.- 11.30. 18.00
12.01.- 12.31. 20.00
The result of this is that the degree day coefficients for the summer months have a lower weighting during estimation than those for the winter months. This is
shown in the following figure:
The system calculates the total of the weighting values for a month. In the example, this results in the following weighting values per month:
Month Total of Weighting Values
01 620.00
02 540.00
03 465.00
04 300.00
05 155.00
06 30.00
07 31.00
08 155.00
09 300.00
10 465.00
11 540.00
12 620.00
The total of the weighting values is 4,221.00.

The following parameters also apply:
The base period is one year.
The period consumption is used as a basis for estimation. The period consumption is 1,000 kWh.
You want to determine the expected consumption for 02.01.
Expected Consumption = Period Consumption (1,000) * Partial Weighting of Estimation Period (620.00) / Weighting of Base Period (4,221.00) = 146.88
General Weighting
In this weighting procedure, you define the weighting units that are valid for a specified period. The periods for the distribution of weighting units are indicated by
month and day, and are not dependent on the year. The weighting portion of a period is the result of the ratio of the weighting units for that period to the weighting
units for the year.
To use this weighting procedure, allocate it to a weighting key in Customizing.
You define the weighting units in Customizing for SAP Utilities under Device Management Meter Reading Weighting Procedures General Weighting
Define Weighting Units .
Example
The following settings have been defined in Customizing under Define Weighting Units for weighting key 05:
Weighting Key Valid From Partial Weighting
05 01.01. 150.00
05 02.01. 120.00
05 03.01. 100.00
05 04.01. 90.00
05 05.01. 60.00
05 06.01. 30.00
05 07.01. 10.00
05 08.01. 30.00
05 09.01. 60.00
05 10.01. 100.00
05 11.01. 110.00
05 12.01. 140.00
The total of the weighting values for weighting key 05 is 1,000.00.

The following parameters also apply:
The base period is one year.
The period consumption is used as a basis for estimation. The period consumption is 1,000 kWh.
You want to determine the expected consumption for 02.01.
Expected Consumption = Period Consumption (1,000) * Partial Weighting of Estimation Period (150.00) / Weighting of Base Period (1,000.00) = 150.00
User-Defined Weighting
You can define and use your own company-specific weighting procedures in addtion to those predefined by SAP.
To do so, define the following business add-ins (BAdI)s
User-Defined Consumption per Weighting Unit (ISU_BENDEF_EPVG)
Determination of User-Defined Weighting Total (ISU_BENDEF_WEIGHTING)
1.3.2.1 Examples for Mixed Weighting
The following examples describe extrapolation with mixed weightings. The examples use degree day weighting which is defined with the following values in
Customizing for SAP Utilities under Device Management Meter Reading Weighting Procedures :
Note: Degree day weightings are absolute values without units. They only represent weightings and not measured energy quantities. The weighting values relate
to calendar days of a year, not to months. Therefore, for the total weighting of an extrapolation period, each individual day has to be taken into account with the
respective degree day weighting. Calculation example: The total of the degree day weightings for the period January 1 to January 31 is 31 * 20 = 620. This is the
result of 31 days with the weighting 20.
Example
Degree day weighting with consumption percentage for weighting
The following data and general conditions apply:
Register type: Cumulative consumption register
Weighting key: Degree day weighting
Mixed weighting: Consumption percentage for weighting = 10%
Base period category: Previous period
Length of base period: 12 months
Period consumption = 5,000 kWh
The example contains a move-in on January 1, 2009 with an initial move-in meter reading. Extrapolation is executed three times based on the period
consumption with reference to the date of the move-in meter reading.
From the consumption percentage for weighting, you can derive that 500 kWh (10% of the period consumption) is used during extrapolation for the linear
consumption percentage and is distributed evenly over all 365 days. The remaining 4,500 kWh from the period consumption are incorporated into
extrapolation by means of degree day weighting and are distributed as shown in the figure Degree Day Weighting .
The following weighting totals are calculated in Customizing for the relevant periods:
Period Total for Degree Day Weighting
01.01.2009 – 01.31.2009 620
01.01.2009 – 06.30.2009 2495
01.01.2009 – 12.31.2009 4395
Formula for extrapolation:

For degree day weighting with a consumption percentage for weighting, the consumption comprises of two parts:
Extrapolated Consumption = Degree Day Weighted Consumption + Linear Consumption Percentage
Both parts contain consumption determined as follows:
Degree Day Weighting Consumption = Period Consumption * 90% * (Total from Degree Day Weighting / Degree Day Annual Weighting)
Linear Consumption Percentage = Period Consumption * 10% (No. Days / 365)
The percentage results from the available data.
Results of Extrapolation by Using Known Values
Note: The results are rounded to 2 decimal places.
Example
Degree day weighting with consumption to be weighted linearly
The following data and general conditions apply:
Register type: Cumulative consumption register
Weighting key: Degree day weighting
Mixed weighting: Consumption to be weighted linearly = 10 kWh with validity period June 1 to August 31.
Base period category: Previous period
Length of base period: 12 months
Period consumption = 5,000 kWh
The example contains a move-in on January 1, 2009 with an initial move-in meter reading. Extrapolation is executed three times based on the period
consumption with reference to the date of the move-in meter reading.
From the consumption to be weighted linearly, you can derive that 920 kWh (92 days in the period June 1 to August 8 at 10 kWh/day) is used during
extrapolation for the linear consumption. The remaining 4,080 kWh from the period consumption are incorporated into extrapolation by means of degree day
weighting and are distributed as shown in the figure Degree Day Weighting .
The following weighting totals are calculated in Customizing for the relevant periods:
Period Total for Degree Day Weighting
01.01.2009 – 01.31.2009 620
01.01.2009 – 06.30.2009 2495
01.01.2009 – 12.31.2009 4395
Formula for extrapolation:

For degree day weighting with consumption to be weighted linearly, the consumption comprises of two parts:
Extrapolated Consumption = Degree Day Weighted Consumption + Absolute Linear Consumption
Both parts contain consumption determined as follows:
Degree Day Weighted Consumption = (Period Consumption - Linear Weighted Consumption * Validity Period)1) * )Total from Degree Day Weighting / Degree
Day Annual Weighting)
Linear Consumption Percentage = Linear Weighted Consumption per Day * Number of Days
1) According to data provided in example, a value of 4,080 kWh
Results of Extrapolation by Using Known Values
Note: The results are rounded to 2 decimal places.
In order to determine the expected consumption or the expected performance for a register on a specific date, you need data on the metering patterns of the
register.
You can take this information from previous meter reading results, from a predefined periodic consumption value or from a predefined period demand.
The base period from which the expected values are calculated is very important during extrapolation. The period in which bases are created to determine
expected values during extrapolation are included in the base period. Using the base period category field in the installation, you can control whether to
extrapolate the expected values based on the previous period or the period of the previous year.
Meter reading results are the ideal base from which to determine expected values, as these results best reflect the consumption patterns of the customer. In order
to use meter reading results, you must ensure that the base period (the interval between the first and the last meter reading result) used for extrapolation is
representative.
You can only extrapolate from a previous period, if it is representative. Whether a period is representative or not is a result of the original weighting procedure.
Determining Whether a Period is Representative
To determine whether a base period is representative, use the following information:
Weighting portion of period = Minimum portion
or
Minimum portion in percent * Length of meter reading period
= Minimum length of base period
Example
The following meter reading reasons exist:
P eriodic meter reading
F inal meter reading
Meter reading at move-in ( M )
Meter reading at installation ( I )
Interim meter reading without billing ( Y )
Interim meter reading with billing ( Z )
C ontrol meter reading
The period length of the portion is 1 year (365 days)
The minimum portion defined in the rate is 50%
The minimum requirements to determine whether the base period is representative are determined in the following way:
Weighting portion of period = Minimum portion
or
Minimum portion in percent (50%) * Length of meter reading period (365 days)
= Minimum length of base period (182.5 days)
In the example, the base period must have a minimum weighting portion of 50% or be at least 182.5 days long in order to be representative.
( )
The period from P to Y is not representative because it does not have the minimum weighting portion (only 20% rather than the required 50%). This means that
this period alone cannot be used as a basis for extrapolation. The system goes back to the previous reading (I). The period from P to I is representative because it
has a weighting portion of 20% + 60% = 80%. The period from P to I can be used as a basis for extrapolation.
Meter Reading Results or Period Value as a Basis for Extrapolation
The system determines whether to use meter reading results or a selected period value as a basis for extrapolation in the following way:
Based on the last correct meter reading results, the system goes back to the previous reading and runs through the following process:
( )
If you enter a modified periodic consumption in transaction Maintain Periodic Consumption (EL 56) for a point in time that lies within the base period for the next
extrapolation, the system will inform you that the entered periodic consumption can influence the extrapolation results.
Determination of Expected Consumption for Consumption Registers
Determination of the expected consumption based on the meter reading results
1. You can calculate the consumption per unit of weight from the determined consumption and the determined weight of the base period:
2. Determined consumption of base period: Determined weight of base period
= Consumption per unit of weight
3. To determine the expected consumption of the forecast period, multiply the consumption per unit of weight by the weight of the forecast period.
4. Consumption per unit of weight * Weight of forecast period
= Expected consumption of forecast period
5. The expected meter reading is calculated from the expected consumption with the help of special parameters (register factor, billing factor, dimension
conversion table).
Determination of the expected consumption based on the period consumption
The following reasons can result in the period consumption being used as a basis for extrapolation:
Not enough meter reading results are available
You entered the period consumption before a representative point in time was created by the updating of meter reading results
The expected consumption is determined in the following way:
1. The consumption per unit of weight is calculated from the period consumption and the weight of its validity period:
2. Period consumption Weight of the period consumption validity period
= Consumption per unit of weight
3. To determine the expected consumption of the forecast period, multiply the consumption per unit of weight by the weight of the forecast period:
4. Consumption per unit of weight * Weight of forecast period
= Expected consumption of forecast period
5. The expected meter reading is calculated from the expected consumption with the help of special parameters (register factor, billing factor, dimension
conversion table).
Determination of the Expected Demand for Demand Registers
Determining the expected demand for demand registers is a similar process to determining the expected consumption for consumption registers. Demand per unit
of weight is, however, not calculated. In this case, you must determine the highest demand for the base period.
Determination of the expected demand based on the meter reading results
1. Determination of the highest meter reading in the base period
2. The determined demand corresponds to the expected demand
Determination of the expected demand based on the period demand
The following reasons can result in the period demand being used as a basis for extrapolation:
Not enough meter reading results are available
You entered the period demand before a representative point in time was created by the updating of meter reading results
The expected demand is determined in the following way:
1. Determination of the period demand
2. The determined period demand corresponds to the expected demand
1.3.3.1 Extrapolation for Consumption Registers

( )
Reg. Fact. = Register factor
MR Result = Meter Reading Result
MR Reason = Meter reading reason
The following meter reading reasons exist:
P eriodic meter reading
F inal meter reading
Meter reading at move-in ( M )
Meter reading at installation ( I )
Interim meter reading without billing ( Y )
Interim meter reading with billing ( Z )
C ontrol meter reading
Wght. Units = Weighting units
Expected meter readings are determined by consumption registers as follows:
1. Determination of meter reading difference P 1 to I:
2. 80 kWh – 0 kWh = 80 kWh
3. Determination of consumption to P 1 by multiplying the meter reading difference with the register factor:
4. 80 kWh2 = 160 kWh
5. Determination of consumption per weighting unit:
6. 160 kWh: 40 = 4 kWh
7. Extrapolation of consumption for period P 1 to P 2
8. 4 kWh60 = 240 kWh
9. Determination of the meter reading difference for period P 1 to P 2 by dividing the consumption value by the register factor:
10. 240 kWh: 10 = 24 kWh
11. Determination of the expected meter reading to P 2 by adding the meter reading difference to meter reading P 1 :
80 kWh + 24 kWh = 104 kWh
When you calculate expected meter reading values from existing meter readings, you must take the minimum portions into account. In the previous example, we
assume that period P 1 to I is representative.
Forecasts from Previous Periods
If you include previous periods as the base period category in the installation, the expected meter reading values are calculated based on the corresponding
previous period .
Example 1: Forecasts from previous periods with minimum portions
( )
On installation of the device, a period consumption value of 4000 kWh/year is entered for the register.
The minimum portion of weighting in percent is 30%.
With a weighting portion of 40%, period Y to I is representative. This means that extrapolation is based on meter reading results rather than on period consumption.
1. Determination of meter reading difference Y to I:
2. 800 kWh – 0 kWh = 800 kWh
3. Determination of consumption to Y by multiplying the meter reading difference with the register factor:
4. 800 kWh2 = 1600 kWh
6. 1,600 kWh: 400 = 4 kWh
7. Extrapolation of consumption for period Y to P
8. 4 kWh600 = 2,400 kWh
9. Determination of the meter reading difference for period Y to P by dividing the consumption value by the register factor:
10. 2,400 kWh: 10 = 240 kWh
11. Determination of the expected meter reading to P by adding the meter reading difference to meter reading Y:
800 kWh + 240 kWh = 1040 kWh
The expected meter reading at time P is 1,040 kWh .
Example 2: Forecasts from Previous Periods without Minimum Portions with Period Consumption
( )
With a weighting portion of 20%, period Y to I is not representative. Therefore, extrapolation is based on period consumption rather than on meter reading results:
1. Determination of period consumption per weighting unit by dividing the period consumption by the weight of validity period.
2. 4000 kWh: 1000 = 4 kWh
3. Extrapolation of period consumption for period Y to P:
4. 4 kWh800 = 3,200 kWh
6. 3,200 kWh: 10 = 320 kWh
800 kWh + 320 kWh = 1120 kWh
Example 3: Forecasts from Previous Periods and Changes to Period Consumption Values in the Base Period
( )
On installation of the device, a period consumption value of 4000 kWh/year is entered for the register. This value is changed to 5000kWh / year for the period I to
C.
With a weighting portion of 10%, period Y to C is not representative. The system goes back to the next meter reading result (I). With 40%, the period Y to I is
representative, however, the period consumption value was changed within this period. Therefore, extrapolation is based on period consumption rather than on
meter reading results:
2. 5,000 kWh: 1000 = 5 kWh
3. Extrapolation of period consumption for period Y to P:
4. 5 kWh600 = 3,000 kWh
6. 3,000 kWh: 10 = 300 kWh
800 kWh + 300 kWh = 1100 kWh
Example 4: Forecasts from Previous Periods and Changes to Period Consumption Values not in the Base Period
( )
On installation of the device, a period consumption value of 4000 kWh/year is entered for the register. This value is changed to 5000kWh / year for the period I to
Z.
With a weighting portion of 10%, period Y to C is not representative. The system goes back to the previous meter reading result (Z). With 30%, the period Y to Z is
representative and the period consumption value was not changed within this period. Therefore, extrapolation is based on meter reading results rather than on
period consumption:
1. Determination of meter reading difference Y to Z:
2. (800 kWh – 720 kWh) + (720 kWh – 500 kWh) = 300 kWh
4. 300 kWh2 = 600 kWh
6. 600 kWh: 300 = 2 kWh
7. Extrapolation of consumption for period Y to P
8. 2 kWh600 = 1200 kWh
10. 1,200 kWh: 10 = 120 kWh
800 kWh + 120 kWh = 920 kWh
The expected meter reading at time P is 920 kWh .
Example 5: Forecasts from Previous Periods and Changes to Period Consumption Values in the Forecast Period
( )
On installation of the device, a period consumption value of 4000 kWh/year is entered for the register. This value is changed to 5000 kWh / year after the last
meter reading result entry in period Y to P.
With a weighting portion of 40%, period Y to I is representative. One period consumption change was made in the forecast period Y to P. The expected meter
reading is determined in the following way:
1. For the period from Y until the change date, extrapolation is based on meter reading results:
2. 800 kWh - 0 kWh = 800 kWh
4. 800 kWh2 = 1600 kWh
6. 1,600 kWh: 400 = 4 kWh
7. Extrapolation of consumption for period Y until the change date:
8. 4 kWh400 = 1600 kWh
9. Determination of the meter reading difference for period Y until the change date by dividing the consumption value by the register factor:
1,600 kWh: 10 = 160 kWh
1. For the period from the change date to P, consumption is extrapolated from the period consumption:
2. 1. Determination of period consumption per weighting unit by dividing the period consumption by the weight of validity period.
2. 5,000 kWh: 1000 = 5 kWh
3. Extrapolation of period consumption for the period from the change date to P:
4. 5 kWh200 = 1,000 kWh
5. Determination of the meter reading difference for the period from the change date to P by dividing the consumption value by the register factor:
1000 kWh: 10 = 100 kWh
3. Determination of the expected meter reading to P by adding the meter reading differences to meter reading Y:
800 kWh +160 kWh + 100 kWh = 1060 kWh
Forecasts from the Period of the Previous Year
If you include periods of the previous year as the base period category in the installation, the expected meter reading values are extrapolated based on the
corresponding period of the previous year .
Based on a forecast date, the system goes back one year and looks for a representative period as a basis for extrapolation.
Note the following exceptions:
Extrapolation for the expected meter readings is based on the previous period rather than the period of the previous year if:
No representative period is determined due to a lack of meter reading results.
A change has been made to the period consumption value since the day of the last meter reading
Changes to the period consumption are only relevant for periods that follow directly after. If you change the period consumption value after the last meter reading
results are taken, the changes only influence forecast periods that come immediately afterwards.
If, however, you want the period consumption to influence the four following forecast periods, you have to enter a period consumption value in every quarter or, on
the day of a meter reading result entry, change the period consumption value for the next quarter.
Example 6: Forecasts from the Period of the Previous year and Changes to Period Consumption Values in the Base Period
( )
On 1.1.96 a period consumption value of 1000 kWh / year was entered for the register. On.5.1.96 for the period T 1 to T 2 .this value was changed to 1200 kWh /
year.
With a weighting portion of 30%, period T 2 to T 1 from the previous year is representative. A change to the period consumption was made within this period. This
change does not, however, influence extrapolation for time T 5 , because a period consumption change only influences forecast periods that follow directly after.
1. Determination of meter reading difference T 2 to T 1 :
2. 1200 kWh - 1000 kWh = 200 kWh
=> Consumption to T2 = 200 kWh
4. 200 kWh: 300 = 2/3 kWh
5. Extrapolation of consumption for period T 4 to T 5 :
6. 2/3 kWh300 = 200 kWh
=> Meter reading difference for period T 4 to T 5 = 200 kWh
7. Determination of the expected meter reading to T 5 by adding the meter reading difference to the meter reading from T 4 :
2000 kWh + 200 kWh = 2200 kWh
The expected meter reading at time T 5 is 2200 kWh .
Example 7: Forecasts from Periods of the Previous Year and Changes to Period Consumption in the Previous Year but not in the Base Period
( )
On 1.1.96 a period consumption value of 1000 kWh / year was entered for the register. On 11.1.96 for the period T 2 and T 3 .this value was changed to 1200
kWh / year.
With a weighting portion of 30%, period T 2 to T 1 from the previous year is representative. No changes were made to the period consumption within this period.
The changes that were made to the period consumption between T 2 and T 3 do not influence extrapolation for time T 5 because change to the period consumption
only influences forecast periods that follow directly after.
The expected meter reading is determined as in example 6.
Example 8: Forecasts from the Period of the Previous year and Changes to Period Consumption Values in the Forecast Period
( )
On 1.1.96 a period consumption value of 1000 kWh / year was entered for the register. On 4.1.97, for the period T 4 and T 5, this value was changed to 1200 kWh
/ year directly after the last periodic meter reading result entry
Because a change to the period consumption influences the forecast periods that follow directly, in this case, extrapolation is based on the period consumption
value rather than the meter reading results of the previous year.
2. 1,200 kWh: 1000 = 1.2 kWh
3. Extrapolation of consumption for period T 4 to T 5 :
4. 1.2 kWh300 = 360 kWh
5. Determination of the expected meter reading to T 5 by adding the consumption to the meter reading from T 4 :
2,000 kWh + 360 kWh = 2360 kWh
The expected meter reading at time T 5 is 2,360 kWh .
The change to the period consumption on 4.1.97 no longer has an influence on the determination of the expected consumption for T 6 on 09.30.97 as this is not the
forecast period that follows directly. Extrapolation is based on the period of the previous year.
If you want to extrapolate the expected consumption on the basis of period consumption, you have to enter the period consumption value for the next quarter on the
day of the last periodic meter reading result entry (T 5 = 97.6.30).
Example 9: Forecasts from period of previous year but period of previous year does not yet exist
If you enter period of previous year in the installation of the base period category but no period of previous year exists (because there has only been a
contractual relationship with the customer for half a year for example), extrapolation will occur based on the previous period.
Example 10: Forecast from Period of Previous Year where Period of Previous Year is not Representative
If you include period of previous year in the installation of the base period category, but the period of previous year is not representative, extrapolation occurs
based on the previous period.
Example 11: Forecast from Period of Previous Year and Changes in Period Consumption during Customer Change
( )
During installation it is clear that the consumption pattern of the new customer is different from that of the previous customer (because there are more people in the
household, for example). Therefore, a new period consumption value is entered during installation.
The base period category period of previous year is entered in the installation.
Because a change to the period consumption influences the forecast periods that follow directly, in this case, extrapolation is based on the period consumption
value rather than the meter reading results of the previous year.
2. 3,000 kWh: 1000 = 3 kWh
3. Extrapolation of consumption for period I to T 4 :
4. 3 kWh300 = 900 kWh
5. Determination of the expected meter reading to T 4 by adding the consumption to the meter reading from I:
2,000 kWh + 900 kWh = 2,900 kWh
The expected meter reading at time T 4 is 2900 kWh .
The period consumption value entered at the time of meter reading I, no longer influences the determination of future expected consumption values.
They are extrapolated from the relevant periods of the previous year. Extrapolation based on the period of the previous year would not be correct in this case,
because of the knowledge we have about the consumption patterns of the new customer.
For this reason, extrapolation is based on a previous period or a period consumption value for one year after installation, even if the base period category period of
previous year is entered in the installation.
After the device has been installed for a year, extrapolation is based on the period of the previous year.
1.3.3.2 Extrapolation for Demand Registers

In the case of demand registers, the highest demand is taken into account in a representative interval as an expected value, in order to determine expected
meter readings from the previous period. In the case of cumulative demand registers, the highest demand difference is taken into account.
Expected meter readings for demand registers are determined as follows:
1. Determination of the highest meter reading from previous reading Y 2 over a representative interval (Y 2 to I):
180 kW
2. Determined demand = expected demand:
180 kW
When you calculate expected meter reading values from existing meter readings, you must take the minimum portions into account. In the previous example, we
assume that period Y 2 to I is representative.
Demand registers always refer to the linear weighting procedure in their rate.
Note
If demand needs to be extrapolated for billing, the expected meter reading values are determined differently. For more information, see Extrapolation of
Demand from Billing .
Forecasts from Previous Periods

If you include previous periods as the base period category in the installation, the expected meter reading values are calculated based on the corresponding
previous period .
In the following example, we assume that the demand registers are balanced.
Example 1:Forecasts from previous periods with minimum portions
On installation of the device, a period demand value of 200 kWh/year is entered for the register.
With a weighting portion of 40%, period Y 2 to I is representative. This means that extrapolation is based on meter reading results rather than on the period
demand.
1. Determination of the highest meter reading from previous reading Y 2 over a representative interval (Y 2 to I):
180 kW
2. Determined demand = expected demand:
180 kW
Example 2:Forecasts from previous periods without minimum portions with period demand
On installation of the device, a period demand value of 200 kWh/year is entered for the register.
With a weighting portion of 20%, period Y to I is not representative. Therefore, extrapolation is based on the period demand rather than on the meter reading
results:
The expected meter reading result is 200 kW .
Example 3: Forecasts from previous periods and changes to period demand in the base period
On installation of the device, a period demand value of 200 kWh/year is entered for the register. This value is changed to 220 kWh / year for the period I to C.
With a weighting portion of 10%, period Y to C is not representative. The system goes back to the next meter reading result (I). With 40%, the period Y to I is
representative, however, the period demand was changed within this period. Therefore, extrapolation is based on the period demand rather than on the meter
reading results:
Example 4: Forecasts from previous periods and changes to period demand not in the base period
As no changes were made to the period demand within the base period, extrapolation is based on meter reading results rather than on period demand.
Example 5: Forecasts from previous periods and changes to period demand in the forecast period
The period demand can still be changed after the last meter reading result entry during the forecast period. This results in the following:
On installation of the device, a period demand value of 200 kWh/year is entered for the register. This value is changed to 220 kWh / year after the last meter
reading result entry in period Y to P.
With a weighting portion of 40%, period Y to I is representative. One period consumption change was made in the forecast period Y to P. The expected meter
reading is determined based on the period demand and equals 220 kW .
Forecasts from the Period of the Previous Year

If you include periods of the previous year as the base period category in the installation, the expected meter reading values are extrapolated based on the
corresponding period of the previous year .
For the forecast from the period of the previous year, the search algorithm for demand registers differs from the search algorithm for consumption registers as
follows:
Demand Registers Consumption Registers
The system only looks for meter reading results in the previous year with the same The system goes back one year from the forecast date and looks for a representative
allocation month as the expected meter readings period
It is not important whether the period of previous year is representative It is important that the period of previous year is representative
If no corresponding period of the previous year is available, extrapolation is based on the previous period.
P(4) = periodic meter reading for allocation month April

P(5) = periodic meter reading for allocation month May, and so on
The expected meter reading for P(5) is determined based on the demand with the same allocation month from the period of the previous year (P(5) = 120 kW)
Example 6:Forecasts from the period of the previous year and changes to period demand in the base period
Period demand was changed in the period P(5) to P(4). This change does not, however, influence extrapolation for time P(5) (5.1.97), because a change in period
demand only influences the forecast period that follows directly after.
Example 7:Forecasts from period of the previous year and changes to period demand in the previous year but not in the
base period
On 1.1.96 a period demand value of 100 kWh / year was entered for the register. On 11.1.96 for the period P(5) and P(12) this value was changed to 150 kWh /
year.
No changes were made to the period demand in the period P(5) to P(4). The changes that were made to the period demand between P(5) and P(12) do not
influence extrapolation for time P(5) (97.5.1),because changes to the period demand only influence the forecast period that follows directly after.
The expected meter reading is determined as in example 6.
Example 8:Forecasts from the period of previous year and changes to period demand in the forecast period
On 1.1.96 a period demand value of 100 kWh / year was entered for the register. On P(4) (4.1.96), this was changed to 120 kW / year.
In contrast to consumption registers, and in the case of demand registers, meter reading results have priority over changes to period demand in the current
forecast period.
Therefore, if the system finds a meter reading result with the same allocation month in the period of the previous year, this result is used for extrapolation instead of
the period demand.
Example 9:Forecasts from period of previous year but period of previous year does not yet exist
If you enter period of previous year in the installation of the base period category but no period of previous year exists (because there has only been a
contractual relationship with the customer for half a year for example), extrapolation is based on the previous period, as in the case of consumption registers.
1.3.3.3 Extrapolation for Resetting Registers

Extrapolation of resetting registers is limited to determining the previous meter reading and increasing it by 1. For the preparation of multiple resetting registers, the
expected meter reading is determined from the previous meter reading plus the number of meter reading orders created between the previous meter reading and
the current meter reading.
1.3.3.4 Extrapolation with Billing Factor

The expected meter reading is calculated from the expected consumption with the help of special parameters (register factor, billing factor, dimension conversion
table). The following example shows the significance of the billing factor.
With a weighting portion of 40%, period Y to I is representative. This means that extrapolation is based on meter reading results rather than on period consumption.
800 kWh – 0 kWh = 800 kWh
800 kWh * 2 = 1600 kWh
3. Determination of consumption to Y by multiplying the meter reading difference with the conversion factor (gas):
1,600 kWh * 10 = 16,000 kWh
4. Determination of consumption to Y by multiplying with the billing factor:
16,000 kWh * 1.5 = 24,000 kWh
24,000 kWh: 400 = 60 kWh
6. Extrapolation of fictitious consumption for period Y to P:
60 kWh * 600 = 36,000 kWh
7. Determination of the actual, new consumption for period P based on the quotient of the new and the old billing factor
8. (36,000 kWh : 1.5) * 2 kWh * 2 = 48,000 kWh
9. Determination of the meter reading difference for period Y to P by dividing the consumption value by the billing factor:
48,000 kWh : 2 = 24,000 kWh
10. Determination of the meter reading difference for period Y to P by dividing the consumption value by the conversion factor (gas):
24,000 kWh : 12 = 2,000 kWh
2,000 kWh : 10 = 200 kWh
800 kWh + 200 kWh = 1,000 kWh
The billing factor effects the expected consumption. As a result of weighting distribution, the consumption value from the base period is transformed to the
extrapolation period and given the value of the new billing factor. The new expected consumption value is then divided by the factors that are valid on the
extrapolation date (register factor, conversion factors) in order to determine the expected meter reading values.
During extrapolation, the conversion factors are determined on a key date (in the same way as the register factors). This means that the conversion factors are
defined for the extrapolation date (this is usually the planned meter reading date) in order to transform the expected consumption value into an expected meter
reading value. In billing, the entire billing period is analyzed for changed conversion factors and is then valuated and prorated accordingly. This is not possible for
extrapolation as the data is not yet available when extrapolation takes place.
For more information on valuating the billing period with gas factors, see the documentation for contract billing in the implementation guide (IMG) under Special
Functions -> Gas Billing .
1.3.3.5 Proration of Meter Readings

Proration is the division of a billing period due to data changes.
Example:
A rate is changed during a billing period. Consumption in the first half of the billing period is calculated using the old rate whereas consumption in the second half
is calculated with the new. In order to do this, the meter reading at the time of the rate change must be determined.
( )
The proration meter reading is determined in the following way:
1. Determination of meter reading difference between C and P 2 :
2. 1,905 kWh -1,000 kWh = 905 kWh
4. 905 kWh: (90 + 91) = 5 kWh
5. Extrapolation of consumption for period from P 2 to the time of data change (April 01, 1997):
6. 5 kWh90 = 450 kWh
7. Determination of proration meter reading at the time of the rate change by adding the consumption to the meter reading at P 2 :
1,000 kWh + 450 kWh = 1,450 kWh
Proration meter reading on April 01, 1997 is 1,450 kWh.
1.3.3.6 Extrapolation of Demand from Billing
Use
In meter reading, the highest demand value in a representative interval is used as the expected value for determining the expected meter reading values from the
previous period for demand registers.
However, this demand value is not always sufficient for billing purposes. Therefore, for the extrapolation of demand values from billing, the system calls a table of
values, which are transferred to the extrapolation period. The source of these values can be any of the following:
Actual meter reading results from the extrapolation period
Period consumption values from the extrapolation period
Values from a comparable period from the base period
Prerequisites
The base period does not have to be representative (as it does for extrapolation for meter reading).
Features
The extrapolation of demand values from billing consists of the following steps:
1. Determination of the extrapolation period
( )
2. Determination of actual meter reading results with a meter reading period that overlaps with the extrapolation period
Transfer of meter reading results to the extrapolation period
( )
3. Determination of the time variability
Transfer of schedule records to the extrapolation period
( )
4. Determination of period consumption
Transfer of period consumption to the extrapolation period
( )
5. Determination of gaps in the extrapolation period, that are neither covered by actual meter reading results nor by period consumption values
( )
Transfer of meter reading results from the base period to the gaps in the extrapolation period
( )
Example
Six-monthly meter reading and billing of the average from the peak values of each half year
For the budget billing calculation of the year 2000, both demand values from 1999 are used with their allocations to the 2 half years. This is the only way to
ensure that the same average value is calculated for 2000 as for 1999 (5+3/2).
Quarterly billing with three multiple meter reading orders; Each demand value is cleared separately for the relevant month
If the base period is the same as the previous period, the relevant demand values from the three previous months are used and transferred to the extrapolation
period.
1.3.4 Meter Reading Organization
Purpose
This component allows you to define the Street Route for all devices to be read in the service territory and make mass changes to meter reading units.
1.3.4.1 Street Route
Purpose
You can use this component to define the sequence in which the devices in a service territory are to be read. Doing this can optimize the meter reader’s route.
The following criteria are used in defining the street route in a meter reading unit:
City
Street
House Number (connection object)
Device Location
Device
Street Route
( )
This component is optional. You require it if you wish to optimize the meter reader’s route.
Features
You can maintain the street route for a single meter reading unit or you can create a shared street route for several meter reading units. Before you can use a
shared street route, you must allocate the meter reading units in the relevant schedule records to one another.
The following enhancements can be used for the street route:
EDMLSORT (IS-U: Sort Meter Reading Orders for Printout and Download)
This enhancement allows you to define your own sort sequence for printing or downloading meter reading orders.
1.3.4.1.1 Maintain Street Route for Meter Reading Unit
Prerequisites
Installations and corresponding devices have been allocated to the meter reading unit.
Procedure
1. Choose Utilities industry Device management Meter reading Meter Reading Organization Street route.
2. Enter a meter reading unit and choose Street route Maintain .
Note
If you want to specify a shared street route for several meter reading units, enter the main meter reading unit.
The Maintain street route dialog box appears. On this screen, all devices are under the top node Devices not allocated to a street route .
1. Allocate all devices from the top node to the bottom node Devices allocated to the street route .
1. To change the route or to allocate devices to a route:
1. Select either an object, a node or a block.
2. Position your cursor on the item selected.
3. Choose Edit Reassign.
1. Save the street route.
Result
The street route is used to either:
Sort devices on printouts when you print meter reading orders for the meter reader.
Sort devices in the file created when you download meter reading orders.
Note
You can define your own meter reading route with enhancement EDMLSORT.
1.3.4.2 Planning Meter Readers
Usage
You use this function after creating an order to allocate selected meter readers to individual or multiple meter reading orders or to change existing allocations.
This function provides greater flexibility in unexpected situations (such as illness) as meter readers can now be allocated temporarily to meter reading orders.
Prerequisites
To use this function, you must first select the Plan Meter Reader indicator in Customizing for SAP Utilities under Device Management Meter Reading
Meter Reading Order Order Creation Define Meter Reader .
Features
If you have selected this indicator for a meter reader in Customizing, you can use the Schedule Meter Reader transaction after order creation and before
downloading the meter reading orders to external mobile data media to allocate meter reading orders or change existing allocations.
You can find the transaction in the Utilities Industry menu under Device Management -> Meter Reading -> Meter Reading Organization -> Schedule Meter
Reader .
1.3.4.3 Mass Changes to Meter Reading Units
Use
You use this function to change the meter reading unit in several installations for a key date.
This function supports the business process for changing meter reading units as a result of organizational changes or changes to areas. If for example new areas
are to be supplied, this can mean that existing meter reading units become too large, meaning that new meter reading units are added.
Prerequisites
1. Define parameter groups.
You enter the meter reading unit to be replaced, the new meter reading unit and the date on which the change is to take place in the parameter groups.
To define parameter groups, in the Utilities Industry menu, choose Device Management Meter Reading Meter Reading Organization Define
Parameter Groups .
For more information, see the field help.
2. Change the meter reading unit and allocate it to a parameter group.
Features
The Mass Changes to Meter Reading Unit function performs the following changes:
All installations that are allocated to certain meter reading units and certain regional structure groups are allocated to a new meter reading unit on the date
specified.
1.3.5 Meter Reading Order
Purpose
This component allows you to create a meter reading order for each register. The order contains register-specific data and information about the planned meter
reading, such as the meter reader and the scheduled meter reading date. Meter reading orders can be created for:
Meter readers from the utility company
External meter reading companies
Meter reading by the customer
Integration
Types of meter readings and their scheduled dates are defined in the Portioning and Scheduling (IS-U-BF-PS) component. You can override the scheduled meter
reading type and select another type of meter reading. For example, instead of selecting the meter reading type Meter reading by the customer you can create
an order for a meter reader. In addition, you can specify dates for aperiodic meter readings manually.
Business Repository
The Business Object Repository (BOR) contains the following Business Application Programming Interface (BAPI) for selecting meter reading orders and results:
MeterReadingDocument.GetList (selection of meter reading orders or results)
For more information about BAPIs see the following documentation:
For general information, see the BAPI User Manual and the BAPI Program Manual
For more detailed information, see the documentation of the individual BAPIs.
Features
You can reverse meter reading orders. If meter reading results exist at the time of the reversal, you can either delete them or retain them for use in another meter
reading order.
During meter reading order creation, you control the sequence of meter readings of different categories. You have the following options:
You can enter a fixed schedule in the schedule master record for the meter reading unit. To do this, you select the Use MR cat. from sched. rec. field
during order creation (individual or mass order creation). The system then creates meter reading orders for meter readings in the category you have entered.
Example
You want to read meters every month. To reduce the number of meter readers, you allow for two estimations and one subsequent reading by a meter
reader. You enter meter reading dates for each month with the corresponding schedule meter reading category in the meter reading unit. The sequence
of the dates is retained even if the customer moves out, for example.
You can define meter reading control settings in Customizing under Device Management -> Meter Reading -> Basic Settings . During mass order creation,
you enter a scheduled meter reading category. The system checks whether meter reading control settings permit this meter reading category for the
installation and then creates meter reading orders for the installations accordingly.
Example
You want to allow each installation to be read by the customer twice and then once by the meter reader. You define meter reading control settings
accordingly in Customizing and enter them in the installation. You perform mass order creation twice for each meter reading, the first time with customer
reading as the scheduled meter reading category, and the second time with meter reading by the utility as the scheduled category.
Meter reading date September 30 October 30 November 30
Installation 1 MR by customer MR by customer MR by utility
Installation 2 MR by customer MR by utility (move-out) MR by customer
One order each is created for September 30 and October 30 during the first order creation run for installation 1. However, the meter reading control settings
no longer allow this for November 30. A meter reading order is not created for the installation until the second order creation run.
The utility company reads meters on October 30 for installation 2 because the customer has moved out.A meter reading order is created for November 30
during the first order creation run as permitted by the meter reading control settings.
1.3.5.1 Meter Reading Order Creation
Purpose
This component allows you to create:
Individual meter reading orders
These orders are usually created for aperiodic billing (for example, for interim and control billings or if a meter reading unit is handed over to another utility
company).
You can also create single orders for periodic billing if an order has to be created again due to a mistake, for example.
Mass meter reading orders
In the case of periodic meter readings, orders for several meter reading units can be created simultaneously.
Meter reading orders are not created for flat-rate installations because these installations do not contain metering devices.
You can also create a service order or notification for aperiodic orders.
Integration
You can transfer data to external systems using IDoc ISU_RPL_ORDER.
1.3.5.1.1 Single Order Creation
Use
This function allows you to create single orders for aperiodic billing. You might need to create single orders for interim and control billings or if a meter reading unit
is handed over to another utility company, for example. You can also create single orders for periodic billings if a specific order has to be created again due to a
mistake.
Integration
You can create individual orders for device installation, removal or replacement, during move-in processing or for individual entry of meter reading results. If you
create an individual order to enter a single meter reading result, this does not necessarily mean that meter reading documents are created automatically. You can
also use the entry function to create individual orders. In this case, the system creates the data structures for entry and validation internally.
Prerequisites
Single order creation may be based on either schedule records, which are generated in scheduling (order creation for periodic meter reading), or on the dates for
meter reading and billing that you have entered (depending on the meter reading reason). Billing takes place according the meter reading reason.
Features
You can create meter reading orders at the following levels:
Meter reading unit
Contract
Installation
Device
Each level is permitted for certain meter reading reasons only. You can display the corresponding meter reading reasons for each level via possible entries.
Each order creation process is linked to certain dates. You can enter any date, except in the case of periodic meter readings. If the meter reading reason is
relevant to billing, enter both a scheduled meter reading date and a scheduled meter reading date so that a billing order can be created. If you create meter
reading orders for a periodic meter reading, the system uses the dates from scheduling. The scheduled meter reading category is always meter reading by the
company.
You can enter one allocation date (on a daily basis) for meter reading and billing respectively. The allocation date of the meter reading is transferred to the meter
reading result.
The following three indicators allow you to control single order creation externally:
Use MR cat. from sched. rec.
If you select this field, the meter reading category in scheduling has priority. This allows you to create orders for meter reading by the customer if the schedule
record contains the appropriate meter reading category. For more information, see Meter Reading Control .
Meter reading interval check
If you select this field, the system checks wither a meter reading order or result exists within the meter reading interval. If so, the system suppresses the meter
reading order with the meter reading reason with lowest priority.
You can speed up order creation by not selecting this field. In this case, the order is always created, even if you have defined meter reading reason priorities for
interval checks.
Ignore contracts
If you select this field, the contracts for which orders have already been created are not checked for completeness the next time you carry out billing-related order
creation. This improves performance when you repeat order creation.
Suppress service orders
If you select this field, the system prevents creation of service orders that are normally created automatically as per customizing settings.
1.3.5.1.2 Mass Order Creation
Use
This function allows you to create meter reading orders for more multiple meter reading units and dates.
Prerequisites
Schedule records must already exist when you create mass orders. Schedule records are created in the scheduling component.
Features
You can only create meter reading orders for one or more meter reading units. There must also be at least one schedule record with an order date within the period
entered during mass order creation.
You can control mass order creation using the following fields:
Scheduled meter reading categ.
If you enter a scheduled meter reading category and do not select the Use MR cat. from sched. rec field, the system creates meter reading orders for the
scheduled meter reading category entered here. This allows you to create multiple orders for meter reading by the customer and subsequently for meter reading
by the utility company. In this case the scheduled meter reading category from the schedule record is ignored.
Use MRC from scheduling (Use scheduled meter reading category from scheduling)
If you select this field, the system creates orders with the meter reading category in the scheduling component. In the meter reading unit, you can define a schema
with schedule records of certain meter reading categories. If you select this field during order creation, the system creates orders with the appropriate meter
reading category. This allows you to control the sequence of meter readings with different categories at the level of the meter reading unit or order creation.
The system ignores settings for meter reading type control and uses the meter reading category from scheduling.
Example
If you enter meter reading category 03 (automatic estimation), all meter reading orders are estimated immediately during order creation.
Meter reading interval check

If you select this field, the system checks wither a meter reading order or result exists within the meter reading interval. If so, the system suppresses the meter
reading order with the meter reading reason with the lowest priority.
You can speed up order creation by not selecting this field. The order is then always created, even if you have defined meter reading reason priorities for interval
checks.
Ignore contracts
If you select this field, the contracts for which orders have already been created are not checked for completeness the next time you carry out billing-related order
creation. This improves performance when you repeat order creation.
Activities
You can schedule mass order creation in background jobs for better performance. You enter the selection criteria and save them as a variant. You can then
supply this variant with start parameters and schedule it to run in a background job.
1.3.5.1.3 Meter Reading Control

During meter reading order creation, you control the sequence of meter readings of different categories. You have the following options:
You can enter a fixed schedule in the schedule master record for the meter reading unit. When you create orders, select the Use MR cat. from sched. rec.
field. The system then creates meter reading orders for meter readings in the category you have entered.
Example
You want to read meters every month. To reduce the number of meter readers, you allow for two estimations and one subsequent reading by a meter reader.
You enter meter reading dates for each month with the corresponding schedule meter reading categories in the meter reading unit. The sequence of the dates
is retained even if the customer moves out, for example.
You can define meter reading control settings in Customizing under Device Management -> Meter Reading -> Basic Settings . During mass order creation,
you enter a scheduled meter reading category. The system checks whether meter reading control settings permit this meter reading category for the
installation and then creates meter reading orders for the installations accordingly.
Example
You want to allow each installation to be read by the customer twice and then once by the meter reader. You define meter reading control settings accordingly
in Customizing and enter them in the installation. You perform mass order creation twice for each meter reading, the first time with customer reading as the
scheduled meter reading category, and the second time with meter reading by the utility as the scheduled category.
Meter reading date 30.09. 30.10. 30.11.
Installation 1 MR by customer MR by customer MR by utility
Installation 2 MR by customer MR by utility (move-in/out) MR by customer
One order each is created for 09/30 and 10/30 during the first order creation run for installation 1. Meter reading control settings no longer allow this for 11/30,
however. A meter reading order is not created for the installation until the second order creation run.
The utility company reads meters on 10/30 for installation 2 because the customer has moved out. A meter reading order is created for 11/30 during the first order
creation run as permitted by meter reading control settings.
1.3.7 Reversal
Reversing meter reading deletes all objects generated during creation of meter reading orders and entry of meter reading results:
Meter reading orders
Meter reading results (optional)
Billing orders
Reversal may be necessary in the following cases:
You determine the scheduling data was incorrect after you created periodic meter reading orders for a meter reading unit.
You enter an incorrect device when creating a control meter reading order.
Features
On the initial screen you can choose whether the meter reading results:
Are to be deleted
Meter reading orders, meter reading results, and billing orders are deleted. New meter reading orders are created when meter reading order creation is
carried out again.
Are not to be deleted
Only meter reading orders and billing orders are deleted, not meter reading results. When meter reading order creation is carried out again, ew meter
reading orders are only created for devices that were not read. No new meter reading orders are created for devices that have already been read, as the
corresponding meter reading results were not deleted.
Meter reading orders and results that have already been billed can only be reversed if the corresponding billing documents have been reversed first. You can find
the reversal transactions for Billing in the Utilities Industry menu under Billing Billing Execution Reversal .
Meter reading results that were entered during installation, replacement, or removal of devices can only be reversed in the respective reversal transactions for
installation, replacement, or removal. They can then be deleted. You can find the reversal transactions for installation/replacement/removal in the Utilities Industry
menu under Device Management Installation .
1.3.5.2 Order Output
Purpose
This component allows you to:
Print meter reading documents
You can print meter reading orders or forms for meter reading by the customer, depending on the type of meter reading scheduled.
Download meter reading order via raw data interface (RDI)
You can download orders as a spool file or an IDoc.
You can transfer orders via an RDI to external entry systems, such as MDE devices (mobile data entry) and document readers (download), or print them from
external printing systems.
In both methods, the application form you use defines the data output. This allows you to output essentially all data in the system.
Integration
You use the Print Workbench application component to create application forms.
You maintain application forms in the schedule record of the meter reading unit in the Portioning and Scheduling (IS-U-BF-PS) component. You can specify an
alternative form during order output.
If you want order output to start automatically via batch jobs, you schedule the jobs by maintaining the relevant intervals in the schedule record of the meter
reading unit.
Example
Examples of intervals include:
Interval between order creation and scheduled meter reading date

Interval between download and scheduled meter reading date
1.3.6 Meter Reading Result
This component manages meter readings and devices. They can be determined in the following ways:
Meter reading by the utility company:
A meter reader from the utility company or from an external meter reading company enters the result in the meter reading order, or in the external system.
Meter reading by the customer:
The customers read the results themselves and report them to the utility company.
Automatic estimation:
The result is estimated automatically.
Derivation
The meter reading result is determined from a meter reading result that has already been entered. This result must be within the entry interval. This prevents
the entry of meter readings that lie too close together.
In addition to the meter reading result, the system also saves the way in which the meter reading was determined.
Integration
For more information about uploading meter reading results, see Upload.
1.3.6.1 Entry of Meter Reading Results
You can use this component to enter mass data (from periodic meter readings, for example) as well as meter readings for individual customers or an individual
contract. You can transfer meter reading results into the Utilities Industry component (IS-U) manually, or using an interface to an external system (upload).
Integration
An IDoc interface (CA-EDI) is used to upload the meter reading results. The meter reading results are imported via direct input.
Features
You have the following options:
Upload
Large amounts of data are transferred from an external system into the system.
Fast entry
Large amounts of data from periodic meter readings are entered in the system. Fast entry is split into:
Fast Entry Without Immediate Correction
You have to correct and release implausible meter readings at a later time.
Fast Entry with Correction
If meter reasding results are implausible, you can access a correction screen.
Single entry
Meter reading results are entered from control meter readings, interim meter readings, or final meter readings (for move-out), for example.
As part of meter reading result entry, the system determines a consumption value dynamically from the difference between the current meter reading result and
the previous meter reading result. However, this value is not saved to the database. This consumption value can be taken into account during validation.
Note
If you have activated the business function Utilities, Quantity Determination (ISU_QD_1) and you use the quantity determination procedure Quantity
Determination During Meter Reading , the system determines a consumption value during meter reading result entry from the difference between the current
meter reading result and the previous meter reading result. The value is saved to the database. This consumption value can be taken into account during
validation and can also be used by subsequent processes such as billing.
Quantity Determination During Meter Reading
Every meter reading result is subject to validation. Validations can be dependent or independent. You define the validations in Customizing for SAP Utilities under
Device Management Meter Reading Validations . The validations take place during entry of meter reading results. Choose PUSHBUTTON when
entering meter reading results to display the validation results of a register.
Validations
If a meter reading result passes validation, it is given the status Plausible and is further processed in billing. If a meter reading result does not pass validation, it
is given the status Implausible and must be corrected. If the meter reading result has to be validated on-site, a correction order or a control meter reading order is
created with the up-to-date data.
You can also correct plausible meter reading results.
Note
You can add additional customer-specific validations to the predefined validations.
Customizing for SAP Utilities under Tools System Modification Customer-Specific Validations .
The following enhancements are available for entry of meter reading results:
EDMFOLUP (IS-U: Determine Follow-Up Actions for Entry of Meter Reading Results)
You can trigger a follow-up action once uploaded meter readings have undergone SAP entry checks and have been validated.
EDMMR001 (IS-U: Meter Reading Results – Subscreen Integration and Field Check)
You can now add customer-specific fields to the table of meter reading results.
For more information, see the enhancement documentation in the system.
1.3.6.2.1 Upload
Usage
You can upload meter reading results from external systems (such as MDE devices) using a BAPI or IDoc of type ISU_MR_UPLOAD02 (upload meter reading
results). The BAPI method is called MeterReadingDocument.Upload. Corresponding structure BAPIEABLU contains the following fields:
MATERIAL (material number)
Material/device category
SERIALNO (device serial number)
REGISTER (register number)
MRREASON (meter reading reason)
MRIDNUMBER (internal meter reading document number)
The meter reading number identifies a meter reading order. A meter reading order is created for each register to be read. The meter reading document
number must be downloaded and uploaded from the external system.
READINGRESULT (meter reading)
The data record is transferred to the system if either a meter reading result or note was provided.
METERREADINGNOTE(meter reading note)
The data record to be uploaded is transferred if either a meter reading or note was provided. The meter reading note can be assigned to a control function in
IS-U. The control function defines follow-up actions.
ACTUALCUSTOMERMRTYPE (meter reading type)
Describes how the meter reading result was recorded – by a meter reader or by the customer, for example.
METERREADER (meter reader number)
The meter reader number is used to identify the meter reader. It is used as a default value and can be stored in the schedule record of the meter reading.
You can use the Meter Reader Number field to indicate that the actual meter reader is different from the default meter reader.
MRDATEFORBILLING (meter reading date)
Billing occurs on this date, which is also the end of the billing period. The end of the billing period is determined.
MRTIMEFORBILLING (meter reading time)
ACTUALMRDATE (actual meter reading date)
ACTUALMRTIME (actual meter reading time)
MRDATEOFMAXIMUM (date of maximum reading)
MRTIMEOFMAXIMUM (Time of maximum reading)
SMORDER (service order number)
ACTIVE (active indicator)
There are two upload scenarios:
1. Meter reading orders were already created and downloaded in IS-U.
Meter readings are assigned to IS-U orders via the document number when they are uploaded. In this case you do not have to maintain the following fields:
Article Number
Device serial number
Register Number
Meter Reading Reason
2. There are no meter reading orders in IS-U/CCS
In this case you have to specify the serial number and the register number to identify the device for which readings are to be entered in IS-U/CCS.
If the serial number is not unique, you also have to provide the material number and device category. You also have to supply the meter reading reason, a
meter reading date and a meter reading.
For more information about IDocs see the following documentation:
For detailed information, see Using Documentation Toolss
Here you determine which documentation you can display for a certain IDoc category.
Features
The enhancements EDMMRRES are available for upload. You use this enhancement to manipulate meter readings after results have been uploaded and before
the readings are validated.
1.3.6.1.2 Fast Entry With/Without Correction
Use
You can use this function to enter a large number of meter reading results manually. Fast entry is normally used for periodic meter readings.
Prerequisites
Before you can use this function you must create a meter reading order. Once the meter reading order has been created, meter reading documents are printed
and distributed to meter readers. The data to be entered, such as meter readings, notes, or the meter reading date, is usually copied from the meter reading
documents.
Features
There are two types of fast entry:
Fast entry without correction
When meter reading results are entered, the meter reading is validated (if there is zero consumption, for example). If the meter reading result fails the validation, it
is reset and must be processed in a further step (by the agent, for example). It is not possible to release the meter reading during fast entry without correction.
Fast entry with correction
If the meter reading fails the validation, it can be released during fast entry with correction.
Activities
Initial Screen
All meter readings that are allocated to a single meter reading unit and that have the same target meter reading date can be entered together. Data to be entered,
such as the meter reading unit, target meter reading date, and meter reading reason can be copied from the meter reading documents. If no target meter reading
date is entered, a list appears containing target meter reading dates for which meter reading orders exist.
Entry Screen
An empty table appears on the entry screen. There is a unique entry number for each meter reading. This number is used to identify and display the
corresponding meter reading order for the readings.
You can specify the following meter reading data for fast entry:
Entry number (only for fast entry)
Meter reading
Meter reading date
Note from meter reader
Actual meter reading type
Meter reader
Time of day of meter reading
Actual meter reading date
Actual time of day of meter reading
Date of maximum meter reading
Time of day of maximum meter reading
Relevance to billing/extrapolation
If the meter reading fails the validation, you can choose from the following during fast entry with correction:
Correct errors
You branch to the correction screen. The correction screen contains detailed information such as the expected reading, actual consumption, and expected
consumption. If the meter reading is released, the remaining validations are carried out.
Release without correction
The meter reading becomes plausible. No further validations are carried out.

Use
This function enables you to enter meter readings for a single customer, contract, installation or device. For example, you may wish to enter a control meter reading
for an installation or an interim meter reading with subsequent billing.
Features
You do not have to create a meter reading order before carrying out single entry. However, if a meter reading order already exists, that order is taken into account. If
no meter reading order exists, an order is created using the criteria you have entered. In the case of a meter reading reason that triggers billing, a billing order is
created.
The meter readings entered are validated. If a meter reading fails the validation, it can be immediately released or reset for later processing.
Activities
You can specify the following meter reading data for single entry:
Meter reading
Meter reading date
Meter reader
If a meter reading result fails the validation, you can process it using the following functions:
Correct errors
You branch to the correction screen. The correction screen contains detailed information such as the expected reading, actual consumption, and expected
consumption. If the meter reading is released, the remaining validations are carried out.
Release w/o correction
The meter reading becomes plausible. No further validations are carried out.
Estimate
Meter reading results can be selected for estimation.
1.3.6.1.4 Assessing
Use
IN SAP IS-U, assessing refers to the automatic handling of meter overflows due to over-estimated previous meter readings.
These assessing cases do not deal with actual meter overflows but with over-estimated previous meter readings. When an assessing case arises, a result is
released during meter reading entry that triggers workflow template ISU_ASSESS1. This workflow reverses the billing and reestimates the meter reading based on
the actual meter reading results.The typical assessing case is illustrated below:
The system determines a meter overflow as the (estimated) meter reading result from 3.1. is higher that the (actual) meter reading result from 4.1.
Since the meter reading result from 3.1. is an estimation, and the last actual result from 1.1. is lower than the current actual result, this is an assessing case.
This means that the system cancels all estimated previous meter reading results that are higher than the current actual result, and reestimates them based on the
current actual meter reading result.
In the above example, the system cancels the meter readings from 2.1. and 3.1. and reestimates them based on the actual meter reading result from 4.1.
Integration
Up to SAP IS-U 4.63, assessing can only be used for billing-relevant meter reading reasons. As of SAP IS-U 4.64, assessing can also be used for control meter
reading.To do this, you must set the Ass. Control MR indicator ( Assessing also for MR reasons not triggered by billing (09,10) ) in Customizing activity Define
Technical Control Parameters for Meter Reading Data Processing (table TE410s).
Prerequisites
The assessing workfow can only adjust an overflow within a contract. If a change of contract has taken place (due to a move-in/out, for example), the assessing
workflow is not triggered and an error message is displayed.
The following example is not an assessing case as a contract changes has taken place due to a move-in/out.
Features
The algorithm for determining an assessing case is as follows:
Determination of consumption V1, which occurs between the last actual meter reading result and the current meter reading result. The meter reading results that
lie between are ignored.
Determination of consumption V2, which occurs between the last actual meter reading result and the last estimated meter reading result. The meter reading results
that lie between are ignored.
If V2 > V1, an assessing case arises.
The following example is an assessing case:
V1 = 40 (0 – 40)
V2 = 100 (0 – 100)
V2 > V1 => Assessing required
Function module ISU_EVENT_ASSESSING checks whether assessing is required. Once the workflow has been triggered, the corresponding billing documents
are reversed and the relevant meter reading results are reestimated in function module ISU_ACTION_ASSESSING.
You can use enhancement EDMASSES to implement customer-specific checks for the determination of assessing cases.
Example
Example 1 - Assessing: Estimated MR Result Lead to Overflow
V2 (55) > V1 (3)
=> Assessing required

The meter reading from 3.1. is higher than that from 2.1.(no overflow), however, the estimated meter reading result from 2.1. was over-estimated and resulted in a
meter overflow.
Example 2 – No Assessing
V2 (100) < V1 (9990)
=> No assessing required

A reestimation would result in an overflow (high consumption).
Example 3 – No Assessing: Actual Meter Overflow (3-figure meter)
V2 (70) < V1 (140)
=> No assessing required

Purpose
You can subsequently correct or change existing meter reading results in the system.
Process Flow
You can change the meter reading results by means of the upload process.
See Upload .
You can use the following transactions to correct meter reading results:
Correct Plausible Meter Reading Results
Correct Implausible Meter Reading Results
Result
The meter reading results have been corrected or changed in the system.
1.3.6.2.1 Upload
Usage
You use this function to change or correct meter reading results by upload.
Integration
BAPI BAPI_MTRREADDOC_UPLOAD and the allocated IDoc of category ISU_MR_UPLOAD02 enable you to change meter reading results.
Read the documentation for BAPI BAPI_MTRREADDOC_UPLOAD to find out how to fill the IDoc segments to change meter reading results.
Prerequisites
You define in Customizing which meter reading results are to be changed during the upload process:
Customizing for SAP Utilities Device Management Meter Reading Meter Reading Result Change Define Change Process for Meter Reading
Data.
Features
You can use a PM service notification to trigger a request for a new meter reading for plausible and implausible meter reading results. Using the upload process
with basic IDoc category ISU_MR_UPLOAD02, you can overwrite existing meter reading results with new results.
IDoc category ISU_MR_UPLOAD02 consists of the following segments:
E1BPEABLUCHANGE (This segment is filled for changing the meter reading results)
The system identifies the meter reading result to be changed either by means of the internal ID of the meter reading order or using the key fields and
auxiliary date (MRDATEFORIDENTIF). The upload process takes place for this meter reading result.
E1BPEABLUUPDATE (This segment is filled for updating, changing, and entering meter reading results)
If the system cannot identify the meter reading result to be changed, it creates a new meter reading order during the upload process. The upload process
takes place either for the meter reading result or the meter reading order.
The following scenarios exist for changing meter reading results by upload:
1. A corresponding meter reading document with a meter reading result exists for the uploaded result. The uploaded records contain the internal ID of the meter
reading document. The Material , Serial Number , Register , Meter Reading Reason , and Auxiliary Date fields are ignored.
2. A corresponding meter reading document with a meter reading result exists for the uploaded result. The internal ID of the meter reading document is not
known and the uploaded records do not contain the ID.
In this case, the key fields of one of the following alternatives must be maintained to identify the meter reading document to be changed:
Serial Number, Register, Meter Reading Date, Auxilliary Date
If the serial number is not unique in the system, a material must also be entered.
Serial Number, Register Code, Meter Reading Date, Auxilliary Date
If the serial number is not unique in the system, a material number must also be entered.
Point of Delivery, Register Code, Meter Reading Date, Auxilliary Date
The auxiliary date for background processing (MRDATEFORIDENTIF) must be specified in order to identify the meter reading result to be changed.
This date corresponds with the meter reading date of the meter reading result to be changed before processing.
If the system cannot identify the meter reading result to be changed during the upload process, the meter reading data of the uploaded record is not imported into
the system.
The following scenarios exist for updating meter reading results by upload:
1. A corresponding meter reading document with a meter reading result or a meter reading order exists for the uploaded result. The uploaded records contain
the internal ID of the meter reading document. The Material , Serial Number , Register , Meter Reading Reason , and Auxiliary Date fields are
ignored. The uploaded record changes the existing meter reading result or creates a new result in the system.
2. A corresponding meter reading document with a meter reading result exists for the uploaded result. The internal ID of the meter reading document is not
known and the uploaded records do not contain the ID. In this case, the key fields of one of the following alternatives must be maintained to identify the meter
reading document to be changed:
Serial Number, Register, Meter Reading Date, Auxilliary Date
Serial Number, Register Code, Meter Reading Date, Auxilliary Date
Point of Delivery, Register Code, Meter Reading Date, Auxiliary Date
The auxiliary date for background processing (MRDATEFORIDENTIF) must be specified in order to identify the meter reading result to be changed.
This date corresponds with the meter reading date of the meter reading result to be changed before processing.
3. No corresponding meter reading order and no meter reading result exists for the uploaded meter reading result.
In this case, the key fields for one of the following alternatives must be maintained:
Serial Number, Register, Meter Reading Date
Serial Number, Register, Meter Reading Date
Point of Delivery, Register, Meter Reading Date
You can also change the meter reading results using BOR method UPLOAD or BOR object MTRREADDOC. the interface of the method contains the following
parameters:
MeterReadResChange (for changing meter reading results)
MeterReadResUpdate (for updating meter reading results)
Activities
Change Meter Reading Results Using IDoc Category ISU_MR_UPLOAD02

1. Change the meter reading results using IDoc category ISU_MR_UPLOAD02 and fill in segment E1BPEABLUCHANGE with the upload data for the meter
reading results to be changed.
2. Import the IDoc into the system and check the log for the upload process (IUPP).
Update Meter Reading Results Using IDoc Category ISU_MR_UPLOAD02

1. Update the meter reading results using IDoc category ISU_MR_UPLOAD02 and fill in segment E1BPEABLUUPDATE with the upload data for the meter
reading results to be updated.
2. Import the IDoc into the system and check the log for the upload process (IUPP).
Change Meter Reading Results Using BOR Method ‘Upload’ of BOR object ‘MTRREADDOC’
1. Fill the MeterReadResChange parameter with uploaded data for the meter reading results to be changed.
2. Execute the method.
Update Meter Reading Results Using BOR Method ‘Upload’ of BOR object ‘MTRREADDOC’
1. Fill the MeterReadResUpdate parameter with uploaded data for the meter reading results to be updated.
2. Execute the method.
1.3.6.2.2 Correction of Plausible Meter Reading Results
Use
This function allows you to correct plausible meter reading results. You can use this function if, for example, you originally estimated the customer’s meter reading
and the customer provides you with the actual meter reading later.
Prerequisites
The meter reading must not have been billed already. A meter reading that has been billed cannot be changed until the billing has been reversed. This function
can only used to correct plausible meter reading results.
Features
After you change meter reading result, it is validated again.
Activities
Initial Screen
All meter reading results are displayed by device and meter reading date. You use an indicator to select the meter readings to be processed.
Entry Screen
If you have selected several entries, they are processed sequentially. You choose Save or Forward to branch to the next entry. If the entry was saved, it is
removed from the processing sequence.
You can specify the following meter reading data during correction of plausible meter reading results:
Meter reading
Meter reading date
Meter reader
Correction
For further information, refer to the function Fast Entry with/without Correction .
1.3.6.2.3 Correction of Implausible Meter Reading Results
Use
Implausible meter reading results are reset when meter reading results are imported via upload or when large amounts of data are entered as part of a fast entry
without correction. These meter readings can be processed further via the function for correction of meter reading results.
Integration
You can forward implausible meter reading results to an agent's inbox. Clerk determination is carried based on the organizational structure.
Establish customizing settings as required under Utilities Industry Basic Functions Clerk Determination .
Prerequisites
A meter reading is given the status Implausible if you have set validations and chosen the error class Warning .
Features
Meter readings that belong to the same premise can be validated together on one screen. During the validation, the plausible meter readings are also displayed.
If only a single-rate meter has been allocated to a premise, you branch directly to the correction screen.
You can create a list of implausible meter reading results for several portions or meter reading units. To do this, choose Goto Implausible MR results and
enter the portions or meter reading units for which you want to create the list.
Activities
Initial Screen
Once you have entered a selection criterion, the implausible meter readings are displayed according to premise. You select meter readings to be processed from
this list.
Overview Screen
Meter readings are displayed along with the actual consumption and demand and the expected consumption and demand. Implausible meter readings are
highlighted in color. Only these highlighted meter readings can be processed.
The following functions are available:
Release w/o correction
Correct errors
Estimate
Correction Screen
You branch to the correction screen if only a single-rate meter is allocated to the premise or if you choose the correction function. Data is displayed such as meter
reading data, forecast data, and master data that support validation.
The following functions are available:
Release
Any outstanding validations are carried out.
Defer
Meter readings are put aside for later processing.
Estimate
Print correction order
Validation information
Control meter reading order
If the control meter reading is plausible, the implausible meter reading result is replaced by an estimated result. This estimation is based on the control meter
reading.
1.3.6.3 Validations
Usage
Validations are carried out during the entry and correction of meter reading results.
There are dependent and independent validations:
Independent validations check the meter reading result from one register only.
Dependent validations , check related registers together.
1.3.6.3.1 Independent Validation
During independent validation, the meter reading result of exactly one register is checked. Validations can be fixed or variable. Fixed independent validations are
performed automatically by the system. Variable independent validations are performed according to the settings in Customizing for SAP Utilities under Device
Management Meter Reading Validiatons Independent Validations .
Fixed Validations
Previous Meter Reading Implausible
The system perfoms validation based on the previous meter reading results. The system first checks whether the result from the previous meter reading is
plausible. If it is not, the current meter reading result cannot be given the status "Plausible". The result of the previous meter reading must first be corrected
so it can be used as a basis for the other checks.
Fixed value deviation check
During reconnection of an inactive or disconnected installation, and during device installation after certification, for example, the system checks whether any
consumption took place and whether the consumption is below the maximum permissible deviation. You define this in Customizing for SAP Utilities under
Device Management Meter Reading Validations Independent Validations Parameters for FVD Validation for Devices Not Allocated to
Installations .
Check resetting register
If the register is a resetting register, the system checks whether the number of times it has been reset matches the number of meter readings.
If you have activated the Quantity Determination business function (ISU_QD_1) and you use Quantity Determination Procedure 03 - Quantity Determination
During Meter Reading , you can activate and use the following check:
Check for Final Quantity
This check precedes the other validations and checks whether the quantity is a final quantity.
If it is a final quantity, the other independent validations are based on this quantity.
If it is not a final quantity, the further validations do not take place and the meter reading result is set to Implausible .
For this check to be performed automatically, you have to select the Validation for Final Quantity check box in Customizing for SAP Utilities under
Device Management Meter Reading Basic Settings Define Control Parameters for Meter Reading Data Processing .
If you do not select this check box, the validation for the final quantity does not take place and the other validations are performed according to the
Customizing settings, regardless of whether the quantity is provisional or final.
Variable Validations
Zero consumption check
The system checks whether the consumption is zero and whether it is within the grace period for zero consumption.
Number of permitted meter readings by customer, estimations, or meter readings by customer and estimations exceeded
The system checks whether the number of consecutive meter readings defined in meter reading control has been exceeded.
Absolute, relative, and floating tolerance limits
The system uses the expected consumption from the comparison period to check whether the current consumption is within the tolerance limits. You enter
the base period category of the comparison period in the installation. You define the number of comparison periods in Customizing for SAP Utilities under
Device Management Meter Reading Validations Independent Validations Define Validation Parameters for Validation Classes .
Note
If you have activated the Utilities, Quantity Determination business function (ISU_QD_1) and you use the quantity determination procedure Quantity
Determination During Meter Reading in combination with the gas division, the upper and lower limits for the meter readings are not displayed with the
validation information. This applies in the following transactions:
Monitoring of Meter Reading Results (transaction EL31)
Single Entry (Transaction EL28)
Correct Plausible Meter Reading Results (transaction EL29)
Correct Implausible Meter Reading Results (transaction EL27)
Usage hours against previous period or fixed value

Usage hours are determined by dividing the consumption from the period by the installed demand. The value is stored in an operand which you can enter in
Customizing for SAP Utilities under Device Management Meter Reading Validations Independent Validations Define Validation Parameters for
Validation Classes .
The current usage hours are checked against the usage hours from the previous period. There is also a fixed value that you may not exceed, which is
derived from the number of days since the previous meter reading multiplied by 24 hours.
Maximum/minimum demand
The system checks whether the demand exceeds or falls below a fixed value. You enter this value in Customizing for SAP Utilities under Device
Management Meter Reading Validations Independent Validations Define Validation Parameters for Validation Classes .
Meter overflow
The system checks whether the current meter reading is lower than the previous meter reading.
1.3.6.3.2 Dependent validations

During dependent validations, registers in a relationship are validated together. You can use the following types of dependent validations:
Control meter validation (fixed value against relative value)
The system checks whether the total consumption of the settlement registers matches the consumption of the control register.
Serial switching validation
The system checks whether the total consumption of secondary installations exceeds the consumption of the primary register.
Cosine phi validation
The cosine phi is calculated from reactive/active registers.
In validation 04, the system checks whether values fall below a lower limit defined in Customizing.
In validation 05 (check against cosine phi of previous period), the system compares the cosine phi of the current and previous period(s).
Consumption ratio validations (fixed value and previous period)
The system creates a ratio for the consumption of registers in a register relationship. The system then checks whether the ratio matches either the fixed value or
the consumption ratio of the previous period.
1.3.6.4 Estimation
Purpose
This component allows you to estimate meter reading results automatically in the case of missing meter readings or implausible consumption.
This component is optional.
1.3.7 Reversal
Reversing meter reading deletes all objects generated during creation of meter reading orders and entry of meter reading results:
Meter reading orders
Meter reading results (optional)
Billing orders
Reversal may be necessary in the following cases:
You determine the scheduling data was incorrect after you created periodic meter reading orders for a meter reading unit.
You enter an incorrect device when creating a control meter reading order.
Features
On the initial screen you can choose whether the meter reading results:
Are to be deleted
Meter reading orders, meter reading results, and billing orders are deleted. New meter reading orders are created when meter reading order creation is
carried out again.
Are not to be deleted
Only meter reading orders and billing orders are deleted, not meter reading results. When meter reading order creation is carried out again, ew meter
reading orders are only created for devices that were not read. No new meter reading orders are created for devices that have already been read, as the
corresponding meter reading results were not deleted.
Meter reading orders and results that have already been billed can only be reversed if the corresponding billing documents have been reversed first. You can find
the reversal transactions for Billing in the Utilities Industry menu under Billing Billing Execution Reversal .
Meter reading results that were entered during installation, replacement, or removal of devices can only be reversed in the respective reversal transactions for
installation, replacement, or removal. They can then be deleted. You can find the reversal transactions for installation/replacement/removal in the Utilities Industry
menu under Device Management Installation .
1.3.8 Monitoring
Purpose
This component offers you a variety of information to enable you to monitor meter reading entry and status. For example, you can track the number of meter reading
results entered, implausible meter reading results, or meter reading results to be billed. You can display meter reading results by business partner, meter
reading units, or periods. You have the following options:
Manual Monitoring
Automatic monitoring
Meter reading results from IDoc
You enter a creation date or an IDoc number to obtain a list of IDocs for your search. If you select and IDoc number, you obtain a list of meter reading data stored
in the IDoc. If you select an entry with status Plausible , the meter reading result you selected is displayed. If you select an entry with status Implausible , you
branch to the screen for correction of implausible results.
If you select an entry with status Error , you branch to the screen for individual entry of results
This component is optional. However, it can be used to quickly obtain information about current meter reading status.
1.3.8.1 Monitoring of Meter Reading Results
To monitor meter reading results, you can use the following transactions in the Utilities Industry menu under Device Management Meter Reading
Monitoring .
Features
Monitoring of Meter Reading Results

Transaction EL31
You can use this transaction to monitor meter reading results based on different selection criteria. You have different monitoring options depending on the selection
criteria you choose. The following table provides an overview of these options. The selection criteria are listed in the first column. The objects that you can monitor
using these selection criteria are marked with x in each row.
Lists
Selection Criterion: Schedule Record Meter Reading Order Meter Reading Result Billing Order
Portion x x (*) x (*) x (*)
Meter Reading Unit x x (*) x (*) x (*)
Business Partner - x x x
Contract - x x x
Installation - x x x
Device - x x -
Premise - x x x
(*) At first the system displays a summarized list grouped by date (meter reading date, billing date); from here you can navigate to more detailed lists.
Portion or Meter Reading Unit

If you start by entering portions or meter reading units, you can display schedule records, billing orders, and meter reading orders.
If the business function Utilities, Quantity Determination (ISU_QD_1) is active, you can also display meter reading results.
Contract, Installation, Business Partner, or Premise

If you start by entering contracts, installations, or business partners, you can display billing orders, meter reading orders, or meter reading results.
Device
If you start by entering devices, you can display meter reading orders or meter reading results.
In almost all of the lists for the monitoring function, you can navigate to the detailed display of an object by choosing Edit Select or by double clicking on
the field in question.
Meter Reading Orders
If there are meter reading orders for the devices, you can use the pushbutton to navigate to the AMI monitor for one or more orders.
Meter Reading Results
The following functions are available in the lists of meter reading results:
On-demand meter reading
For the right kind of devices, you can use the pushbutton to request on-demand meter readings.
Note
A prerequisite is that you have activated the business function Advanced Metering Infrastructure (ISU_AMI_1).
AMI monitoring
If there are meter readings for the devices, you can use the pushbutton to navigate to the AMI monitor for one or more meter readings.
Note
A prerequisite is that you have activated the business function Advanced Metering Infrastructure 2 (ISU_AMI_2).
Quantity determination
For meter readings with a quantity determination trigger, you can use the pushbutton to carry out quantity determination.
Note
A prerequisite is that you have activated the business function Utilities, Quantity Determination (ISU_QD_1).
Automatic Monitoring of Meter Reading Data

Transaction EL32
You can use this transaction to monitor meter reading data and trigger automatic follow-on processing for selected meter reading orders. For the follow-on
processing actions, this transaction interprets the settings in Customizing for the automatic monitoring of meter reading data:
Customizing for SAP Utilities Device Management Meter Reading Basic Settings Automatic Monitoring of Meter Reading Data .
For more information about the automatic follow-on processing of meter reading orders, see the documentation for the Customizing activity.
Postprocessing of IDocs for Uploading Meter Reading Results

Transaction ELDM
You can use this transaction to display the successfully and unsuccessfully posted meter reading documents after uploading discrete meter reading data (IDocs
from category ISU_MR_UPLOAD).
Device Overview
Transaction EL43
You can use this transaction to get an overview of the devices of a meter reading unit.
1.3.8.2 Device Overview
Use
This function provides you with an overview of all installations from a meter reading unit as well as of all devices in an installation and their register relationships .
1.3.9 Quantity Determination
The following sections provide you with an overview of quantity determination. The term quantity determination refers to the process of converting a meter reading
difference into a billing-relevant quantity. For quantity determination you can choose from different quantity determination procedures.
Features
Quantity Determination Procedures

You choose a quantity determination procedure based on the role of your company in the market, the market rules that apply to you, and the processes within your
company. The quantity determination procedure determines when quantity determination takes place and how the data is stored.
Possible quantity determination procedures are:
Quantity Determination During Billing (classic procedure)
The following figure illustrates the two quantity determination procedures:
Overview of Quantity Determination Procedures
Quantity Determination During Billing

This quantity determination procedure, shown in the upper section of the figure above, is the classical procedure during which a billable quantity is determined
from a meter reading difference during billing.

In this quantity determination procedure, shown in the lower section of the figure above, a quantity is determined from a meter reading difference when the meter
reading result is entered. This quantity is saved to the database. The quantity can be used for billing at a later point in time. As opposed to quantity determination
during billing, quantity determination during meter reading allows quantities or consumption to be determined separate from billing. This is a legal requirement in
deregulated energy markets.
Note
To be able to use this procedure, you must activate the Utilities, Quantity Determination business function (ISU_QD_1).
For more information, see

1.3.9.1 Quantity Determination During Meter Reading
You use this quantity determination procedure if the market rules that apply to you, or the processes within your company, require quantity determination as part of
meter reading data processing.
As soon as a meter reading is entered or changed, the system uses the quantity determination procedure to calculate the respective consumption quantity, saves
it in the database, and updates the quantity determination information. The system also determines the conversion history and saves this along with the
consumption.
Prerequisites
You have activated the business function Utilities, Quantity Determination (ISU_QD_1).
There are a number of restrictions that apply when using this quantity determination procedure. Make sure you take these into account before taking further steps
in the changeover of the quantity determination procedure.
Important Notes
Also see the Implementation Considerations and Additional Information sections at the end of this description.
Process
As a substep of Process Measurement Data for Discrete Meter Readings , quantity determination belongs to Measurement Data Management . Measurement
Data Management includes the determination and management of discrete measurement data as well as interval data. The data can originate from different types
of meter.
Discrete data from a conventional meter or an advanced meter
Interval data from an advanced meter or another interval meter
Quantity determination is only relevant for discrete measurement data.
.
Process in Detail
When using the quantity determination process Quantity Determination During Meter Reading , quantity determination takes place along with the validation of the
entered measurement data during measurement data processing. If a final quantity determination is not possibile at this time, the system automatically generates
quantity determination triggers to execute quantity determination again at a later time. You can schedule processing of the quantity determination triggers as a
separate activity (mass activity) or as part of the monitoring of meter reading results (single processing). The estimation of discrete values takes place based on
quantites. If measurement data is corrected a recalculation of the quantities also takes place.
Follow-On Processes
When you use this quantity determination procedure, follow-on processes such as SAP Utilities Billing use the quantities determined in meter reading as a basis.
Billing
In SAP Utilities Billing, both the proration of meter readings and billing simulation are based on quantities. When displaying a billing document for a billed period,
the system automatically recognizes the quantity determination procedure being used from the device information.
You can generally execute utilities billing using the quantity determination procedure Quantity Determination During Meter Reading without making any additional
adjustments. Analyze the company-specific starting point and read the notes under
Check Company-Specific Starting Point
Integration
Visualization of Quantity Determination Information

Quantity determination information is displayed in the following areas:
Meter Reading
The following information is displayed on the user interfaces for meter reading data processing:
Quantity Determination Information
Shows whether the displayed consumption value is a final consumption or a provisional consumption.
Quantity Determination Status
Shows the status of the quantity determination.
1 - Quantity Determination Not Necessary
2 - Quantity Determination Performed Successfully
3 - Quantity Determination Trigger Generated
Device Management
You can display the quantity determination procedure using the transactions Change Rate Data (transaction EG70) and Display Rate Data (transaction EG71).
Customer Service Processes

In the customer service processes (for example, move-in and move-out), the following information is displayed on the user interfaces for meter reading data
processing:
Consumption
Quantity Determination Information
Quantity Determination Status
Make sure you take the following information into account before taking further steps in the changeover of the quantity determination procedure.
Customizing
Activating the business function does not also activate the functions described here. To use these functions, you must specify the quantity determination
procedure Quantity Determination During Meter Reading in Customizing: SAP Utilities Basic Settings/Enterprise Structure Define Quantity
Determination Procedure
Define Quantity Determination Procedure
Company-Specific Starting Point

If you want to change over existing processes to the new procedure, it may be necessary to perform additional activities. Check this for your own company's
requirements for the data in your system.
Changeover Date of the Quantity Determination Procedure

You can only change over the quantity determination procedure if the registers only contain meter reading results whose meter reading date is after the changeover
date. We recommend choosing dates for the changeover that are in the future and for which no changeover has yet taken place.
Notes About the Time of the Changeover
More Information
To familiarize yourself with the concepts of this quantity determination procedure, read the following information:
Change Meter Reading Results
Quantity Determination Trigger Concept
Check for Final Determined Consumption in Technical Transactions
Estimation Procedure
For information about the activities for changing over to this quantity determination procedure, see section One-Off Activities for Changeover :
Define Quantity Determination Procedure
Setting the Quantity Determination Procedure for Existing Installations
For information about the activities for quantity determination in day-to-day business, see Activities in Production Operation.
1.3.9.1.1 Important Notes
There are a number of constraints to take into account when using the quantity determination procedure Quantity Determination During Meter Reading . Make sure
you take these into account before taking further steps in the changeover of the quantity determination procedure.
Constraints
Register Relationships
Register relationships for the following register relationship types in the gas division cannot be used in conjunction with the quantity determination procedure
Quantity Determination During Meter Reading :
05 – Volume correction factor relationship
06 – Volume correction factor calculation
Caution
Check whether such register relationships exist in your system. For divisions in which installations have these register relationships, you cannot change over
to the quantity determination procedure Quantity Determination During Meter Reading without consulting SAP. The conversion report does not check this
itself.
If you do not take this into account, data inconsistencies can occur.
Volume Correction Factor Procedures

Volume correction factor procedures with the following special procedures in the gas division cannot be used in conjunction with the quantity determination
procedure Quantity Determination During Meter Reading :
Register relationship ZZ
Register relationship ZE
Caution
Check whether you use such special procedures in your system. For divisions in which installations have these special procedures, you cannot change over
to the quantity determination procedure Quantity Determination During Meter Reading without consulting SAP. The conversion report does not check this
itself.
If you do not take this into account, data inconsistencies can occur.
Dynamic Period Control

Dynamic period control cannot be used in conjunction with the quantity determination procedure Quantity Determination During Meter Reading . When attempting
to change over installations with dynamic period control to the quantity determination procedure Quantity Determination During Meter Reading , the consistency
checks identify these installations. If you still want to execute quantity determination during meter reading, you cannot use dynamic period control.
Dynamic Period Control
Assessing
Assessing cannot be used in conjunction with the quantity determination procedure Quantity Determination During Meter Reading . If you still want to use the
quantity determination procedure Quantity Determination During Meter Reading , be aware that the Assessed event cannot be triggered during meter reading.
Assessing
Demand Registers
You cannot use the quantity determination procedure Quantity Determination During Meter Reading in conjunction with demand registers. For demand registers,
quantity determination generally takes place during billing.
When attempting to change over installations that contain demand registers to the quantity determination procedure Quantity Determination During Meter
Reading , the quantity determination procedure Quantity Determination During Billing is set automatically for demand registers.
Japanese Billing Periods

Japanese billing periods cannot be used in conjunction with the quantity determination procedure Quantity Determination During Meter Reading . If you are
using Japanese billing periods , you cannot use the quantity determination procedure Quantity Determination During Meter Reading .
1.3.9.1.2 Notes About the Time of the Changeover
Before you activate the business function Utilities, Quantity Determination (ISU_QD_1) and change over the quantity determination procedure, you should
consider when you want the changeover to take place. The changeover of the quantity determination procedure has an effect on many SAP Utilities business
processes and therefore has far-reaching consequences.
During the changeover of the quantity determination procedure, a metered data entry is necessary on the changeover date for all installations belonging to the
division in question. Under certain circumstances, this could result in logistical problems and large volumes of data. Take this into account when choosing the time
of the changeover and the changeover methods described below.
The market rules that apply to you also have an influence on the time of the changeover. Depending on how much room to maneuver you have with regard to
applying the market rules, and depending on the initial situation in your system, choose one of the following changeover methods:
Changeover on key date
Rolling changeover
As a general rule, you can only change the quantity determination procedure if the registers of the installations concerned only contain meter reading results whose
meter reading date is before the changeover date. Therefore, take the following recommendation into account.
Recommendation
We recommend choosing dates for the changeover that are in the future and for which no changeover has yet taken place.
Changeover on Key Date

For this method, you change over all installations that are assigned to the selected division to the quantity determination procedure on a specific key date.
If the market rules that apply to you stipulate that you have to determine the consumption for every meter reading as of a certain key date, and you want to change
over to this quantity determination procedure as quickly as possible in order to comply with these rules, you can use the Changeover on Key Date model.
To change over the installations in your system to the quantity determination procedure that is defined for a division in Customizing, and that is valid as of a defined
key date, you have to use a report to convert the installations at register level. This report has to interpret the Customizing settings and apply them to the
installations.
You can use the Define Quantity Determination Procedure report (REQD_SET_QDPROC_TO_REGISTER) for this purpose. This report changes the quantity
determination procedure on the key date defined in Customizing.
Alternatively, you can use the report as a template to create a company-specific changeover report in your project.
Rolling Changeover
With this method, you change over the installations in your system that are assigned to a selected division to the quantity determination procedure in different
stages. If you choose the changeover date so that the installations are changed over after billing, you avoid having to enter additional measurement data on the
changeover date and you achieve a clear differentiation between the quantity determination procedures.
To change over the installations in your system to the quantity determination procedure defined in Customizing, you have to use a report to convert the installations
at register level. This report has to interpret the Customizing settings and apply them to the installations. The report also has to move the from-date of the quantity
determination procedure so that the changeover date is different from the key date defined in Customizing.
You can use the Define Quantity Determination Procedure report (REQD_SET_QDPROC_TO_REGISTER) for this purpose. You can also implement the method
Change From-Date of Quantity Determination Procedure (CHANGE_VALID_FROM_EADZ_QD) of BAdI Quantity Determination Procedure (ISU_QD_PROC).
Alternatively, you can use the report as a template to create a company-specific changeover report in your project.
For more information about the changeover of quantity determination procedures and about the Define Quantity Determination Procedure report, see Define
Quantity Determination Procedure for Existing Installations.
1.3.9.1.3 Concepts
Read the information in the following sections to familiarize yourself with the functions and concepts of the quantity determination procedure Quantity Determination
During Meter Reading . Alternatively, choose the following links to access information about the concepts behind this quantity determination procedure.
Change Meter Reading Results
Check for Final Determined Consumption in Technical Transactions
Estimation Procedure
1.3.9.1.3.1 Change Meter Reading Results
During the entry of meter reading results, the system uses the difference from the previous meter reading result to calculate the consumption. If you change or
delete meter reading results, the system automatically recalculates the consumption quantity.
The system analyzes the environment of the changed or deleted meter reading result and recalculates all quantities that are based on the changed or deleted
meter reading result. The following examples relate to cumulative consumption registers.
The abbreviations in the examples have the following meaning:
MR = Meter reading result
Q = Quantity
The orange arrows followed by a meter reading result (MR) or quantity (Q) illustrate the change described in the text.
Example 1 - Value Changed
The change to the value for meter reading result MR2 means that quantities Q1 and Q2 are recalculated.
Example 2 - New Meter Reading Result Between Exising Meter Reading Results
The entry of the new meter reading result MR3 means that the already determined quantity Q is split into two parts Q1 and Q2 during recalculation.
Example 3 - Meter Reading Result Between Other Meter Reading Results Deleted
The deletion of meter reading result MR2, which is between meter reading results MR1 and MR3, means that the already determined quantities Q1 and Q2 are
combined into a single quantity Q during recalculation.
Example 4 - Status of Meter Reading Result Changed from “Active” to “Inactive”
The change to the status of the meter reading result from Active to Inactive is handled the same way as the deletion of a meter reading result, which is
described in the previous example. The already determined quantities Q1 and Q2 are combined into a single quantity Q during recalculation.
1.3.9.1.3.2 Quantity Determination Trigger Concept
If a final quantity determination is not possible for certain meter reading results, the system automatically creates quantity determination triggers.
A quantity determination trigger identifies a meter reading result without a final quantity determination and shows that quantity determination has to be calculated
again for a data record in order to get the final results. The availability of a final quantity is a prerequisite for subsequent processes such as billing. Billing can only
take place based on a final quantity.
A final quantity is defined as a quantity that was determined at a time when all the parameters (for example, current calorific value) or the previous meter reading
were known. The final quantity is saved to the database.
Reasons for Generating Quantity Determination Triggers
The system generates quantity determination triggers for the following reasons:
01 - No Current Gas Data
Quantity determination triggers with reason 01 are usually generated as a result of missing time-specific gas values. These can be billing calorific
values, for example, or other values used to determine the quantity.
For more information about determining gas factors, see Customizing for Contract Billing under Special Functions Gas Billing .
02 - Previous Meter Reading Document Not Unique
Quantity determination triggers with reason 02 are generated in the following cases:
A meter reading order still exists between the previous meter reading and the new meter reading.
The quantity determination procedure was changed over between the previous meter reading and the current meter reading.
99 - Other
Due to the high flexibility of device management and meter reading, certain situations may arise when it is not be possible to uniquely and consistently
determine the quantity. In such cases, the system generates quantity determination triggers with reason 99 - Other .
These reasons are displayed on the relevant interfaces along with additional information about quantity determination.
Activities
Depending on the reason for the generation of the quantity determination trigger, certain follow-up actions are necessary before the trigger can be processed.
For more information, see Process Quantity Determination Trigger under Activities in Production Operation.
1.3.9.1.3.3 Check for Final Determined Consumption in Technical

Transactions
The successfully executed quantity determination for a register results in the final determined consumption . This result depends on a number of influencing
factors. The final determined consumption is consistent as long as these factors are not changed after the quantity has been determined successfully. For this
reason, the system no longer allows changes in the following technical transactions if the change relates to the period in which the consumption was determined:
Transaction EG70/EC30: Change Rate Data
The following fields cannot be changed at register level:
Rate Type
Gas Procedure
Fixed Temperature
Volume Correction Factor
Consumption Fixed Value to be Weighted Linearly
Validity Period
Consumption Percentage for Weighting
Period Consumption
Number of Days for Which Period Consumption is Valid
Register Not Relevant for Billing
Transaction EG72: Device Allocation
If the quantity determination for a register has been successfully carried out in a certain period, the system no longer allows changes to the device allocation
of the register within that period. This also applies for the billing factor and measured pressure.
Transaction EG60: Change Logical Register
If the quantity determination for a register has been successfully carried out in a certain period, the system no longer allows changes to the logical register
within that period. This rule not only applies for gas, but also for other divisions such as electricity and water.
Transaction EG76: Register Relationship
If the quantity determination for a register has been successfully carried out in a certain period, the system no longer allows changes to the register
relationship of the register within that period.
1.3.9.1.3.4 Estimation Procedure
If measurement data is incomplete or implausible, it may be necessary to replace or add to this data with estimated values. Data simulations and forecasts are
also based on estimations. In SAP Utilities, estimation procedures are used in the following processes:
Estimate meter reading results
Validate meter reading results
Billing simulation
Budget billing plan creation
Unbilled revenue reporting
The estimation procedures used are extrapolation and interpolation. When using the quantity determination procedure Quantity Determination During Meter
Reading , both of these procedures use the quantities saved in the system for the respective base period as a basis for estimation. The system uses these
quantities to calculate the quantity for the estimation period and then calculates the estimated value for the meter reading.
During extrapolation, a value is determined beyond the base period. During interpolation, a value is estimated between other existing values. The base period is
the period that contains all meter readings used as the basis for estimation.
One feature of the quantity determination procedure Quantity Determination During Meter Reading for the gas division is that the quantity is calculated once an
actual meter reading is available following one or more estimations (usually extrapolations). In this case, the gas factors are determined for the most recent actual
previous meter reading result. This part of the concept is described in section Interaction - Estimation and Meter Reading.
With these differences in mind, you can read the information about the classical estimation procedures for discrete values:
Classical Estimation Procedure
The aspects specifically relevant for quantity determination during meter reading are described in the following sections.
During estimation, assumptions are made regarding the time-related distribution of the quantity on which the estimation is based. This distribution is described with
a weighting function y(t). The examples in the further sections are based on a linear distribution of weightings in which the weighting function increases by one
unit per day. In practice, you can also set up and use other weighting methods in the system. For more information about weighting procedures and the necessary
Customizing settings, see Weighting Procedures.
Features
The following sections describe extrapolation and interpolation as estimation procedures for discrete data during the use of the quantity determination procedure
Quantity Determination During Meter Reading .
Extrapolation
Interpolation
The concept for calculating the quantity once an actual meter reading result is available following one or more estimations (usually extrapolations) is described in
the following section:
Interaction - Estimation and Actual Meter Reading
During the estimation procedure of extrapolation, a value is forecast for the entire base period.
The steps described below are carried out automatically by the system and are not visible to the user. The description should explain the algorithm that derives
an expected quantity from a quantity stored in the system and forecasts a meter reading result.
Features
When using the quantity determination procedure Quantity Determination During Meter Reading , extrapolation takes place as follows:
1. The saved (and rounded) quantities from the meter reading results in the representative base period are added together as a basis for extrapolation.
2. The system determines the weighting Y of the base period.
3. The system determines the weighting Ye of the forecast period.
4. The system determines the quantity Qe for the forecast date by multiplying the added quantity Q from the base period with the quotient of the weighting of
the forecast period and the weighting of the base period .
Formula
The factor ( Q / Y) describes the Expected Weighted Consumption .

5. From this forecast quantity Qe, that has not yet been rounded, the system calculates the estimated meter reading result E taking the relevant factors (such
as the gas factors and register factors) into account.
This is then rounded and saved according to the system settings.
6. Taking into account the factors from the forecast period, the system determines the final consumption value from the difference between the estimated meter
reading result E and the previous meter reading result MR1. The final consumption value is then rounded and saved.
Note
The system does not wait for actual gas factors for extrapolation, but determines the final quantity immediately. This means that no quantity determination
triggers are generated.
The following figure shows extrapolation using a simple example. The abbreviations have the following meanings:
Q = Quantity
Qe = Forecasted quantity
Y = Weighting of base period
Ye = Weighting of forecast period
MR = Meter reading result
E = Estimated meter reading result
Extrapolation
In the example, the base period is between MR0 and MR1; that is 12.31.2008 to 06.30.2009.
In the example, the forecast period is between MR1 and E; that is 07.01.2009 to 12.31.2009.
Constraints
Whereas during the classical quantity determination procedure, you can exclude estimated values from being used as a basis for extrapolation, this is not
possible when using the quantity determination procedure Quantity Determination During Meter Reading as the estimated quantities are also necessary as a
basis for extrapolation. If you have selected the Ignore Estimated Meter Reading Results During Extrapolation checkbox in the control parameters in Customizing
for Meter Reading Data Processing, the system ignores this setting as soon as a period exists in which the quantity determination procedure Quantity
Determination During Meter Reading is used for a register.
Customizing for SAP Utilities Device Management Meter Reading Basic Settings Define Control Parameters for Meter Reading Data Processing .
1.3.9.1.3.4.2 Interpolation
During the estimation procedure of interpolation, a value is estimated between two existing values. These existing values can be actual values or estimated
values.
The steps described below are carried out automatically by the system and are not visible to the user. The description should explain the algorithm that uses the
weighting procedure to distribute a quantity saved in the system and, from that, derives the estimated meter reading result.
Features
Interpolation Between Consecutive Meter Readings

When using the quantity determination procedure Quantity Determination During Meter Reading , interpolation between consecutive meter readings takes place
as follows:
1. The basis of interpolation between two meter reading results is the quantity saved and rounded for the second meter reading result.
2. The system determines the weighting Y of the base period
3. The system determines the weighting Ye of the period for which you want the quantity Qe to be estimated.
4. The system calculates the estimated quantity Qe as follows:
Formula
The factor (Q / γ) describes the Expected Weighted Consumption .

5. From this estimated quantity Qe, that has not yet been rounded, the system calculates the estimated meter reading result E taking the relevant factors (such
as the gas factors and register factors) into account.
This is then rounded and saved according to the system settings.
The following figure shows interpolation using a simple example: The estimated meter reading result E was interpolated based on the estimated quantity Qe.
The abbreviations have the following meanings:

MR = Meter Reading Result
Q = Quantity
Y = Weighting
E = Estimated Meter Reading Result
Qe = Estimated Quantity
Ye = Weighting for Estimated Quantity
Interpolation
Interpolation Between Non-Consecutive Meter Readings
The system prefers actual meter reading results to estimated meter reading results as a basis for estimation. If an estimated meter reading result follows an actual
meter reading result, the base period is extended as far as the actual meter reading result.
This is explained in the following figure.
MR = Actual Meter Reading Result
Y = Weighting
Q2 = Quantity for Meter Reading Result MR2
Q2' = New Quantity Dynamically Calculated for Meter Reading Result MR2 as Part of Interpolation
Ye = Weighting for Estimated Quantity
Example 1
In example 1, there are three meter reading results in the period December 31, 2008 to December 31, 2009: MR0, E1, and MR1. E1 is an estimated meter
reading result. The algorithm ignores this estimated result during interpolation and uses the two actual meter reading results MR0 and MR1 instead. As described
in the previous section Interpolation Between Consecutive Meter Reading Results , the basis for interpolation is the quantity saved and rounded from the second
meter reading result. This quantity Q2 refers to the period MR1 to MR2, which is from October 01, 2009 to December 31, 2009. However, for the interpolation, the
system needs a quantity that refers to the period from January 1, 2009 to December 31, 2009. The system calculates this quantity Q2' dynamically. The next
steps for determining the estimated value Ex are identical to steps 2-5 from the previous section Interpolation Between Consecutive Meter Readings .
Example 2
In example 2, there are three meter reading results in the period December 31, 2008 to December 31, 2009: MR0, E1, and MR1. E1 is an estimated meter
reading result. The algorithm ignores this estimated result during interpolation and uses the two actual meter reading results MR0 and MR1 instead. The basis of
interpolation is the quantity saved and rounded for the second meter reading result. This quantity Q2 refers to the period E1 to MR1, which is from April 1, 2009 to
December 31, 2009. However, for the interpolation, the system needs a quantity that refers to the period from January 1, 2009 to December 31, 2009. The
system calculates this quantity Q2' dynamically. The next steps for determining the estimated value Ex are identical to steps 2-5 from the section Interpolation
Between Consecutive Meter Readings .
Caution
During quantity determination for the estimated and saved meter reading result Ex, the estimated meter reading result E1 is used. The quantity saved for meter
reading result Ex refers to the period up to the previous meter reading result (E1 - Ex).
The base period can be extended in both directions. This is shown in the following example. You want to validate an actual meter reading result MR1, which is
between two estimated meter reading results E1 and E2. The estimation procedure of interpolation is also used during validation if you correct meter reading
results using transactions EL 27and EL29.
This is explained in the following figure. The same abbreviations are used as in example 1.
Example 3
In example 3, E1 and E2 are estimated meter reading results. The algorithm ignores these estimated results during interpolation and uses the two actual meter
reading results MR0 and MR2 instead. The basis of interpolation is the quantity saved and rounded for the second meter reading result. This quantity Q2 refers to
the period E2 to MR2, which is from October 1, 2009 to December 31, 2009. However, for the interpolation, the system needs a quantity that refers to the period
from January 1, 2009 to December 31, 2009. The system calculates this quantity Q2' dynamically. The next steps for determining the estimated value E are
identical to steps 2-5 from the section Interpolation Between Consecutive Meter Readings . The quantity saved for meter reading result Ex refers to the period up
to the previous meter reading result (E1 - Ex).
Interpolation Between Estimated Meter Readings

If interpolation or reversal takes place multiple times between estimated meter reading results, it is generally not possible to determine the original total
consumption.
This is explained in the following figure. The abbreviations have the following meanings:
Q = Quantity
Φ = Gas Factor
Example 4
In example 4, interpolation takes place between the estimated meter readings MR0 and MR1. The system uses the (averaged) factor Φ from the period MR0 to
MR1 in all steps for the conversion between meter reading and consumption. This ensures that the total consumption Q is retained:
Q= Qe + Q1.
If another meter reading is subsequently estimated between MR0 and E, the system uses the averaged factor Φe from the period MR1 to E for the conversion
between the meter readings and consumption values. However, as the factors Φ and Φe are generally different, the total consumption Q is not retained.
1.3.9.1.3.4.3 Interaction - Estimation and Actual Meter Reading
One feature of the quantity determination procedure Quantity Determination During Meter Reading for the gas division is the way in which the quantity is
calculated once an actual meter reading is available following one or more estimations (usually extrapolations).
Features
In this case, to harmonize the results, the gas factors are determined for the most recent actual previous meter reading result. The system calculates the quantity
as follows:
Formula
This is explained in the following figure.
Φ = Gas Factor
Example
In the example, E1 and E2 are estimated meter reading results. The gas factor Φe is an averaged value for the period E2-MR2. However, the gas factor Φe is not
used for quantity determination for the period E2-MR2. The gas factor Φt, which relates to the period up to the next actual previous meter reading result, is used
instead.
This procedure allows more consistency with regard to further actions in the period MR1-MR2, such as interpolation and deletion or correction of estimated meter
reading results.
1.3.9.2 One-Off Activities for Changeover
If you want to use the quantity determination procedure Quantity Determination During Meter Reading , you have to carry out certain activities to changeover to this
procedure. These activities are described in the following sections. Alternatively, choose the following links to access information about the one-off activities for the
changeover.
1. Check Company-Specific Starting Point
2. Activate business function Utilities, Quantity Determination (ISU_QD_1)
3. Define a quantity determination procedure for each division in Customizing
4. Use a report to convert existing installations
After changing over to this quantity determination procedure, there are a number of other activities you have to carry out in day-to-day business. For more
information about these activities, see Activities in Production Operation.
1.3.9.2.1 Check Company-Specific Starting Point
Before you change over divisions in your system to the quantity determination procedure Quantity Determination During Meter Reading , check the company-
specific starting point. This primarily refers to the gas procedures and rates used in your system as well as the enhancements and business add-ins you have
implemented. These procedures and rates have to meet certain prerequisites if they are to be used in collaboration with the quantity determination procedure
Quantity Determination During Meter Reading .
Gas Procedure
To enable a correct quantity determination, it must be possible to uniquely determine the gas factor between two meter readings. Therefore, we recommend that
you only use gas procedures that uniquely determine the gas factor.
The gas procedures that meet this condition are those that are based on arithmetic/weighted average value calculation.
Rates
Variant programs for quantity determination that are based on the input operand category QUANT can continue to be used without adjustment, with the exception of
variant program QUANTI25. Check the variant programs used in your system to determine whether you use them for special customer-specific solutions for
quantity determination. In certain circumstances, you may need to adjust the respective rates or schemas.
The variant program QUANTI25 - Display Register Operand for Consumption in Interim Dimension is not compatible with the quantity determination procedure
Quantity Determination During Meter Reading . This is because the variant can no longer calculate the interim dimension if the quantity has already been
determined during meter reading.
Enhancements and Business Add-Ins
Check the enhancements and business add-ins implemented in your system in connection with the implementation project to determine whether they are
compatible with the quantity determination procedure Quantity Determination During Meter Reading . Due to the high flexibility of the SAP enhancement concept,
these implementations are used differently in every company. This means that we cannot provide a universally valid statement regarding the compatibility of the
enhancements and business add-ins implemented in your system with the quantity determination procedure Quantity Determination During Meter Reading.
Therefore, you should analyze all enhancements and business add-ins that use meter readings and consumption values.
In the following tables you can find a selection of enhancements and business add-ins that may not be compatible with quantity determination during meter
reading.
If you have implemented one of the following enhancements, check for your implementation project whether it is compatible with the quantity determination
procedure Quantity Determination During Meter Reading :
Enhancement Description
EDMLELHR IS-U: Customer-specific extrapolation procedure
EDMLELAH IS-U: Comparison of extrapolation procedure of customer <-> IS-U
EDMLELHA IS-U: Extrapolation procedure for estimation of meter reading results
EDMLELHP IS-U: Extrapolation procedure with artificial period consumption
EBIA0015 IS-U: Backbilling customer exit
The following enhancements can no longer be taken into account if you use the quantity determination procedure Quantity Determination During Meter Reading .
EDMASSES – Customer-specific assessing check
See also: Information about Assessing under Important Notes.
EDMMR002 – Change to gas date during entry of meter reading results
This enhancement is replaced by the business add-in ISU_QD_GAS_DATE_CHANGE ( BAdI for Change to Gas Date During Entry of Meter Reading
Results ).
If you have implemented one of the following business add-ins (BAdIs), check for your implementation project whether the implementation is compatible with the
quantity determination procedure Quantity Determination During Meter Reading :
Business Add-In Description
ISU_USE_EASTE Use of EASTE entries
ISU_BENDEF_EPVG ISU: User-defined consumption per weighting unit
ISU_GEWSCHL_EXTRAPOL ISU: Determination of weighting key in extrapolation/assessing
1.3.9.2.2 Defining the Quantity Determination Procedure
The Quantity Determination Procedure determines how the energy quantity from meter reading results is determined or calculated at register level.
Note
The quantity determination procedure applies for all installations in which a device is installed.
You can use a quantity determination procedure to define the following for a register from a specified time:
1. Quantity determination is to be performed during billing.
This is the standard procedure that does not determine final quantities or consumption values until billing is performed. This procedure is possible for
cumulative and balancing consumption registers and demand registers.
2. Quantity determination is to be performed during meter reading.
This procedure determines the final quantities or consumption values during the meter reading. This procedure is possible for cumulative and
balancing consumption registers. This is required during deregulation so that the consumption values recorded can be sent to all authorized market
participants in a timely manner.
The quantity determination procedures determined here are used exclusively for discretely read registers and not for interval registers.
Use
Implementation phase (as part of an implementation project):
You can define the quantity determination procedure at register level for installations that already exist in the system: This can take place for an entire division, for
a division with a selection of installations, or for a division with a selection of meter reading units. Use the conversion report
REQD_SET_QDPROC_TO_REGISTER (see Defining the Quantity Determination Procedure for Existing Installations).
Caution
Read the documentation on Defining the Quantity Determination Procedure for Existing Installations carefully before carrying out the conversion.
Day-to-day operation:
For billing-related installation, modification, or removal, the system defines or changes the quantity determination procedure in the background when you save the
data. The following transactions are used to do so:
Billing-Related Installation (EG34)
Full Installation (EG31)
Full Replacement (EG30)
Billing-Related Removal (EG35)
Full Removal (EG32)
Device Modification (EG42)
Change Logical Register Number (EG60)
You can display the quantity determination procedure using the transactions Change Rate Data (EG70) and Display Rate Data (EG71).
Customizing
You define the quantity determination procedure required in Customizing.
You make the relevant settings in Customizing for SAP Utilities under Basic Settings/Enterprise Structure Define Quantity Determination Procedure . You
also define the division and date from which the procedure is to apply.
Example Customizing
The following Customizing setting specifies that consumption values as of January 15, 2011 for division 01 (Electricity) are determined during billing, and for
division 02 (Gas) are determined during meter reading.
Division Date Quantity Determination Procedure
01 January 15, 2011 02 (Quantity Determination During Billing)
02 January 15, 2011 03 (Quantity Determination During Meter Reading)
Conversion of Quantity Determination Indicator for Existing Installations

Changes to the Customizing settings do not have an immediate effect on existing installations. To define the quantity determination procedure selected for existing
installations at register level according to the Customizing settings, you have executed the conversion report.
Technical Transactions
If you use technical transactions, the system defines or changes the quantity determination procedure as follows at register level:
1. For a technical installation:
The quantity determination procedure is not defined or changed in this case.
2. For a full installation:
For a full installation at the electricity installation on January 01, 2011:
Device Register Valid from Valid to Quantity Determination

Procedure
NNN 1 January 01, 2011 December 31, 9999 02
In this case, the quantity determination procedure = 02 - Quantity Determination During Billing
For a full installation at the electricity installation on May 01, 2011:

Procedure
NNN 1 May 01, 2011 December 31, 9999 02
3. For a billing-related installation:

For an installation at the first installation (electricity installation) on January 01, 2011:

Procedure
NNN 1 January 01, 2011 December 31, 9999 02
The first installation is always regarded as the leading installation here.

During installation at the second installation (gas installation) on May 01, 2011, which is the leading installation according to the BAdI
ISU_QD_PROC.

Procedure
NNN 1 January 01, 2011 April 30, 2011 02
NNN 1 May 01, 2011 December 31, 9999 03
In this case, the quantity determination procedure = 02 Quantity Determination During Billing and 03 - Quantity Determination During Meter Reading
Note
If you install a device in several installations, you must implement the interface method IF_EX_ISU_QD_PROC-
>GET_LEADING_INSTALLATION in the BAdI ISU_QD_PROC to define which installation is the leading installation.
4. For a replacement:
1. If the quantity determination procedure for the old device was already defined before the replacement:
If the old and new device both have the same register data, the system transfers the quantity determination procedure from the old device to the
new device.
If the new device has more registers than the old device, the system determines the quantity determination procedure from the Customizing
settings for the new registers. It uses the replacement date as the start date for determining the quantity determination procedure.
If the new device has fewer registers than the old device, the system determines the quantity determination procedure from the Customizing
settings for the registers to be removed. The replacement date minus a day is used as the Valid_To date here.
2. If the quantity determination procedure for the old device was not yet defined before the replacement:
The quantity determination procedure for the old and new device is defined for the billing-relevant period.
5. For a billing-related removal:
5. For a billing-related removal:
1. If the quantity determination procedure for the device was already defined before the removal:
Note
This example shows the follow-on activity according to the example in point 3 (billing-related installation).
During removal from the second installation (gas installation) on December 31, 2011 the system does not change the quantity determination
procedure.

Procedure
NNN 1 May 01, 2011 December 30, 2011 03
NNN 1 December 31, 2011 December 31, 9999 02
During removal from the final installation (electricity installation) on February 01, 2012, the system changes the quantity determination
procedure as follows:

Procedure
NNN 1 May 01, 2011 December 30, 2011 03
NNN 1 December 31, 2011 January 31, 2012 02
2. If the quantity determination procedure for the device was not yet defined before the removal:
The quantity determination procedure for the device is defined for the billing-relevant period.
6. For a full removal:
1. If the quantity determination procedure for the device was defined before the removal:
The quantity determination procedure is determined from the Customizing settings for the device.
2. If the quantity determination procedure for the device was not yet defined before the removal:
The quantity determination procedure for the device is defined by the removal date -1.
7. For a technical removal:
The quantity determination procedure is not defined or changed for a technical removal. When the technical removal takes place, the quantity determination
procedure should already have been changed.
8. For a modification:
1. If the quantity determination procedure for the device was defined before the modification:
The system defines or changes the quantity determination procedure if the field Interval Length ID , Division Category , Reactive, Apparent or
Active Registers , is changed, or according to the Customizing setting made under SAP Utilities Device Management Installation
Basic Settings Define System Parameters for Installation/Removal/Replacement .
If you change the field Register Category, Register Code , the system determines the quantity determination procedure according to the
Customizing settings. If you modify other fields or have not made the Customizing setting under SAP Utilities Device Management
Installation Basic Settings Define System Parameters for Installation/Removal/Replacement , the system does not change the quantity
determination procedure.
2. If the quantity determination procedure for the device was not defined before the modification:
9. Changing the logical register number:
1. If the quantity determination procedure for the device was defined before the logical register number was changed:
If a new placeholder for a logical register number on screen is generated, the system determines the quantity determination procedure from the
Customizing settings, or from the Customizing settings and the BAdI implementation ISU_QD_PROC, if the device is installed in multiple
installations.
If a terminated placeholder for a logical register number on screen is extended, the system determines the quantity determination procedure for
the new period from the Customizing settings and the BAdI implementation ISU_QD_PROC, if the device is installed in multiple installations.
If a current placeholder for a logical register number on screen is terminated, the system restricts the quantity determination procedure to the
current date minus a day.
2. If the quantity determination procedure for the device was not defined before the logical register number was changed:
1.3.9.2.3 Defining the QD Procedure for Existing Installations
You can use conversion report REQD_SET_QDPROC_TO_REGISTER to define the quantity determination procedure at register level for installations that already
exist in the system. This can take place for an entire division, for a division with a selection of installations, or for a division with a selection of meter reading units.
A combination of a selection of installations and meter reading units is possible.
You can only access the report with a selected division. The report selects:
All installations of a division
Selected installations of a division
Installations for selected meter reading units of a division
Note
Note that the last time-based allocation to the installation is selected automatically for meter reading units.
Customizing
You have made the relevant Customizing settings for quantity determination under SAP Utilities Basic Settings/Enterprise Structure Define Quantity
Determination Procedure .
Before starting the report, you have to make the following settings:
Division
Date from which the procedure is valid (changeover date)
Requested quantity determination procedure
Caution
In the standard system, you can only change over to another quantity determination procedure if registers only contain meter reading results whose
meter reading date is before the changeover date (in Customizing). We recommend choosing dates for the changeover that are in the future and for which
no changeover has yet taken place.
For a rolling changeover, the changeover date can also be determined using a BAdI implementation within a period (for more information about the BAdI
implementation, see the Features section of this documentation).
Requested quantity determination procedure
Note
The conversion report REQD_SET_QDPROC_TO_REGISTER is a sample report that only supports certain scenarios (see the Constraints section of this
documentation). You can copy this report and adjust it to define your own project-specific scenarios.
Features
You can use this report to make the initial settings for the quantity determination procedure for existing installations.
When you define the quantity determination procedure, the system generates meter reading orders with meter reading reason 17 - Meter Reading Due To Change
in Installation Structure for consumption registers. The date of the generated meter reading orders is the day before the key date that you defined in Customizing
(date of meter reading order = Customizing date minus 1 day). You can determine the meter reading results by mass estimation, for example. This type of
changeover is called a key date changeover (for more information, see Notes About the Time of the Changeover).
If you use the Reverse Meter Reading transaction (EL37) to delete one of these meter reading results, the system generates a new meter reading order with
reason 17.
Note
Note that the conversion is a one-off action. Installations that have already been converted by the report or the technical transactions are not processed again.
During the conversion, demand registers are changed over to the quantity determination procedure 02 Quantity Determination During Billing . Resetting registers
and interval registers are changed over to the quantity determination procedure 01 Not Relevant for Quantity Determination .
Recommendation
With BAdI ISU_QD_PROC and method CHANGE_VALID_FROM_EADZ_QD, you can change the changeover date ( from-date ) of the new quantity
determination procedure. If you use the sample implementation of this BAdI, the system searches within a period ( key date from Customizing - 12 months to
key date from Customizing + 12 months ) for the last meter reading result with one of the meter reading reasons 01, 02, 03, 05, 26 or 27. The date that the
system finds replaces the changeover date ( from-date ) imported from Customizing. The last meter reading date is then used as the start of the new quantity
determination procedure and no additional meter reading orders are created. This type of changeover is called a rolling changeover (for more information, see
Notes About the Time of the Changeover). You can adjust this sample implementation to meet your own requirements.
If you modify a device that is installed in multiple installations with different divisions, change its logical register, or execute report
REQD_SET_QDPROC_TO_REGISTER, use the method GET_LEADING_INSTALLATION of the BAdI mentioned above.
For more information about BAdI ISU_QD_PROC and the available methods, see the respective system documentation.
Constraints
The following consistency checks separate the installations where conversion cannot take place as the prerequisistes have not been met:
1. Check to determine whether meter reading results exist in the future
2. Check to determine whether quantity determination procedure 02 Quantity Determination During Meter Reading is used for Dynamic Period Control (DPC
Billing).
Note
With dynamic period control (DPC Billing), you cannot use quantity determination procedure 03 - Quantity Determination During Meter Reading.
The technical device transactions execute the consistency checks mentioned above as well as others. See Check for Final Determined Quantity in Technical
Transactions.
If a conversion does not take place, because a meter reading result exists in the future (after the changeover date in Customizing), for example, you can solve the
problem by reversing the meter reading result and then carrying out the changeover of the quantity determination procedure.
Technical Options
Depending on the Test Mode and Error Mode check boxes in the Technical Options screen area, you can execute the report in different variants. For
example, with or without entering information in the database or the application log, or any combination of these options. We recommend that you initially start the
report in test mode.
Test mode selected - Error Mode not selected
An analysis is performed for installations selected in the system; the quantity determination procedure is not selected in the database. Detailed messages
are written to the application log.
Test mode not selected - Error mode not selected
An analysis is performed for installations selected in the system; the quantity determination procedure is selected in the database. Detailed messages are
written to the application log.
Test mode selected - Error mode selected
An analysis is performed for all installations with errors in the system (errors regarding an attempted but unsuccessful conversion); the quantity
determination procedure is not defined in the database. Information about installations with errors is also not saved to the database. Detailed messages are
written to the application log.
Test mode not selected - Error mode selected
An analysis is performed for all installations with errors in the system (errors regarding an attempted but unsuccessful conversion); the quantity
determination procedure is defined in the database. Information about installations with errors is saved to the database. Detailed messages are written to the
application log.
The application log is not saved in test mode.
The Detailed Appl. Log check box enables you to use a detailed log to view detailed information on installations that have already been converted and that have
been converted successfully.
Recommended Procedure
We recommend that you carry out the conversion in the following successive steps:
1. First define a meaningful way of creating intervals for your installations. For example, using meter reading units or by executing function module
ISU_INSTALLATION_INTERVALS.
2. Execute the report in test mode, analyze any errors, and correct them.
3. Execute the report in active mode, analyze any errors, and correct them.
4. Execute the report in error mode.
Note
Note that in active mode, the system sets object locks for the devices. During the generation of meter reading orders, locks are set at installation level.
Example for Special Configuration

The following arrangement with multiple device installations shows how the conversion report works:
Device 2 is installed in installation 1 and installation 2. Device 3 is installed in installation 2 and installation 3.
Example 1
If the selection criteria in the conversion report lead to the selection of installation 1, installation 2 is selected as well due to the shared device 2. Device 1 and
device 2 are converted. As a result, installation 1 is fully converted, and installation 2 is semi-converted, as device 3 is not converted.
Example 2
If the selection criteria in the conversion report lead to the selection of installation 2, installations 1 and 3 are also selected due to the shared devices 2 and 3.
Devices 2 and device 3 are converted. As a result, installation 2 is fully converted, and installations 1 and 3 are semi-converted, as devices 1 and 4 are not
converted.
1.3.9.3 Activities in Production Operation
Technical Transactions
During day-to-day use, the system automatically sets the quantity determination procedure defined for the corresponding division in Customizing at register level in
the following transactions:
Billing-Related Installation
Billing-Related Removal
Full Installation/Removal/Replacement
Device Modification
Change Logical Register Number
If a device is installed in multiple installations, the leading installation determines the quantity determination procedure. To determine the leading installation,
implement method Determine Which Installation is the Leading Installation (GET_LEADING_INSTALLATION) of business add-in Quantity Determination
Procedure (ISU_QD_PROC).
Process Quantity Determination Trigger

If a final quantity determination is not possible for certain meter reading results, the system automatically creates quantity determination triggers. Reasons for
creating quantity determination triggers include missing gas data or previous meter readings are not unique, for example.
A quantity determination trigger identifies a meter reading result without a final quantity determination and shows that quantity determination calculation has to be
executed again for a data record in order to get the final results. The availability of a final quantity is a prerequisite for subsequent processes such as billing.
Depending on the reason for the generation of the quantity determination trigger, carry out the following actions:
Reason for Quantity Determination Trigger Follow-On Action
01 - No Current Gas Data When current gas data is available, process the quantity determination trigger
02 - Previous Meter Reading Document Not Unique Enter the meter reading result and process the quantity determination trigger
99 - Other Process the quantity determination trigger
To execute quantity determination again, process the quantity determination triggers:

Single processing
Transaction Monitor Meter Reading Data (EL31)
SAP menu under Utilities Industry Device Management Meter Reading Monitoring .
Description of transaction EL31 under Monitoring of Meter Reading Results.
Mass activity
Transaction Process Quantity Determination Trigger (EQDTRIGGERMA)
SAP menu under Utilities Industry Device Management Meter Reading Monitoring
Process Quantity Determination Trigger
1.3.9.3.1 Process Quantity Determination Trigger
With the mass activity transaction Process Quantity Determination Trigger (EQDTRIGGERMA), you can carry out quantity determination for a large number of
installations in parallel based on the relevant triggers, allowing you to process high volumes of data efficiently.
Prerequisites
Business function ISU_QD_1 ( Utilities, Quantity Determination ) is activated.
Features
You can use the Process Quantity Determination Trigger transaction, which is based on the FI-CA mass activity framework, to generate intervals from which the
system can subsequently create jobs for quantity determination.
The parallel processing object used here is ANLAGE.
The system first generates open intervals for all existing installations. The upper limit of each interval is also used as the lower limit of the next interval. This
guarantees that all installations can be taken into account in the intervals.
Note
You can change these intervals manually.
At runtime, the system creates closed intervals for the installation intervals that are actually available at this time. The quantity determination triggers are
determined and processed for each interval based on the selection parameters: Quantity determination is executed for each quantity determination trigger.
Successful quantity determination results are saved in the meter reading document and are available for subsequent processes (such as billing). All successfully
processed quantity determination triggers are deleted. Quantity determination triggers that were not processed successfully (for example, if no quantity could be
determined due to missing calorific values) can be processed again at a later point.
Activities
You call the mass activity in the SAP Easy Access menu under SAP Menu Utilities Industry Device Management Meter Reading Parallel
Processing Process Quantity Determination Trigger .
Identify every run by specifying a date and a sequence ID that you can select without restriction. You must specify a new ID for each run.
The selection range of the mass activity offers the following select options and input fields, which you can find on the General Selections tab page:
QD Trigger Selection:
Meter Reading Unit
Rsn for QD Trigger
Sel. Date QD Trigger
Note
The selection date field is automatically filled with the current date and is used to determine quantity determination triggers that have been created and are to
be processed by the specified date. The system does not process quantity determination triggers that were created after the specified date.
Type of Run: Simulation run (indicator)

All input fields are optional. However, the selection date is always preassigned.
Processing of the quantity determination triggers takes place using the selection criteria you entered. You can further process any error messages that occur for
mass activities using Business Process Exception Management (BPEM) (see Enhanced Message Management).
Note
On the Technical Settings tab page, you can select an existing installation interval as a variant and either change it manually or create a new interval under
Variant Maintenance .
Example
You can either propose a specific interval size (such as 1000 installations) or propose a specific number of intervals (such as 20).
Under Number of Jobs , you can also define the number of parallel jobs between which interval creation is to be distributed. You can use explicit load
distribution to define how many jobs are allocated to each application server.
Recommendation
You can identify the optimum number of intervals to be created and number of jobs to be executed in parallel by performing the appropriate tests.
On the Logs tab page, you can display the jobs that have already run and see whether these were successful or trace any possible causes of errors.
Caution
If you suspend an active mass run using the function End Program Run Prematurely , you should then use the function Restart Run to continue
processing.
Other Notes
1. Once you have executed a mass run job, you cannot execute this job again using the same ID. If you want to execute it again, you must create a new
mass activity with a new ID.
If you start the run in simulation mode at first, you can use the same identification afterwards to execute an active run.
2. The status lines function Move Run Parameters allows you to move existing run parameters to a new run identification.
3. The application log displays the following statistical information for each processed interval: Number of determinations successful / with errors / not
necessary / not executed.
4. In the action menu, you can choose Environment Application Log to navigate directly to the application log.
More Information
For more information, see Quantity Determination and Quantity Determination Trigger Concept.
Purpose
This component manages device inspections and certifications. If a device passes an inspection in accordance with prescribed margins of error, it is certified for
a certain period and can be reinstalled. A device may be certified in one of the following ways:
As a device in a sample lot
Individually via periodic replacement
Individually via an SD order
There are two types of certifications:
The calibration validity of a device is renewed via an external certification carried out in accordance with legal requirements by a recognized inspection
office.
The quality of a device is inspected according to internal certification guidelines.
This component is optional. You require it if you wish to manage device inspections or certifications with the Utilities Industry (IS U) component.
Integration
If you would like to inspect devices that are already installed, they must be removed and replaced first. The following components are used for processing the
work order or notification required for removal and replacement:
Function Component
Entry of work order or notification Service Management (PM-CS)
Entry of replacement Replacement (IS-U-DM-DI-CH)
If a device can be inspected without being removed, you must also create an order or notification in PM-CS.

Purpose
Device inspection can be used for company inspections or official certifications of devices.
Process flow
Device inspection includes the following phases:
1. Sampling procedure
2. The sampling procedure reduces the number of devices to be inspected or certified. Devices are selected randomly from a large number of similar devices.
3. Device replacement
4. The devices to be inspected are removed or replaced via the periodic replacement function or via a special replacement order.
5. Inspection or certification
6. The removed devices are inspected or certified. Inspection is carried out internally. Certifications or official inspection are usually carried out by inspection
authorities.
Once the results of the certification are available, the individual devices are re-certified in the system and can be used again.
7. Renewal of lot certification
If the lot meets the certification requirements, the devices in the lot can be re-certified.
Result
The inspection process is used for inspecting and certifying individual devices. The sampling procedure is used for renewing the certification of many devices
through inspection of a small number of devices.
This component provides support during the selection and inclusion of devices in sample lots. Lots can be created for devices subject to certification in the
electricity, gas, water, and district heating divisions. Differentiating between external and internal sample lots meets the demands of legislators and internal quality
checks within an organization.
A defined number of sample devices are drawn from a lot. The result of the certification determines the renewal period of the entrie lot.
Caution
Due to the differences in legitimacy in different situations around the world (fcalibration authorities, for example), a general certification of this sampling
procedure is not possible. Therefore, check the legitimacy of this procedure with the relevant authorities before using it.
You can meet the different requirements of the described sampling procedure (regarding the sample drawing procedure in particular) by enhancing or adjusting
the standard procedure. The necessary interfaces are provided for this purpose.
Country-Specific Requirements
To meet the requirements of the Canadian market, you can use the sampling procedure for Canada.
For more information, see Sampling Procedure for Canada.
This component is optional. You need it for creating sample lots.
Integration
If a lot that is subject to external certification fails certification, all devices in the lot (except those that have already been removed) are added to the periodic
replacement list and are certified individually. Therefore, you need the Periodic Replacement (IS-U-DM-IS-PR) and Certification (ISU-DM-IS-CT) components.
Note
The device does not lose its certification if it is certified for a period longer than the lot certification period. In Customizing for Device Management , go to
Inspection Basic Settings Define Parameter(s) for Sampling Inspection/Certification and select the CP field (certification period of device overrides
period of lot).
The extent to which the inspections are carried out is based on the Inspection Point Group component (IS-U-DM-TD-IG) of the device category. You can then use
the Inspection Result Management component (IS-U-DM-TD-IG) to enter the inspection results. However, neither of these is a prerequisite for the sampling
procedure.
Purpose
The sampling procedure is used to select and subsequently inspect a random number of inspection-relevant sample devices drawn from a larger number of
devices.
Process Flow
The sampling procedure is divided into the following phases:
1. Lot creation
You create a lot master record that contains the lot data.
2. Allocation of devices to the lot
You determine the scope of the lot by allocating devices to the lot. When you do this, you must take into account the similarity of devices so that inspection
results are as representative of the entire lot as possible.
You can perform this function more than once.
3. Determination of lot devices
You prepare for lot drawing by creating a table of devices allocated to the lot. This serves as a basis for drawing sample devices.
4. Drawing sample devices
The sample devices are drawn from the devices allocated to the lot. The number of sample devices and spare sample devices is dependent upon the lot
size, the lot type or other legal requirements.
The number is a default value and is not checked by SAP. You can define a user-specific check of the number using customer exit (BAdI
CHECK_NUMBER_OF_SAMPLE_DEVICES).
5. Renewal of lot certification
If the sample devices meet the criteria for re-certifying the entire lot, the lot status in the lot master record is changed and the lot is re-certified.
1.4.2.1.1 Official/Internal Lots
Definition
IS-U devices are grouped into lots for purposes of inspection or certification.
Lots can be either official or internal.
Use
You can use an official lot in order to certify several devices via the sampling procedure.
You can use an internal lot in order to carry out company inspections on devices that by law are not subject to certification or inspection.
Structure
Lots may contain the following:
Code defining the lot as an official or an internal lot
Lot status
Compilation date
Date on which lot devices were determined
Lot size
Drawing date
Next due year
Break-up date
Integration
The lot number is entered in the device master record of the lot device. This entry is used to determine the next replacement year of the device, depending on the
status of the lot.

Use
This function enables you to allocate devices to a lot or remove devices from a lot.
Integration
This function is a prerequisite for subsequent device inspection functions.
You can use enhancement EDMLOT01 (Compile inspections/selections for lot) for this function. This enhancement allows you to perform addition device
inspections to decide whether devices are to be included in the lot.
Prerequisites
Before you can allocate devices to a lot, you must create the lot.
Devices can only be removed from an official lot if sample devices have not yet been removed from the lot.
Before you allocate warehouse devices to a lot or to prevent them from being allocated to a lot, you must establish customizing settings accordingly.
Features
You use selection criteria to allocate devices to an existing lot. You can either specify each device separately, or you can use the device category and other
selection criteria to determine multiple devices and allocate them to the lot.
You can also remove single devices or devices of a specific device category from the lot.
Activities
The system changes the lot compilation date in the lot master record to the current date and resets the number of lot devices.
1.4.2.1.2.1 Compiling Lots

Prerequisites
Before you compile official lots, sample devices must not be drawn from the lot.
Procedure
Note
You can also use report REGLOS04 to compile lots.
To allocate a single device to a lot, proceed as follows:

1. Choose Device Management Inspection Sampling procedure Compile lot .
2. You branch to the initial screen of the transaction.
3. Enter the lot number and choose Lot Add Single devices .
4. You branch to the entry screen for single devices.
5. Enter the devices and choose Save to add the devices to the lot.
To allocate several devices to a lot via the device category, proceed as follows:
3. Enter the lot number and choose Lot Add Via device category .
4. You branch to the entry screen for selecting devices from the sample lot via the device category.
5. Enter the device category and the number of devices to be selected. You can further restrict your selection by specifying a replacement year or a
construction year for the devices to be selected.
6. Choose Lot Determine device to determine the devices that match your criteria.
7. You branch to a list with the number of devices found for a certain device category.
8. Choose Save to allocate the devices to the lot and return to the initial screen.
1.4.2.1.2.2 Deleting Devices or Device Categories from Lots
Prerequisites
You cannot delete devices or device categories from an official lot if sample devices have already been drawn from the lot.
Procedure
Deleting individual devices
3. Enter the lot number and choose Lot Delete Single devices .
4. You branch to the entry screen for deleting devices from the sample lot.
5. Enter the devices you wish to delete and choose Save .
You return to the initial screen of the transaction.
Deleting devices of a device category
3. Enter the lot number and choose Lot Delete Via device category .
4. You branch to the entry screen for deleting devices from the sample lot via the device category.
5. Enter the device categories of the devices to be deleted. You can further restrict your selection by specifying the replacement year or the year of
construction.
6. Choose Save to determine and display the number of devices to be deleted. If you confirm the display, the devices are deleted from the lot and you return
to the initial screen of the transaction.
1.4.2.1.3 Determination of Lot Devices
Use
This function determines all devices that are allocated to a lot and writes these devices to an internal table. This internal table is used as a starting point for
drawing sample devices.
Prerequisites
Before the devices of a lot can be determined, devices must be allocated to the lot.
Features
With the appropriate customizing settings you can include warehouse devices when determining lot devices. This is controlled via an indicator on the initial screen
of the transaction.
Activities
The date of the last lot determination is changed to the current date in the lot master record and the number of lot devices is changed to the number of devices
determined.
1.4.2.1.4 Drawing of Sample Devices
Use
The sample devices and spare sample devices are drawn from a lot using random numbers . These devices are then removed and inspected in order to
assess the quality of the entire lot. Devices can remain installed for inspection if the Installed devs field (certify installed devices) is selected in the device.
You can determine:
Whether warehouse devices are to be taken into account
This is possible for the total lot procedure at the level of an individual lot or at drawing level.
Whether you require a single drawing or a double drawing
You can only determine this before the first drawing.
If a certain number of devices fails in the first of a double drawing, the devices determined in the second drawing are used. The number is specified by the
calibration authority in the case of an official lot and by the utility company in the case of an internal lot. In the case of an official lot, this number determines
the calibration authority. In the case of a company lot, it determines the utility company.
During lot device determination all lot devices receive an internal identification number . If the internal identification number of the device corresponds to the
random number, this device is drawn as a sample device. Once the fixed number of sample devices has been determined, the spare sample devices are
selected in the same way.
The following legal regulations apply to drawing:
Number of devices to be drawn
In Germany the calibration regulation of August 12, 1988 applies (Federal Law Gazette 1988, no. 43, p. 1657ff) §14.
Random number table
In Germany DIN (German Industrial Standard) 57 418 Part 6/VDE 0418 Part 6, June 1983 applies.
Algorithm for determining the random numbers
A maximum of two drawings per year
At the end of the drawing, a log is displayed that you should read line by line. It shows the stages of the drawing and a list of the sample devices and spare
sample devices. The drawing is not completed until the log is saved. The devices are then selected in their corresponding master records as sample devices.
The log can be printed as proof for the calibration authority.
If you want to use your own algorithm to draw sample devices you can do this by means of BAPI BAPI_ISULOT_INS_SAMPLE_DEVICES .
Prerequisites
In Customizing for Device Management the number of sample devices and spare sample devices to be drawn must be defined under Device inspection
Sampling procedure Define determination of sample devices .
This number is dependent on the following parameters:
Division
Indicator Single sample lot drawing
Type of certification requirement
Type of sample device (sample device or spare sample device)
Lot size
To carry out a drawing, you need to perform the following activities:
1. Create lot
Create a lot master record that contains the lot data.
2. Compilation of lot devices
During this process, the lot number is transferred to the master record of the devices allocated to the lot.
3. Determination of lot devices
In this process, all devices belonging to the lot are determined using the lot number entered in the device. They are given a consecutive internal
identification number and stored in a table. This table serves as a basis for future drawings. The table contents can be printed in the form of a list for the
calibration authority.
Features
The random number table consists of 50 lines (j) and 50 columns (i), in which the numbers 0 to 9 are arranged randomly . To display the table, select
Environment Display DIN table . The numbers are arranged in pairs so they can be read more easily.
The table is accessed until all required random numbers have been determined. A random number does not produce a sample device or a spare sample device
if:
The random number is larger than the lot size
The random number is zero
The random number has already been determined
The device has already been a sample device or a spare sample device (this can be changed via customizing)
The device is in the warehouse (if warehouse devices are not permitted during the drawing)
The device is not allocated to the lot (due to a removal, for example)
The device does not exist
The device cannot be processed during the drawing (due to changes to the device by a different transaction)
Initial Access
The first time you access the table is referred to as initial access and is used to determine the first random number. It consists of a starting line j and as many
starting columns i as there are digits in the lot size. You can change this before determination of the first random number.
Initial access is proposed automatically for every drawing and is determined based on the current time. Based on the minute as the starting column and the
second as the starting line, two-digit random numbers are determined from the random number table and used as starting lines or starting columns.
The following special features apply.
If the current time produces a first starting line or starting column that is higher than 50, that number is subtracted from 100 and the difference is used.
If the current time produces a first starting line or starting column of 0, the starting line or column 1 is used.
The two-digit numbers for the starting line or starting column are then found based on the starting line and starting column determined by the current time. The
following conditions apply:
If the first decimal place of a starting number is greater than four, it is ignored and the next random number is determined.
If a number is repeated during generation of the starting columns, it is rejected and a further random number is determined.
If two drawings have the same starting numbers, they will also have the same random numbers. This allows you to repeat a drawing, for example, for devices that
cannot be processed in the short-term (these devices are contained in the log). In this case, the drawing is not saved and the transaction is called again so that
the device can be marked as a sample device when it can be processed again.
First Random Number

The first random number is found where the starting line meets the starting columns. The start access is saved with the drawing date in the master record of the
corresponding lot so that information about the inspection is available at any time.
Further Random Numbers

The next random number is determined from the point where the line j + 1 meets the predetermined starting columns. If the line becomes j = 50 + 1, it is set
back to 1. However, each of the predetermined starting columns is simultaneously increased by 1. If, as a result of this process, a column becomes i = 50 + 1,
then it is set back to 1. Then line 2, line 3, and so on are accessed using the starting columns previously increased by 1.
Example
For a lot with 250 devices, a start access was randomly determined with the starting line j = 2 and the starting columns i = 1, 4, 3.
Excerpt from the DIN random number table:
Column i
Line j 1 2 3 4 5
1 2 2 1 7 6
2 1 9 3 6 2
3 1 6 7 7 2
4 7 8 4 3 7
From this table, the first random number determined is 163, the second is 177, the third is 734, etc. This third random number does not produce a sample device
since the number is larger than the lot size.
Using this algorithm, the random numbers are repeated after the table has been accessed 2500 times . Therefore, after the first 2500 times, the first starting
column is increased by 1, the second by 2, the third by 3, etc. After an additional 2500 times - if the start access has already been increased - the first column is
increased again by 1, the second by 2, and so on. However, the contents of the table are never changed.
1.4.2.1.4.1 Drawing Sample Devices
Prerequisites
Before you can draw lot devices, you must first allocate devices to the lot and determine the lot devices.
No more than two drawings are permitted per year.
Procedure
To draw sample devices, proceed as follows:
1. Choose Device Management Inspection Sampling procedure Draw sample devices .
3. Enter the number of the lot from which you wish to draw sample devices and choose Enter .
4. You branch to the next screen for sample device drawing.
5. Enter the number of sample devices or spare sample devices for the first drawing and, if necessary, select Warehouse dev. (inclusion of warehouse
devices) if your customizing settings permit this. You can also change the start access for the lot determination procedure. You also have the following
options:
1. If you select the Samp dev. percentage field when you create the lot, the default number of sample devices is determined on a percentage basis.
2. However, you must first define percentages in Customizing under Define Determination of Sample Lot Devices .
3. Depending on customizing settings under Define Determination of Sample Lot Devices, you can define a different number of sample devices for electronic
meters than for mechanical meters.
1. To carry out the first drawing, choose Draw sample devices .
2. To display the results of the drawing, choose Drawing Display Drawing 1 details.
3. If a second drawing is not permitted or you do not wish to carry out a second drawing, you must save the drawing.
You branch to the initial screen for sample device drawing.
Result
The sample devices that have been drawn are indicated as such in the device master record. The devices must be removed, if necessary, and subsequently
inspected or certified.
If you wish to carry out a second drawing, proceed as above and save the results after the first drawing.
1.4.2.2 Sampling Procedure for Canada
This sampling procedure can be used by utility companies in Canada to meet the requirements of the Canadian market. Before using this procedure, check its
legitimacy with the relevant authorities.
For more information about the requirements, see Measurement Canada.
The sampling procedure for Canada differs from the standard procedure with regard to the algorithm for determining random numbers and with regard to the type of
sampling procedure.
Another feature of the Canadian sampling procedure is that you can determine whether a lot meets the requirements for a sampling inspection before the samples
are drawn.
To learn more about the standard sampling procedure, see Sampling Procedure.
Prerequisites
You have checked the legitimacy of this procedure with the relevant authorities for your market.
The Canadian sampling procedure is activated (see section Activities).
Process
The sampling procedure runs as follows:
1. Create lot
You use the Create Lot transaction (EG80) to create a lot.
2. Compile the lot
Allocate devices to the lot. You can do this using the Compile Lot transaction (EG83) in dialog processing or report Enter Lot in Devices (transaction
EG8A) in background processing for larger numbers of devices.
3. Determine lot devices
In the Determine Lot Devices transaction (EG84), prepare for determining sample devices by creating a list of devices that are allocated to the lot. During
the Canadian sampling procedure, this list can also be displayed in an ALV grid with additional fields. You can sort the list by the individual fields.
4. Draw sample devices
You use the Draw Sample Devices transaction (EG8D) to draw sample devices. The result of the drawing is displayed in an ALV grid. You can sort the list
by the individual fields.
5. Extension of lot
If the sample devices pass the inspection, the lot is extended. If they do not pass inspection, you can carry out other drawings depending on the type of
sampling procedure. If the sample devices do not pass this inspection either, the lot is broken up. In this case, all of the devices in this lot are added to the
periodic replacement list and must be replaced.
Features
Algorithm for Determining Random Numbers

For more information, see Measurement Canada.
Type of Sampling Procedure

The type of the sampling procedure determines how many sample devices are permitted for a lot and whether the order of the drawing is relevant for the
inspection. The following procedures are relevant for the Canadian sampling procedure:
1 – Simple sampling procedure
One inspection only is permitted.
2 - Double sampling procedure
Two inspections are permitted.
3 - Multiple sampling procedure
A maximum of 5 inspections are permitted.
4 - Sequential sampling procedure
The order of the drawing is relevant for the inspection: The devices are inspected in the order in which they are drawn.
Lot Inspection
Before the sample devices are drawn, you can determine whether a lot meets the requirements for a sampling inspection. You can use the Time in Service
report (REGDEVLOT_CAN) to determine the time in service of individual devices or of all devices in a lot. The system proposes the selection criteria according to
the default implementation of the business add-in Selection Parameter Proposals for Time in Service Report (CL_SELECT_LOT_VALUES). Alternatively, you can
create your own company-specific implementation.
Activities
To be able to use the sampling procedure as described in the Process section above, you have to make the following settings:
1. Activate the Canadian sampling procedure in Customizing for SAP Utilities under Device Management Inspection Sampling Procedure
Country-Specific Settings for Canada Define Procedure for Determination of Random Numbers .
To activate the Canadian sampling procedure, select the Pseudo-Chaotic Algorithm entry for the determination of random numbers.
2. Define the type of sampling procedure for the determination of sample devices in Customizing. SAP Utilities Device Management Inspection
Sampling Procedure Country-Specific Settings for Canada Define Determination of Sample Devices .
1.4.3 Periodic Replacement
Purpose
This component manages periodic replacement. During a periodic replacement, devices due for certification are removed and replaced with equivalent devices.
You manage the devices to be replaced using the periodic replacement list, where you can also enter further devices, such as devices from an internal lot. You
can choose devices from the list that must be replaced at a certain time and then create a work order or notification for those devices.
This component is optional. You require it if
you wish to certify devices individually
a lot does not pass inspection and the devices must be certified individually
Integration
You need the Certification (IS-U-US-CT) component in order to certify a device that has been replaced.
1.4.3.1 Creation of Periodic Replacement Lists
Use
This function enables you to:
Create periodic replacement lists
Extend periodic replacement lists
Add devices with an advanced replacement year to periodic replacement lists
When a periodic replacement list is created, all installed devices are included whose periodic replacement year is before or the same as the specified periodic
replacement year.
The periodic replacement year is then obtained by adding the last certification year (in the device master record) and the calibration validity (in the device
category master record).
If a device is allocated to an official lot, the periodic replacement year of that device is specified when the lot is terminated. If a device has been allocated to an
internal lot, this is not taken into account during determination of the periodic replacement year for that device.
SAP recommends that you create periodic replacement lists in background jobs. You can select this option before you create a list.
Integration
You can create work orders or notifications for the devices once the periodic replacement list has been created. To do this choose, Create Work Orders or
Notifications .
Prerequisites
Only devices that have been installed and certified can be placed on the periodic replacement list. The devices for this installation process must be already
certified.
Features
When you create a periodic replacement list, the list for the current year is always cleaned up first. This means that all devices are removed from the list that have
not yet been removed or for which no orders or notifications have been created yet. Subsequently, all devices with the periodic replacement year in question are
included in the list. If desired, you can create the list only for devices of a specific division category.
When you extend the list for a year, you use additional specifications (see below).
You can combine these two steps if you make additional specifications when you create the list.
You can also specify the following:
Device category with/without replacement year and/or last certification year
Company area (processor ID)
Lot
Within one line, these specifications restrict one another (logical AND). Several lines have the effect of an extension (logical OR).
If you add devices to the list that have an advanced replacement year, you cannot use additional specifications. Adding such devices to the list is only a manual
extension.
Before you create or extend a list, a saved variant must exist. A variant contains all parameters for executing the function.
If devices belong to an official lot and the lot is terminated before the replacement list is created, then the devices of that lot are automatically included in the list.
However, if the lot is terminated after the periodic replacement list is created and the lot devices for this year are to be included in the list, then you must add those
devices after the list has been created.
A statistics or error log is created when a list is created or extended. You can also display these logs after executing Transaction SLG1 (Object: IUEG, Sub-
Object REP_STAT or REP_ERROR).
1.4.3.2 Work Order or Notification Creation
Use
This function allows you to create work orders or notifications for:
Devices from the periodic replacement list
Sample devices or spare sample devices from a sample lot.
Note
This section tells you how to create work orders. You use the same procedure to create notifications.
( )
Depending on the selection criteria you have entered, work order creation may require high system performance. Therefore, if you wish to create many orders
at once, we recommend that you create them in the background.
Integration
You cannot create orders for periodic replacement devices if you have not already created a periodic replacement list. Also, you cannot create orders for sample
devices or spare sample devices if you have not already carried out the sampling procedure.
Prerequisites
Selection options for devices from the periodic replacement list are either:
Predefined
Or dependent upon customizing settings in device management under Inspection Periodic Replacement List Define control parameters for periodic
replacement list.
Before you can create orders, you must allocate order codes to order profiles in Customizing for work management. To do this, choose Work Management
Processing Define order codes . For devices from the periodic replacement list, use the order code PREP, for sample devices or spare sample devices,
use order code SAMP.
Before you can create notifications, you must allocate notification codes to order profiles in Customizing for work management. To do this, choose Work
Management Processing Define Notification Codes .
Features
When you create replacement orders for devices from the periodic replacement list, you can select devices from the list using a periodic replacement year. You
can limit the selection using the following criteria:
Number of devices to be selected
Planned replacement year of the devices
Device category
Division category
Function class
Construction class
Meter reading unit
Company area
Regional selections (according to country, city, street and house number)
Free selections (in the case of active customer include for periodic replacement)
For regional selections, several lines have the effect of a logical OR, meaning the selection is extended.
When you create replacement orders for devices from sample lots, you can differentiate between sample devices, spare sample devices or first and second
drawing.
Each time you create an order, you can specify the basic start and end date. These dates are transferred to the SM order and used in scheduling.
You can also specify a default value for the maintenance planning plant. This value is used for determining the order profile if the system cannot determine the
maintenance planning plant internally.
If you wish to replace all devices in a device location, you can use Replace all dev. of dev. loc. You can restrict your selection by specifying one or more
divisions. Replacement orders are then created for all devices in the relevant device locations in the divisions specified.
It is also possible to carry out an interval check for all devices determined. During an interval check, the system determines whether a meter reading is
scheduled for a given device after the scheduled order date. Further processing is dependent upon the Display date overlap indicator. If you set this indicator,
you receive a list of all devices for which the meter reading interval check resulted in overlapping dates. The list specifies whether a replacement order is to be
created for the device or whether only an entry in the statistics log is to be made. If you do not set this indicator, a message is written to the statistics log for each
device with overlapping of dates.
If you create orders for devices that can only be certified while installed, then you must define a separate order code for these devices. This order code must be
allocated to the appropriate order profile in Customizing. You then allocate the newly defined order code to the device category of these devices. This means that
the allocated order code is used for all devices of this device category instead of the order code PREP or SAMP. You can also define this allocation at the device
level. In this case, a separate order code is allocated to a single device.
A statistics or error log is created each time work orders are created. You can also display these logs after executing the transaction or via transaction SLG1
(object IUEG, sub-objects WO_STAT or WO_ERROR).
1.4.3.3 Work Order Printout
Use
This function allows you to print work orders with IS-U data.
Because PM/SM orders do not recognize IS-U data, you use modified PM/SM print reports and a modified PM/SM print form.
Prerequisites
You must perform the following IMG activities for print control in maintenance order management:
Define shop papers and corresponding print layout
Maintain default shop papers for printing
In the first activity, you define a shop paper using a print form and a print report. In the second activity, you allocate the shop paper to each order type. The shop
paper then serves as a default for the order type.
Features
In IS-U, the print form ISU_JOB_TICKET is used. It contains fields for IS-U data in addition to the standard fields for order data. This form contains fields from a
variety of business processes although you do not always require all of the fields at once.
The link between this form and the individual print reports produces the shop papers. For each business process (in this case, each order category), there is one
shop paper. All IS-U print reports are in development class EEWM_PRINT.
The availability of IS-U data is dependent on the data of the individual print report.
Activities
SAP recommends the following procedure for modifying shop papers:
1. Copy the print report
2. Modify the print report.
3. Copy the form (ISU_JOB_TICKET).
4. Modify the form.
5. Use Transaction OID1 to define an individual shop paper using the print report and form you copied.
6. Use Transaction OID2 to define this shop paper as a print default for the order type.
Purpose
This component manages individual certifications of devices. If a device functions in accordance with legally prescribed standards, it is certified for a certain
period of time and can be installed (or reinstalled).
This component is optional. You require it if
you wish to certify devices individually
a lot does not pass inspection and the devices must be certified individually
Integration
Devices that you wish to certify are normally entered in the periodic replacement list via the Periodic Replacement (ISU-DMISPR) component. Devices that
have already been removed are not entered in this list, however.
The scope of the inspections is determined by the Inspection Point Group (IS-U-DM-TD-IG) component of the relevant device category. You can then enter
inspection results using the Inspection Results Management (IS-U-DM-IS-IS) component. Neither component is required for the sampling procedure.
Use
This function enables you to certify devices that have lost their calibration validity. A device might be certified due to a destroyed seal or as part of periodic
replacement or company inspection.
Prerequisites
You can certify devices at any time. There are no prerequisites for certification.
Features
Devices are certified based on the certification year. You can limit a certification to devices of a certain device category. You can specify whether only installed
devices or only removed devices are to be certified.
The following restrictions apply to the certification year:
Devices can usually be certified for the current year (system year) and previous years. You can only certify devices for the following year (system + 1) after
September 30 of the current year.
Example
Certification date: 09/30/1998 or 10/01/1998
Certification years permitted: 1998 and earlier or 1999 and earlier
Subsequently, by specifying the device serial number, you can enter all devices to be certified in the table. If a device belongs to a device group, the rest of the
devices of the device group can be included in the table automatically. For each device, you can specify certification number, a certification type and a seal code.
You can also enter the readings of all registers of the devices to be certified. Note that the meter readings you specify do not undergo a validation.
1.4.4.2 Seal Extension
Use
Seal extension is an enhancement to certification. Seal extension is used for certifying devices that have lost their calibration validity. A device might require seal
extension due to a destroyed seal or as part of periodic replacement or company inspection. Unlike certification, this function requires you to enter a seal date, a
certification type, and seal code.
Prerequisites
You can certify devices at any time. There are no prerequisites for certification.
Features
Seal extension is carried out based on the certification year and seal date of the device. You can restrict the seal extension to devices of a certain device category.
You can specify whether only installed devices or only removed devices are to be certified.
The following restrictions apply to the certification year:
Seal extension can be carried out for the current year (system year) and previous years. You can only certify devices for the following year (system + 1) after
September 30 of the current year.
Example
Seal extension date: 09/30/1998 or 10/01/1998
Certification years permitted: 1998 and earlier or 1999 and earlier
Subsequently, by specifying the device serial number, you can enter all devices to be certified in the table. If a device belongs to a device group, the rest of the
devices of the device group can be included in the table automatically. For each device, you specify certification number, a certification type and a seal code.
You have the option of entering a certification number.
You can also enter the readings of all registers of the devices to be certified. Note that the meter readings you specify do not undergo a validation.
1.4.5 Recording Device Inspection Data in Quality Management

The SAP Quality Management (QM) component is used to record and manage device inspection data in IS-U. This section describes the necessary system
settings.
Required Presettings
Table T156M
Before you can post a material transfer in the inspection stock, you must enter MA07 2 1 and MA07 2 2 in table T156M. If these entries are missing,
maintain them as described in note 119613.
Table TQ30
Enter inspection type 08ISU_01. Double click on the inspection type and maintain the following values:
Physical-sample type 08
Notification type F3
One notification per inspection lot X
Task list usage 9
Control key QM01
Transaction 9000
Table TQ34
Double-click on the inspection type to maintain the values for 08ISU_01. These values are then given when you allocate the inspection type to the material
(see Create Material).
Table TQ32
Enter inspection type 08ISU_01 for inspection lot origin 08.
Table TE131
If inspection type 08ISU_01 is defined for a material, this table must contain the movement types for which PM inspection lots have to be generated for
certification during stock transfer (standard U11).
Create material
If QM inspection lots can be generated for certification of equipment, you must specify the following in the material:
In the basic data 1, Unit must be specified as the base unit of measurement.
Under Quality Management you have to create inspection type 08ISU_01 for the inspection data and set the following detailed information fields:
Post to inspection stock X
Inspection with task list X
Automatic allocation of default values X
Inspect characteristics X
100% - inspection X
Skips permitted X
Automatic usage decision X
Single units possible X
When you enter check type 08ISU_01, ensure to set the Preferred indicator.
Serial number profile
In the serial number profile for IS-U equipment, you must enter serial number usage 02 (optional) for serialization procedure QMSL.
Inspection Plan
Description of the quality inspection process for the materials in a plant.
An inspection plan can consist of several operations. An operation determines which activity to execute at a work center. Operations can consist of several
inspection characteristics. An inspection characteristic describes what needs to be inspected.
In addition, the required production resources and tools can be determined for each operation.
Inspection Plan Header

In order to prevent getting multiple results per characteristic and device, ensure that the value 3 (unique external numbering) is entered in the External
Numbering field in the inspection plan header. If you do not do this, it is possible that multiple results are generated by the import of data from an external
system.
The Usage field must contain the value 9 (the same as in inspection type 08ISU_01).
Procedure
When processing inspection data, if you want to go directly to the units to be inspected view once you have selected the corresponding operation, you must enter
the value 11 (confirmation of results for units to be inspected) in the Recording View field.
If you want to be able to export lot data to a subsystem, you must specify a work center for every operation. The work center must in turn be allocated to a
subsystem. You maintain subsystems in transaction QSUB.
Communication with External Systems

RFC function modules are available in QM for communication with external systems. The names of all the function modules begin with QIRF_, which makes them
easy to find within the development environment.
QIRF_SEND... These function modules allow you to download data from an ERP system to a subsystem.
QIRF_GET... These function modules allow you to upload data from a subsystem to an ERP system.
For further details on the function modules, see the documentation for QM.
QIRF_SEND_REQUIRMENTS_GET_DATA
You use this function module to download operation and characteristics data to the subsystem. Ensure that the Record Type field in the I_QUAILS input structure
is empty and that the SUBSYS (Subsystem) field is filled.
QIRF_GET_ORIGINAL_VALUES
You use this function module to upload inspection data recorded in the subsystem to an ERP system.
For quantitative characteristics, use record type Q51. For qualitative characteristics, use record type Q52.
In order to be able to allocate the inspection data to the corresponding device, you must set the KZSERNR indicator in table T_QAISETAB and you must enter the
serial number in the SERIALNR field.
Process Flow
The cycle of the devices is generally the same:
1. Delivery of the devices
It is irrelevant whether or not the devices are serialized on delivery.
2. Install devices
The devices are serialized at this point at the latest.
3. Replace devices periodically.
At this stage, some of the removed devices must undergo certification. For this purpose, you must allocate the devices to be inspected to a QM lot according to
their category. Include as many devices in a QM lot as you want to process in one operation.
The individual inspections are specified in the inspection plan, which is automatically allocated to the QM lot when it is created.
A QM lot can be generated in a number of ways:
Generate QM lot manually
1. Transaction QM01.
2. Enter material, plant, and inspection lot origin.
3. On the next screen, enter the number of devices that you want to inspect using the QM lot (inspection lot amount).
4. The serial numbers of the devices are only allocated to the QM lot when you record the inspection results (transaction QE01).
5. Manual transfer of devices to inspection stock.
Generate QM Lot by Stock Transfer
1. Transaction MB1B.
2. Enter movement type U11, plant and, if necessary, storage location.
3. In the next screen, enter target stock location, material, the number of devices you want to inspect using the QM lot and, if necessary, a source stock
location.
4. Confirm the next screen without making any changes and on the following screen enter the serial numbers of the devices for inspection (use F6 for selection
help).
5. If you end the posting by saving, a QM lot with the specified devices is generated in the background and transferred to the inspection stock of the target
stock location.
6. Once the QM lots are generated and the serial numbers are assigned, you can enter the inspection data (transaction QE01).
Recording Inspection Data in External Systems
In this case, the subsystem must first download the inspection characteristics of the ERP system by means of the QIRF_SEND_REQUIRMENTS_GET_DATA
function module. Once all of the information exists in the subsystem, the inspection data can be fully recorded there.
Since the serial numbers can not yet be downloaded at this point, you must enter them manually when recording the inspection data.
In order to ensure that the inspection data is allocated to the correct device when it is uploaded to the ERP system, you must specify the serial number in every
data string.
Inspection Lot Completion
Once the inspection data has been recorded, you must close the characteristics before you can complete the inspection lot. Inspection lot completion (transaction
QA11) includes making a decision about the usage of the inspected material and transferring the devices from the inspection stock.
You can use UD code A from selected set 03 for the usage decision.
If you want the usage decision to trigger a follow-up action it makes sense to define your own usage decision. Proceed as follows:
Table TQ07:
Define a follow-up action
Define the function module to be executed for the follow-up action
Transaction QS00:
Define a code group
Define the codes that can be used in the code group
Define a selected set with status 2 (released)
Define the codes of the selected set referring to a follow-up action (TQ07)
In order to disburden the inspection stock, you must transfer the devices to one or more storage locations within the transaction.
1.5 Country Specific Functions

SAP Help IsU Device Management PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Help IsU Device Management PDF

Uploaded by

Copyright:

Available Formats

Device Management

PDF download from SAP Help Portal:

Created on December 19, 2014

Name in IS-U From component Name in Standard System

Device Plant Maintenance (PM) Equipment

Device Category Logistics Basic Data (LO-MD) Material

Device Number Logistics Basic Data (LO-MD) Serial Number

Integration of IS-U with MM, LO and PM

MM is also used for the following functions in device flow:

Procurement Purchase Requisition and Purchase Order from (MM-PUR)

Delivery Goods Receipt from Inventory Management (MM-IM)

Stock Transfer Goods Issue and Return Delivery from MM-IM

Serial Number Management

Goods Receipts for Purchase Orders

1.1 Technical Device and Connection Data

1.1.1 Register Group

1.1.1.1 Sample Register Relationship

1.1.2 Input/Output Group

1.1.3 Command Group

1.1.3.1 Creating Command Groups

1.1.4 Winding Group

1.1.5 Device Category

1.1.5.1 Device Category Creation

1.1.5.2 Creating Device Categories in IS-U

1.1.6.1 Device Creation

1.1.6.1.1 Inspection Relevance

1.1.6.2 Creating Devices in Plant Maintenance

1. Choose Utilities industry Device management Technology Device Create.

1.1.6.3 Creating Devices in Inventory Management

1. Enter the required data. Choose Continue .

1.2.4.1 Device Installation

1.2.1 Device Information Record

About AMI-relevant device information records

1.2.2 Device Grouping

1.2.3 Installing, Removing or Replacing Devices

Installing, removing or replacing a device from a device group

Installing, removing or replacing several devices

1.2.4.1 Device Installation

1.2.4.1 Device Installation

1.2.5.1 Device Removal

Device Removal for One Day in Future

Lot Membership and Certification

1.2.5.1 Device Removal

1.2.6.1 Device Replacement

1.2.6.1 Device Replacement

1.2.6.2 Replacement of Device Group with Another Device Group

1.2.6.3 Replacement of Device Group with Smaller Device Group

1.2.6.4 Replacement of Device Group with Larger Device Group

1.2.6.6 Replacement of Devices in a Device Group

1.2.6.7 Replacement of Device Group with Complex Device

1.2.6.8 Replacement of Complex Device with Device Group

1.2.7 Reversal of Technical Installations, Removals and

Full installation, removal or replacement

1.2.7.1 Reversing Device Installations

1.2.7.2 Reversing Device Removals

Reversing Device Removals:

1.2.7.3 Reversing Device Replacements

1.2.8.1 Device Modification

1.2.8.1 Device Modification

Special prerequisites for modification

1.2.8.1.1 Entry of Meter Reading Results During Modification

1.2.8.1.2 Allocation of Different Device Category via MM-IM

1.2.8.1.3 Allocation of Different Device Category via PM

01.01.2009 – 01.31.2009 620

01.01.2009 – 06.30.2009 2495

01.01.2009 – 12.31.2009 4395

01.01.2009 – 01.31.2009 620

01.01.2009 – 06.30.2009 2495