meter reading sap isu

DEVICE MANAGEMENTPDF download from SAP Help Portal:http://help.sap.com/saphelp_erp60_sp/helpdata/en/c6/4dc622eafc11d18a030000e829fbbd/content.htmCreated on March 10, 2014The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis PDF document contains the selected topic and its subtopics (max. 150) in the selected structure.Subtopics from other structures are not included.

2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG. The information contained herein may be changed without priornotice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 73

TABLE OF CONTENT1 Device Management1.1 Technical Device and Connection Data1.1.1 Register Group1.1.1.1 Sample Register Relationship1.1.2 Input/Output Group1.1.3 Command Group1.1.3.1 Creating Command Groups1.1.4 Winding Group1.1.5 Device category1.1.5.1 Device Category Creation1.1.5.2 Creating Device Categories in IS-U1.1.6 Device1.1.6.1 Device Creation1.1.6.1.1 Inspection Relevance1.1.6.2 Creating Devices in Plant Maintenance1.1.6.3 Creating Devices in Inventory Management1.2 Device Installation1.2.1 Device Information Record1.2.2 Device Grouping1.2.3 Installing, Removing or Replacing Devices1.2.4 Device Installation1.2.4.1 Device Installation1.2.5 Device Removal1.2.5.1 Device Removal1.2.6 Device Replacement1.2.6.1 Device Replacement1.2.6.2 Replacement of Device Group with Another Device Gr1.2.6.3 Replacement of Device Group with Smaller Device Gr1.2.6.4 Replacement of Device Group with Larger Device Gro1.2.6.5 Repl. of Dev. Group with Dev. Grp with Special Tec1.2.6.6 Replacement of Devices in a Device Group1.2.6.7 Replacement of Device Group with Complex Device1.2.6.8 Replacement of Complex Device with Device Group1.2.7 Reversal of Technical Installations, Removals and Replacements1.2.7.1 Reversing Device Installations1.2.7.2 Reversing Device Removals1.2.7.3 Reversing Device Replacements1.2.8 Device Modification1.2.8.1 Device Modification1.2.8.1.1 Entry of Meter Reading Results During Modification1.2.8.1.2 Allocation of Different Device Category via MM-IM1.2.8.1.3 Allocation of Different Device Category via PM1.2.9 Installation Structure1.2.9.1 Device Allocation1.2.9.1.1 Creating Device Allocations1.2.9.2 Rate data1.2.9.3 Register Relationship1.2.9.4 Period consumption1.2.9.5 Logical Register Number1.2.9.5.1 Changing Logical Register Numbers1.3 Meter Reading1.3.1 Weighting Procedure1.3.2 Extrapolation1.3.2.1 Extrapolation for Consumption Registers1.3.2.2 Extrapolation for Demand Registers1.3.2.3 Extrapolation for Resetting Registers1.3.2.4 Extrapolation with Billing Factor1.3.2.5 Proration of Meter Readings1.3.2.6 Extrapolation of Demand from Billing1.3.3 Meter Reading Organization1.3.3.1 Street Route1.3.3.1.1 Maintain Street Route for Meter Reading Unit1.3.3.2 Mass Changes to Meter Reading Units1.3.4 Meter Reading Order1.3.4.1 Meter Reading Order Creation1.3.4.1.1 Single Order Creation1.3.4.1.2 Mass Order Creation1.3.4.1.3 Meter Reading Control1.3.4.1.4 Reversal1.3.4.2 Order Output1.3.5 Meter Reading Result1.3.5.1 Meter Reading Result Entry1.3.5.1.1 Independent validations1.3.5.1.2 Dependent validations1.3.5.1.3 Upload1.3.5.1.4 Fast Entry With/Without Correction1.3.5.1.5 Single Entry1.3.5.1.6 Correction of Plausible Meter Reading Results1.3.5.1.7 Correction of Implausible Meter Reading Results1.3.5.1.8 Assessing


Page 2 of 73

1.3.5.2 Estimation1.3.5.3 Reversal1.3.6 Monitoring1.3.6.1 Monitoring of Meter Reading Results1.3.6.2 Device Overview1.4 Device Inspection1.4.1 Device Inspection1.4.2 Sampling Procedure1.4.2.1 Sampling Procedure1.4.2.1.1 Official/Internal Lots1.4.2.1.2 Lot Compilation1.4.2.1.2.1 Compiling Lots1.4.2.1.2.2 Deleting Devices or Device Categories from Lots1.4.2.1.3 Determination of Lot Devices1.4.2.1.4 Drawing of Sample Devices1.4.2.1.4.1 Drawing Sample Devices1.4.3 Periodic Replacement1.4.3.1 Creation of Periodic Replacement Lists1.4.3.2 Work Order or Notification Creation1.4.3.3 Work Order Printout1.4.4 Certification1.4.4.1 Certification1.4.4.2 Seal Extension1.4.5 Recording Device Inspection Data in Quality Management


Page 3 of 73

1 Device Management PurposeThis component manages technical data, installations, meter readings, and the inspection of devices.

IntegrationThe following table lists the standard R/3 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 systemDevice 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 function Goods Receipt. At the utility company, the device is labeled with this number.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 todistinguish it from other pieces of material that may have the same serial number. The equipment number is the same throughout the whole 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 ComponentProcurement 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-IMStock transfer Goods Issue

and Return Delivery from MM-IMEquipment records are created automatically at goods receipt. Therefore, functions of the PM application component are used, including standard orderingfunctions and creation of maintenance plans or task lists. Billing is then carried out with the Sales and Distribution (SD) application component.For more information, see:

PM:Equipment

LO-MD:

Material MasterSerial Number ManagementMM-PUR:

Purchase RequisitionsPurchase Orders

MM-IM:Planning Goods Receipts

Goods Receipts for Purchase OrdersGoods Receipts for OrdersOther Goods ReceiptsGoods IssuesTransfer Postings and Stock Transfers


Page 4 of 73

1.1 Technical Device and Connection Data PurposeThis component manages technical and connection data of devices:

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 aconnection object to the supply line.

1.1.1 Register Group PurposeThis component groups together the registers of one device category or one device, including technical data (such as number of digits and type of display) andbilling data (such as rate usage type). Registers meter consumption and demand. Registers can be actual physical devices or displays in electronic devices.

FeaturesYou 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 registerof the register group must be in the main division category.

1.1.1.1 Sample Register Relationship UseThis function allows you to allocate a sample register relationship to a register group.

FeaturesYou 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 PurposeThis component groups together the inputs and outputs of a device category or device and provides technical data of these devices. Inputs and outputs areinterfaces for devices. Remote meters have several pulse inputs and a modem interface.

1.1.3 Command Group PurposeThis component allows you to define commands and group them together. A command is a signal sent by the utility company that triggers a switching procedurein a ripple control receiver.


Page 5 of 73

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 PrerequisitesYou have created the appropriate commands for the command group.ProcedureTo create a command group choose Utilities industry Command/comm. group Create command group

1.1.4 Winding Group PurposeThis component groups together windings of one device or device category. Windings define the transformation ratio (of transformers, for example) and are dividedinto 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 considerationsThis component is optional. It is only required if you use transformers.

1.1.5 Device category PurposeThis component manages device categories. Each device belongs to a certain device category. The device category groups together all devices with similarfeatures (for example, price class, register group, or certification data).The various device categories can then be allocated to the following basic device categories:

MeterTransformerAudiofrequency ripple control receiverRemote meterCounterCorrectorPressure regulatorSensorOther

One device category can also be a combination of different device categories.

IntegrationThe device category corresponds to the material in the Logistics Basic Data (LO-MD) application component.For more information, see LO-MD:

Material MasterSerial Number Management

1.1.5.1 Device Category Creation UseThis function allows you to create device categories in the Utilities Industry (IS-U) component.IntegrationThis 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) applicationcomponent.Features


Page 6 of 73

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 allowyou 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.

If you use MM, we recommend the first option above.

PrerequisitesYou have maintained the following in IS-U:

Register groupsInput/output groupsCommand groupsInspection point groups (optional)Winding groups (only required for transformers)

1.1.5.2 Creating Device Categories in IS-U Procedure1. 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.ResultThe 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 Device PurposeThis component manages the devices of a utility company.Devices can:

MeterControl (such as audiofrequency ripple control receivers)Process data (such as correctors)Protect or adjust (such as pressure regulators)

IntegrationA device corresponds to a piece of equipment in the Plant Maintenance (PM) application component. It is uniquely identified in the system by:

The equipment number in PMThe combination of serial number and material number in the Logistics Basic Data (LO-MD) application component

The serial number is identical to the device number in the Utilities Industry (IS-U) application component and is labeled on the device.The material number is identical to the device category number in IS-U.

For more information, see:Technical Objects (PM-EQM):EquipmentLogistics Basic Data (LO-MD):

Material MasterSerial Number ManagementPurchasing (MM-PUR):


Page 7 of 73

Purchase RequisitionsPurchase Orders

Inventory Management (MM-IM):Planning Goods Receipts

Goods Receipts for Purchase OrdersGoods Receipts for OrdersOther Goods ReceiptsGoods IssuesTransfer Postings and Stock Transfers

1.1.6.1 Device Creation UseThis 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 additionto a corresponding piece of equipment in the Plant Maintenance (PM) application component.

IntegrationThis function uses many functions from the Plant Maintenance (PM) application component.

PrerequisitesYou have created the appropriate device category for the device.

FeaturesYou 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 moduleEXIT-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 meansthat 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 UseYou use this function to determine whether a particular device, such as an external device, is to be included in aSampling Procedure.

PrerequisitesYou have established settings for inspection relevance in Customizing. To do this, go to Utilities Industry Device Management Inspection SamplingProcedure Define Inspection Relevance of Devices.

1.1.6.2 Creating Devices in Plant Maintenance PrerequisitesThe appropriate device category for the device has been created.Procedure

To create several devices at once in the Plant Maintenance application component, choose Utilities Device management Technology Device Listediting Create.

01. Choose Utilities industry Device management Technology Device Create.You branch to the initial screen for creating material serial numbers.

Enter the material number, and if necessary the serial number and the equipment category used for IS-U devices. Chose Continue.The Enter IS-U data dialog box appears.

Enter the required data. Choose Transfer.


Page 8 of 73

You branch to the screen Create material serial number: IS-U data.Enter the required data.Save your data.

ResultThe device has been created as a piece of equipment in the Plant Maintenance application component.

The material stock of the Inventory Management (MM-IM) application component was not updated.

1.1.6.3 Creating Devices in Inventory Management PrerequisitesThe appropriate device category for the device has been created.Procedure1. Choose one of the following menu paths:

-Utilities industry Device management Technology Device Inventory management-Logistics Materials management Inventory management2. Choose Goods movement Goods receipt and select the appropriate type of goods receipt.You branch to the initial screen for entering goods receipts.

The type of goods receipt you choose depends on your processing steps up until now. For example, if you have created an orderfor the devices to be created, choose Goods receipt For order. Alternatively, you can choose Goods receipt Other.

3. Enter the required data. Chose Continue.You branch to the screen for entering new goods receipt items.4. Enter the material, the quantity and if necessary other data. Chose Continue.The Maintain serial numbers dialog box appears.

a. Choose Create serial number automatically or enter the number manually. Choose Previous screen.You branch to the Enter IS-U data dialog box.b. Enter the required data. Choose Copy.You branch to the screen where you can perform collective processing for goods receipt entry.

From the Enter IS-U data dialog box your branch to the classification system, which enables you to classify devices according toyour own criteria. Choose Classification.

5. Save your data.You can now enter further devices as above.ResultThe device has been created as a piece of equipment in the Plant Maintenance application component. The material stock of the Inventory Management (MM-IM) application component was not updated.

1.2.4.1 Device Installation PurposeThis component allows you to do the following:

Install, remove, and replace devicesYou 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 dothis, 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.

IntegrationYou can use the IDoc ISU_DEVICE_CHANGE to transfer data from external systems to the work process. You can enter one meterreading result per action. It is currently not possible to process multiple meter readings.


Page 9 of 73

If a meter reading is implausible, IDoc processing is not canceled. You can correct the reading. For more information, see Correction ofImplausible 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 andreplacement. You have the following options:

Installation and removalYou can enter the target plant and storage location as well as the movement type on the initial screen.

Device replacementYou can enter goods movement data (target plant and storage location and movement type) for device removal and installation. You can also enter other datasuch as the cost center.

To activate these functions, you have to define parameter GOODSMVMT in Customizing under Installation System Parameters forInstallation/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.

1.2.1 Device Information Record DefinitionThe device information record is an object in the IS-U system that enables the system to perform billing-orientated functions.

UseWhen 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 informationrecord that only manages device data required for billing, for example, rate data, device allocations, register relationships and maintenance of logical registers.

IntegrationThere is no longer a connection to Plant Maintenance (PM). Communication with other systems, such as importing consumption data, takes place via the point ofdelivery.

1.2.2 Device Grouping PurposeIn 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 adevice group, all other devices in the group are automatically drawn for removal or installation. This ensures that devices that belong together are not accidentallyinstalled or removed. You must confirm the replacement of each device in a device group.

Implementation considerationsThis 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.

FeaturesYou 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, whetheryou 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 groupGroup typeGroup categoryTerminate 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.


Page 10 of 73

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 ProcedureInstalling, removing or replacing a single device

Enter your device (enter both devices in the case of a replacement).Enter the required data on the screen for either installation, removal, or replacement.Save your data.

Installing, removing or replacing a device from a device group1. 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.

2. Process the work list.3. Enter the required data for each device on the screen for either installation, removal, or replacement.4. Save your data.Installing, removing or replacing several devices

Do not enter a device, device category or division.Enter the devices in the worklist or set the Rem. (removal) indicator.Process the work list.Enter the required data for each device on the screen for either installation, removal, or replacement.Save your data.

1.2.4.1 Device Installation PurposeIn 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 utilityinstallation. 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, seeReversal of Technical Installations, Removals and Replacements

FeaturesInstallation includes the following functions:

Allocation of devices (e.g. transformer to meter)Entry of periodic consumptionEntry of meter readings recorded at the time of installationCreation of register relationshipsAdopting

Sample Register Relationships

You can define a default measured pressure for technical installation. To do this, you have to establish settings in Customizing under DeviceManagement 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.

1.2.4.1 Device Installation PurposeYou 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 ifMeters in an apartment building are installed first and assigned to apartments laterBoth steps are carried out by different agentsOne technical installation and several billing-related installations. This would apply in the case of a pressure regulator or an ARCR that controls several


Page 11 of 73

installations.Full

installation, as in the case of a single-family home.

PrerequisitesWhen 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 beenentered 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 locationsEquipmentEquipment at Functional Locations

Process flowDevice installation includes the following phases:

01. 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 companyrequirement (such as a switching change) or an external requirement (new connection),

02. The installation order is executed and returned.03. 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 DevicesNote the following:

01. If the device belongs to a device group, the entire device group must be installed in the case of technical installations and full installations.02. 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 registergroup.

ResultTechnical 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 installationThe 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 installationThe device is installed in the device location with respect to technical dataThe device is allocated to an installation for billing.

1.2.5.1 Device Removal PurposeYou 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-relatedremoval, 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, seeReversal of Technical Installations, Removals and Replacements

FeaturesYou must enter the meter reading recorded upon removal if a reading was not entered already for that date.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.


Page 12 of 73

1.2.5.1 Device Removal PurposeYou 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 removal later, for example if billing and technical areas in a utility company are managed by different employees.One billing-related

and several billing-related removals. This would apply in the case of a pressure regulator or an ARCR that controls several installations.Full

removal, for example in the case of a single-family home that is dismantled.

PrerequisitesWhen 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 beenentered after 10/08.

Before a technical installation can be performed,The device must not have already undergone billing-related installation on the removal dateThe device must not control any other deviceNo register of the device may be part of a register relationship that is automatically terminatedIn 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.

For more information see the following in the Technical Objects (PM-EQM) application component:

Functional LocationsEquipmentEquipment at Functional Locations

Process flowDevice removal includes the following phases:

01. A removal order is created for a device or a device group in the Service Management (PM-SMA) application component. This results from a companyrequirement (such as the dismantling of an object) or an external requirement (new connection).

02. The removal order is executed and confirmed.03. The removal of the device is entered in IS-U.

For more information, see

Installing, Removing, and Replacing Devices

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 youdefine system parameters for installation/removal/replacement.

ResultTechnical 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 removalThe 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 removalThe device is removed from device location with respect to technical dataThe system terminates all billing-related allocations of devices to installations.

Device Replacement Purpose


Page 13 of 73

This component allows you to enter the replacement of a device by another device with the same function from the same or similardevice category. A device is replaced instead of being both removed and installed if the following data is to be transferred to the newdevice:

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 ConsiderationsThis 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 toreplace a device. For example, a replacement is necessary if an installed device is damaged or if it is to be certified with the DeviceInspection (ISU-DMIS) component.

IntegrationYou can transfer data to external systems using IDoc ISU_RPL_ORDER.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 use enhancement EDMEG901 to change the predefined order and notification codes when work orders or notifications arecreated.

FeaturesIn 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 andchoose Device Management Installation Basic Settings Define System Parameters for Installation/Removal/Replacement.

1.2.6.1 Device Replacement PurposeThis process enables you to replace devices.

You replace a double-rate meter as part of a periodic replacement or due to damage.

You can replace devices that have different measuring types. However, you may have to change the measuring types in the device allocation data.

PrerequisitesWhen 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.

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 beenentered 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 thePlant Maintenance application component.For more information see the following in the Technical Objects (PM-EQM) application component:

Functional LocationsEquipmentEquipment at Functional Locations

Process flowDevice replacement includes the following phases:

01. 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 companyrequirement (such as a switching change) or an external requirement (such as a change in use of the object).

02. The replacement order is executed and confirmed.03. The replacement of the device or of all devices in a device group is entered in IS-U.


Page 14 of 73

For more information, see

Installing, Removing, and Replacing Devices

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 nottransferred to the order automatically as additional items.

The system automatically checks and prorates the attributes (such as measured pressure, billing factor, or command) of existing device allocations. Amessage is displayed if the system cannot check attributes automatically. You can go directly to the device allocation and check attributes manually. To dothis, choose Goto Device allocations.

ResultThe 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.

1.2.6.2 Replacement of Device Group with Another DeviceGroup PurposeThis process can be used for replacing one transformer group with another transformer group, for example.Process flowDevice 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 DeviceGroup PurposeYou can use this process to replace three devices in a meter board with two devices, for example.Process flowDevice 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


Page 15 of 73

1.2.6.4 Replacement of Device Group with Larger DeviceGroup PurposeYou can use this process to replace two devices in a meter board with three devices, for example.Process flowDevice 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 and2a, 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. PurposeYou can use this process to install devices with different tasks in a meter board, for example.Process flowDevice 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.

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 beinstalled (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 PurposeThis process can be used for replacing an audiofrequency ripple control receiver in a meter board, for example.Process flowA 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 thedevice group. Devices 2a and 3a are not affected.Replacement of devices within a device group


Page 16 of 73

1.2.6.7 Replacement of Device Group with Complex Device PurposeThis process can be used for replacing a meter board with a complex meter, for example.Process flowDevice 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 PurposeThis process can be used for replacing a complex meter with a meter board, for example.Process flowComplex 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 andReplacements UseYou 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 RemovalsReversing Device InstallationsReversing Device Replacements

PrerequisitesThe device must not have been installed for billing, that is, it must not be allocated to an installation.

FeaturesFull installation, removal or replacementThis function does not make changes to the data of the following objects:

Register relationships and reference valuesStatistics recordsDevice allocations for controlling devicesBlocked devicesDevice groups


Page 17 of 73

The reversal does not take into account any device transfers you have carried out.

Reverse InstallationWhen you perform aninstallation 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 outin 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 RemovalAremoval reversal results in the termination of a technical removal in the Utilities Industry (IS-U) and Plant Maintenance (PM) components. An installation is carriedout in PM at the time of removal.Reverse ReplacementAreversal replacement results in the termination of a device replacement in the Utilities Industry (IS-U) application component In the Plant Maintenance andService Management (PM) component, the old device is automatically re-installed and the current device is removed.

1.2.7.1 Reversing Device Installations UseThis procedure enables you to cancel device installations

PrerequisitesYou have executed a device installation that you want to cancel.

Procedure01.

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.

Terminate any device allocations or relationships you have created.Reverse the installation.

The device has now beentechnically removed.

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.

ResultThe device installation has been fully reversed. The device now has the status Removed again.

ExampleInitial 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:

01. 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.

02. 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.

03. Reverse the installation.


Page 18 of 73

1.2.7.2 Reversing Device Removals UseThis procedure enables you to cancel device removals.

PrerequisitesYou 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.

ProcedurePerform the removal reversal.

The device has now beentechnically installed.

Create any device allocations or relationships you may have terminated.Install the device (

billing-related installation) in all installations on the removal date.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.

ResultThe device removal has been fully reversed (technically and billing-related. The device is installed.

ExampleInitial SituationDevice 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:

01. Reverse the technical removal from device location DL1 for the 10 February 2000.


Page 19 of 73

02. Perform a billing-related device installation of device D1 in the installation 1 (Inst.1) for February 10, 2000.03. 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 UseThis procedure enables you to reverse device replacements.

PrerequisitesYou 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 orDevice 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 eachinstallation date.

You can determine the installation date via the Utilities Industry menu under: Device Installation Installation Installation Structure Rate Data orUtilities 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 removaldate. 6. Perform a stock transfer for the device removed. 7. Perform a stock transfer for the device removed.

ResultThe replacement has been fully reversed. The device now has the status Installed again.

ExampleInitial 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.


Page 20 of 73

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 andInst.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.


Page 21 of 73

1.2.8.1 Device Modification PurposeYou 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.Implementation considerationsThis component is optional. You can use it for resetting device parameters as well as reprogramming, modifying, and reconnecting devices. Examples ofmodification include:

Changing the register configuration of a deviceUsing a different winding of a transformer

FeaturesModification 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)

1.2.8.1 Device Modification UseThis function allows you to change device data and register data. This function does not allow you to change device categories, however.

PrerequisitesNote 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 systemmust correspond to the actual history of the processes.

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 beenentered after 10/08.

Special prerequisites for modificationActivity PrerequisitesChange 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.

ActivitiesIf 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 devices 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 asnecessary.

A message is displayed if the automatic adjustment is not possible. You can go directly to the device allocation and check and adjust the attributemanually. 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.


Page 22 of 73

1.2.8.1.1 Entry of Meter Reading Results During Modification PrerequisitesYou have changed the technical register data.ProcedureChoose 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 PrerequisitesThe device you wish to modify is maintained in the Inventory Management (MM-IM) application component.Procedure

Choose Logistics Materials management Inventory management.

Choose Goods movement Transfer postingYou branch to the screen for entering transfer postings.

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.ResultA different device category (material) has been allocated to the device.

1.2.8.1.3 Allocation of Different Device Category via PM PrerequisitesThe device you wish to modify is not maintained in the Inventory Management (MM-IM) application component.Procedure

Choose Logistics Plant maintenance Technical Objects

Choose Serial numbers Change and enter the serial number. Chose Continue.Choose Serial data and then Edit

Change material no.The Change material serial number dialog box appears.

Enter the new material. Chose Continue.

You may be notified of the system status of the device (piece of equipment).Save your data.

ResultA different device category (material) has been allocated to the device.

1.2.9 Installation Structure PurposeYou can use this component to manage technical and billing data as well as period consumption of devices.FeaturesTechnical data

Device allocationsdescribe 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 takeninto account when creating a meter reading order:

-Allocation of active registers to reactive registers for calculating the cosine phi-


Page 23 of 73

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 registersdescribe 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 logicalregister 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 dataRate datais 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 billingThe rate type of a registerThe price class

Period consumptionThe 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 creationCannot be used, for example if there is a change of tenantAre to be ignored, for example if the customer has a complaint regarding budget billing

1.2.9.1 Device Allocation UseThis 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.

IntegrationYou 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.

PrerequisitesThe devices to be allocated to one another must have undergone a technical installation and have certain characteristics depending on the allocation type. Onlywater 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.

FeaturesDevice 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 sliceinto two slices and maintain them.

Time slice: 01/01/1996 to 12/31/1999Period already billed: 01/01/1996 to 12/31/1999The 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 canbe 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 gasmeters 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 theregister 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 devicethat 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 thisindicator to display the valid devices with corresponding validity periods. You can also display these devices by selecting the appropriate line and choosingExtras 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.

ActivitiesWhen you maintain billing-relevant device allocations, you must enter meter readings for the devices. In the case of sub-annual changes, you must enter meterreadings manually.


Page 24 of 73

1.2.9.1.1 Creating Device Allocations PrerequisitesThe devices have undergone a technical installation.You now wish to maintain device allocations.

ProcedureChoose Device installation

Installation structure Device allocations MaintainYou 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 tothe 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 periodof 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 keydate. 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 devicerelationships.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 isvalid for all registers of the device.

03. 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 allocationsat the register level are then automatically generated and displayed. SAP recommends this procedure for devices with many registers. If necessary, you cancorrect individual allocations after they are generated.

04. Once you have entered all allocations, save your data.05. 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 UseThe 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 levelis 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 isallocated. 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 mightinclude the indicator for relevance to billing, the rate type and the price class.

IntegrationWhen 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.

PrerequisitesThe device has undergone a billing-related installation.

FeaturesRate 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 sliceinto 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 theregister 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 thesubsequent lines for the register that apply to other installations, the multiple-installation data is only displayed.

ActivitiesIn 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 forthe devices. In the case of sub-annual changes, you must enter meter readings manually.


Page 25 of 73

Register Relationship UseThe 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 InstallationStructure Register Relationships.

PrerequisitesThe device must first undergo a technical installation.

ActivitiesThe meter reading results of the registers in question must be determined.

Deleting Registers from the Existing 1.2.9.3 Register RelationshipIf you want delete the registers of a device from an existing register relationship, you cannot enter this device in the initial screen of theChange Register Relationships transaction. If you do enter the device to be removed, the system issues the message EN478 (at leastone 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 installedin the device location or installation.

Limitations when Processing Register Relationships

General LimitationsAll registers affected by the register relationship must be installed over the whole processing period. A register relationship can onlyexist once within a period.

Customizing RestrictionsYou can find the Customizing settings for register relationships under SAP Utilities Tools System Modifications User-DefinedFunction 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 bewithin 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 thesame installation.

See Define Types of Register Relationships in Customizing.

Restrictions for Different Register Relationship TypesRestriction for Active/Reactive Relationship 01Reactive and active registers must have the same register category. The system does differentiate between cumulative and balancingregisters.For the reactive register, enter reactive register in the RA field (difference between reactive, apparent and active registers).For the active register, enter active register in the RA field.Restrictions for Serial Switching Relationship 02Serial Switching only for Consumption RegistersSerial switching is only supported for consumption registers. Primary and secondary registers must therefore have the registercategories cumulative or balancing consumption register.Serial switching of demand registers is not possible. In demand registers, the measured demand peaks from primary and secondaryregisters do not necessarily occur at the same time. The difference of demand from the primary register minus the demand from thesecondary 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.


Page 26 of 73

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 RelationshipsDefine Types of Register Relationships.

Serial Switching of Different Secondary RegistersThe primary meter can only be the primary meter in one serial switching relationship. You can allocate more than one secondary meterto one primary meter in a serial switching relationship, however. If this is the case, the total of all secondary meter consumptions issubtracted 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 IndicatorsPrimary and secondary reactive/active indicators must match.Installation AllocationDuring 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 notbilling-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-

RelevantRate

D1 1 RA ' ' RT10G2 1 RA X RT10

Rate data from installation B:


Page 27 of 73

Device Register Rate Type Register Not Billing-Relevant

Rate

G2 1 RB ' ' RT50

Step 2:Create the register relationship.

Device Register Operations CodeD1 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 D2is 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 rateshave 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 haslinear 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 hasweighting 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 deviceD2 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

MeasurementWeightingProcedure

D1 1 RA ' ' RT80 MWh LinearG2 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

MeasurementWeightingProcedure

G2 1 RB ' ' RT50 kWh Weighting ofenergy feeding

Result

When you enter meter reading results for D2, the plausibility checks are always executed with the billing unit of measurement kWHand weighting of energy feeding. The plausibility check and extrapolation of meter reading results from D2 are dependent on whetherthey 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 consumptionfor both devices are converted into MWh. The MWh consumption of the secondary meter is subtracted from the MWh consumption ofthe 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 beavoided. If different weighting occurs, secondary meter consumption in a prorated time slice may be calculated higher than primarymeter consumption. This can occur even when the total primary meter consumption is larger than the total secondary meterconsumption. As a result of this, we recommend that you avoid using different weighting whenever possible.


Page 28 of 73

Register DiscountYou can also offer discount on registers that are serially switched. Note the order in which the serial switching and register discount areprocessed 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 useregister discounts. If this is the case, you must enter a suitable register factor for the secondary meter. The register factor is included inbilling before the deduction consumption is calculated.Restrictions in a Primary Rate Secondary Rate RelationshipPrimary and secondary registers must have the same register category.The system does differentiate between cumulative andbalancing registers.The entry in the BW field must be the same for the primary and secondary rate register.Restrictions in Control Relationship 04Register and control register must have the same register category.The system does differentiate between cumulative and balancingregisters.The entry in the BW field must be the same for the register and control register.Restrictions in Volume Correction Factor Relationship 05Both 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 correctionfactor 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 06Both 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 andvolume 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 07The 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 08Both 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 09Only watt registers and consumption registers can be used.

1.2.9.4 Period consumption UseIn 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 consumptionpatterns 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 customers environment have changed (for example, by converting the measuring accuracy (register factor) of the meter duringthe 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 consumptionpatterns of a customer have changed)

IntegrationTo 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 itrepresents the basis for extrapolation if no meter reading results are available.

FeaturesTo 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 chooseContinue. 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 registersmetering pattern from the installation date, position the cursor on the relevant line and choose Maintain History. On this screen, period values and meter readingresults 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 overlapand 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 billingor 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 theexpected consumption for the forecast period is split into two subintervals. This may cause two period consumption values to be created for


Page 29 of 73

extrapolation and can lead to distortion when determining the expected consumption. This can lead to distortion when determining the expectedconsumption.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:

01. 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

01. 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 kWh * 50 = 125 kWh

01. 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 consumptionvalid from 15.12. (2500 kWh / year) is created. As the old period consumption no longer truly reflects the consumption patterns of the customer, theextrapolation results are also distorted.

1.2.9.5 Logical Register Number UseThe 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 registernumber if you replace devices using the replacement function instead of the separate installation and removal functions.IntegrationA technical removal ends the history of logical registers unless they are passed on to another device.PrerequisitesThe device must have undergone a technical installation and have registers.FeaturesThe 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 timeslice 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 copyingthe logical register number of another register. The logical register number is symbolized by a four-digit dummy number.ActivitiesDuring logical register number maintenance, you must enter meter readings for the relevant devices manually.

1.2.9.5.1 Changing Logical Register Numbers PrerequisitesThe 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

Choose Device installation Installation structure Logical register number ChangeYou branch to the initial screen.

Choose a device location or an installation.


Page 30 of 73

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 installedin the device location on the day before the key date is displayed on the left side of the screen.

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.Repeat this action for several time slices, if necessary.

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.3 Meter Reading PurposeThis component allows you to organize meter readings and meter reading results. Devices are either read periodically for periodic billing or aperiodically, such asfor 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 theMeter 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 eitherentered manually or uploaded. They are then validated and corrected, if necessary. The results are then forwarded to the Contract Billing (ISU-BI) component.

IntegrationThe following Business Application Programming Interfaces (BAPI) are available in the Business Object Repository (BOR) for selecting meter reading orders andresults:

MeterReadingDocument.GetList (select meter reading orders and results)MeterReadingDocument.Upload (upload meter reading results)

Further information on IDocs:For general information, see theBAPI User Guide and BAPI Programming

For more information, see the BAPI documentation in the BOR.

1.3

meter reading sap isu

Documents