My IS-U

SAP Utilities
The SAP Utilities (IS-U) component is a sales and information system that supports all business
processes and utility services of a utility company. You can use IS-U for managing and billing residential,
commercial and industrial, and prospective customers. This component also allows you to manage and
bill customers who receive services, purchase goods, or pay fees and taxes.
If you have any comments or suggestions regarding this documentation, we are always grateful for
feedback.
Integration
IS-U is integrated with the Service Management (PM-SMA), Customer Service (CS) and Sales and
Distribution (SD) application components, enabling you to bill service orders, service contracts, and the
sale of goods.
The Contract Accounts Receivable and Payable (FI-CA) component manages the large number of
postings from billing and budget billing requests.
IS-U uses the SAP Business Workflow (BC-BMIT-WFM) application component to automate business
processes. Common workflows include initial creation of a service connection and the disconnection of
devices.
Features
SAP Utilities
• IS-U/CCS
 With Basic Functions you manage addresses and regional structures, as well as
generating dates and schedules for meter readings, billings, and budget billings.
 With Master Data you manage data that remains fixed for long periods of time. In IS-U,
this data includes the business partners, contracts and contract accounts, connection
objects (buildings and real estate) and the premises, installations, and device locations
contained therein.
 With Device Management you manage the installations, meter reading, and the
certification of all devices for a utility company.
 The IS-U Billing component is used for billing the following standard divisions: Electricity,
gas, water/waste water, district heating, and multimedia services (for example, cable TV).
 The IS-U Invoicing component enables you to group services and invoice them on one
bill. You can also use the component to calculate and charge fees and taxes.
 In Kundenservice you can use the Customer Interaction Center (CIC) or Front
Office to display all data and start frequently used business processes. In Internet-Self-
Services your customers can send you new data or changes to their existing data via the
Internet. For example, they can grant you collection authorization or register a move-in.
• Energy Data Management (EDM) is a solution that meets the requirements of interval reading,
schedule management, and the billing of interval energy consumption. EDM covers the following
areas:
 Central database for energy data (Energy Data Repository)
 Settlement and schedule management using the settlement workbench
 Billing of profiles using real-time-pricing billing (RTP billing)
• Work Management combines various SAP components and enhances them to include industry-
specific functions for planning, calculating, executing, and billing work orders.
• SAP Waste and Recycling (IS-U-WA) is a comprehensive logistics, billing, service, and customer
service system that covers all the business processes required by a waste disposal company.
• Intercompany Data Exchange (IDE) is a solution that covers the requirements that have arisen
from the deregulation of energy markets. IDE covers the following areas:
 Management of deregulation data
 Process execution
 Management of data exchange processes
In August 2002, SAP launched the Efficiency Project IS-U/CCS. The idea was conceived of following a
number of projects, in which customers expressed the desire to improve the efficiency of certain IS-
U/CCS mass dialog processes (such as Find Business Partner, Identify Business Partner, Move-In,
Move-Out, Move-In/Out, Change Bank Details, Bill Correction). The documents referred to below all
contain information that you require in order quickly and efficiently implement the optimization measures
developed in this project. We strongly recommend that you implement these measures in your company
as they will significantly improve processing times.
You can find the documentation in the SAP Service Marketplace under http://service.sap.com/utilities →
Product Information → IS-U/CCS → General → Cookbooks&Guidelines:
• Documentation Increased Efficiency IS-U/CCS – Available Optimization Options
This document describes the optimization options that are available as of SAP IS-U/CCS Release
4.64. For example, we determined that we were not taking full advantage of the optimization
possibilities in processes such as move-in, move-out, and move-in/out, which are used very
regularly. This cookbook provides relevant information and stresses the importance of placing
particular value on efficient processes during all implementation projects.
• Documentation Increased Efficiency IS-U/CCS – New Developments
This document describes the new developments that SAP provided as an add-on support package
(AOSP) for SAP IS-U/CCS Release 4.64 in July 2003 and for SAP IS-U/CCS Release 4.71 in
September 2003 (new developments included Accelerated Move-In/Out, and express transactions
Change Bank Data, and Change Budget Billing Amount). As of IS-U/CCS Release 4.72, these new
developments are part of SAP Utilities.
Cross-Industry Solutions
In addition, you can make use of the following cross-industry solutions:
• SAP Business Information Warehouse for the utilities industry
You can find this documentation via the SAP HelpPortal (http://help.sap.com).
• SAP Customer Relationship Management for the utilities industry.
You can find this documentation in the SAP Solution Manager.
• SAP Enterprise Portals for the utilities industry.
You can find this information via the the iView Studio (www.iviewstudio.com).
Basic Functions
Purpose
This component contains the following basic functions of the Utilities Industry (IS-U) component:
• Central management of address data arranged according to postal and political regional structure
• Scheduling at the meter reading unit and portion levels
Regional Structure
Purpose
This component organizes a supply area on the basis of the following elements:
• Postal regional structure
This is essentially composed of cities and streets with their street sections. City districts and P.O.
boxes can also be represented. You can store a postal code for each object.
• Political regional structure
Unlike the postal regional structure, you can define the political regional structure yourself.
The political regional structure is linked via the postal regional structure to the addresses of the
connection objects. This means that the elements of the political regional structure stored in the
system correspond to elements of the postal regional structure (cities, streets and street
sections).
Integration
The regional structure uses the standard component Address Management (CA-GTF-ADR) component to
check and allocate addresses. For more information, see Customizing (Cross Application Components →
General Application Functions→ Address Management).
Features
The central file for city and street names and the allocated postal codes in the postal regional structure
ensure that the addresses are correctly spelled and structured. Country-specific algorithms also exist to
simplify the address entry process. To specify an address in the Netherlands for example, you only have
to enter the postal code and house number. In Germany, the postal code can often be determined directly
from the city name.
The following enhancements have been made to the regional structure:
• SZRS0001 (city) and SZRS0002 (street)
When creating a city or street, you can check whether that particular city or street already exists
in the system. You can also store your own check logic.
• SZRS0003 (address check-interface with external service providers)
When you maintain addresses, you can perform additional checks. You can also store your own
check logic. This enhancement is also intended for calling external providers' tools
• EE020001 (IS-U data determination from address)
This enhancement enables you to determine address data that you created maintained yourself
in the regional structure.
Postal Regional Structure

Use
The postal regional structure enables you to do the following:
• Manage postal codes, cities and streets.
• Check the accuracy of postal codes, cities and streets.
• Simplify the process of entering postal codes, cities and streets.
When you create objects that refer directly or indirectly to an address, some fields may already
contain default values (as in the connection object). In other cases, such as in the installation, you
must have the system propose a value.
Prerequisites
You must have set the City file active indicator in Customizing for each country. To do this, choose Global
Settings → Set Countries → Set Country-Specific Checks. This ensures that the system checks the
address data,
Features
For cities and streets you can:
• Enter billing-relevant data, such as temperature area, calorific value area, air pressure area and
meter reading units
When you create utility installations that are to be billed, the data is then proposed automatically.
• Define customer fields
This is done in Customizing. Choose SAP Utilities → Tools → System Modifications → Customer-
Specific Fields → Define Customer-Specific Fields in City and Street.
When you enter an address, the system determines the following:
• The city, city district and street are spelled correctly
• The city, street and (if applicable) postal code have been entered
• The city district corresponds to the city, the street corresponds to the city, and the city district
corresponds to the street
• The postal code exists (including the postal code for the P. O. box)
• The postal code has been cleared for deliveries/PO boxes
• The postal code exists in the city.
If a postal code has been maintained in the street section then the postal code
corresponds to the postal street section. If a postal code has been maintained in the city
district then the postal code corresponds to the city district.
If you enter an incomplete address the system determines the missing information. However, you must
have specified a country. You can enter an address in one of the following ways:
• By postal code only. The system determines the city and street, provided that there is only one
city and street for that postal code. If there is more than one possibility, a dialog box appears in
which you can select the address you want.
• By city, street and house number. The system then determines the postal code and the city
district.
• The region is determined from the other entries.
In the Street and City fields, you can use the search help to enter data in several address fields at once.
For example, the search help for the street also provides the city, country and region..
Postal Code
Definition
Code allocated to an address to simplify postal delivery. The national postal authorities control the
assignment of postal codes.
Use
A postal code can be used in different ways (for example, as a delivery postal code or P. O. box). The
postal code is only unique if you enter it in conjunction with a country.
Integration
If you set the City file active indicator for each country in Customizing, the system determines whether the
postal code you enter exists and whether its intended use is permitted. To set this indicator, you choose
Global Settings → Set countries → Set country-specific checks.
City
Definition
Town or municipality as defined in the postal regional structure. This does not necessarily have to
correspond to the political regional structure.
Use
In the city you can store data such as the region and the transport zone, and also application-specific and
customer-defined data. This data is accessible to the programs of data objects that have an address.
From the city you can branch to the following sub-objects:
1. Postal codes
These are the postal codes permitted in the city.
2. City districts
You assign the number of the city district yourself. If the postal code in the city district is unique,
you can enter it here. However, this is only possible if you entered the postal code in the city first.
3. P. O. boxes
Here you allocate P. O. box numbers to postal codes. However, this is only possible if you
entered the postal code in the city first.
Structure
The key of a city consists of the city number and the country. This ensures that the key is also unique if
cities are created for different countries by means of data carriers with external number assignment.
You can enter the city name and the short description according to language. In this way the special
situation in areas with multiple languages is taken into account.
Integration
If you set the City file active indicator in Customizing for each country, the system determines whether the
city that you enter exists. To set this indicator, you choose Global Settings → Set Countries → Set
Country-Specific Checks.
From the postal code entry screen, you can switch to the postal code creation screen.
Street
Definition
Road surface together with the surrounding buildings.
Use
In the street, you can store regional structure data such as the city district and regional structure grouping,
as well as application-specific and customer-defined data. Data objects for which an address has been
maintained can then access this data in the programs.
Data that is stored in the street or in the street section overrides data stored in the city.
Different streets with the same name are created in the system as different streets. A street that runs
through several cities must be stored in the system as several streets.
Structure
The key of a street consists of the street number and the country. This ensures that the key is also
unique if the streets are created for different countries by importing data carriers with external number
assignment.
The street name and the short description are language-dependent. This allows for the special situation
in multi-lingual areas.
In the street you can branch to the sub-object postal street sections. Here you can store data such as the
allocation of house number ranges to postal codes and city districts. This data overrides the data stored in
the street or in the city.
You can only maintain postal codes if the Street postcode indicator (street-specific postal
code) is set in Customizing for each country. To do this, choose Global Settings → Set
Countries → Set Country-Specific Checks.
Integration
When you enter a street, the system determines whether it exists and whether it is permissible in a city,
provided that the following settings have been established for each country:
• The City file active indicator is set in Customizing. To do this, choose Global Settings → Set
Countries → Set Country-Specific Checks.
The Street direct. indicator (street directory) is set in the city.
Maintaining the Political Regional Structure

Procedure
1. Maintain the hierarchy of the political regional structure.
2. Maintain the elements of the political regional structure.
3. Enter the links to the political regional structure in the postal regional structure (that is, in the cities and
in the streets).
Maintaining the Hierarchy

Prerequisites
A hierarchy does not yet exist. However, if you wish to change an existing hierarchy, the basic procedure
described below also applies.
Procedure
1. Choose Utilities industry → Regional structure → Political → Maintain hierarchy.
The system takes you to the initial screen Maintain political regional hierarchy structure.
2. Enter the country and the language. Choose Continue.
The system takes you to the initial screen Maintain political regional hierarchy structure. Only the
top level of the hierarchy is already displayed. This does not yet have a description.
3. Place the cursor on this line and choose Hierarchy→Change.
A dialog box appears. Enter the description and use of this hierarchy level. Choose Continue.
The system takes you to the initial screen Maintain political regional hierarchy structure. The
description of the top hierarchy level is now displayed.
4. Choose Create.
A dialog box appears. Here you create a new hierarchy level that is directly below the upper most
level.
Enter the data and choose Continue.
Your two entries are now included in the hierarchy display.
5. Create the remaining hierarchy levels you require, following the same procedure as for step 4.
Each new level you create is inserted directly below the level on which you have placed the
cursor. You can also create parallel hierarchy levels by placing the cursor on the same level
choosing Hierarchy→ Create.
6. If you would like two parallel branches to have the same sub-branch, you only need to create one
sub-branch.
Example
In this instance, maintain the hierarchy as described until c. If you now create a level directly
below level c and use the same description for this new level as for d, then the system creates a
"reference". An exclamation mark in a yellow circle appears on the new line, and no further levels
can be attached to this line. However, any levels below the upper level d (in this case level e) are
also inserted below the lower level d.
7. Save the hierarchy of the political regional structure.
Result
The political regional structure hierarchy is displayed as an overview tree.
Maintaining Elements
Prerequisites
The hierarchy for the political regional structure exists, but you have not yet created any elements.
Procedure
1. Choose Utilities industry → Regional structure → Political → Maintain elements.
The Maintain political regional hierarchy structure screen appears.
2. Enter the country and the language. Choose Continue.
The screen where you maintain the political regional structure appears. If you wish, you can
display the hierarchy of the political regional structure in a dialog box by choosing Utilities →
Hierarchy display.
3. Place the cursor on the Political regional structure line and choose Political regional structure →
Create.
A dialog box appears. Enter the description(s) for one or more elements of the top hierarchy level.
Choose Continue.
You return to the Maintain political regional hierarchy structure screen. At the end of each line, an
empty field is displayed. Once you have saved (and exited the screen and returned to it), the keys
of the elements of the political regional structure appear in these fields.
4. Place the cursor on one of the new elements and choose Political regional structure → Create.
A dialog box appears. In the top half of the dialog box, enter the descriptions of elements that are
situated directly below the element you selected in the hierarchy. In the bottom half of the dialog
box, enter elements that are situated on the same hierarchy level as the element you selected.
Choose Continue.
The new elements are now displayed on the overview screen.
5. Repeat step 4 until you have created all the elements you require.
6. Save the elements of the political regional structure.
Result
The political regional structure is displayed as an overview tree.
Portioning and Scheduling

Purpose
You use this component to generate dates for meter reading, billing, and budget billing plans. To generate
these dates you must first create the following schedule master records:
• Portions for billing
• Meter reading units for meter reading
Portions combine contracts that are to be billed together. You allocate a contract to a portion either
directly in the contract, or indirectly via the meter reading units that are specified in the installation
associated with that contract.
Meter reading units group together installations according to regional criteria. They contain all the data
relevant to the scheduling of the meter reading. You can only create meter reading units if a portion
already exists.
Breakdown of a Service Territory into Portions and Meter Reading Units
To create budget billing dates, you must maintain the parameter record as well as the portion. The
parameter record contains data for the creation of partial bills or for budget billing request printouts. One
parameter record can be valid for several portions.
Scheduled Dates for Billing, Budget Billing and Meter Reading
Schedule Master Records
Use
Schedule records are generated on the basis of the schedule master records.
Schedule master records are made up of the following objects:
• Parameter record
• Portion
• Meter reading unit
Parameter Record
Definition
The parameter record contains control data for budget billing. You use this control
data to generate due dates for the budget billing amounts when you create the
portion schedule records.
Use
You need a parameter record to create a portion.
You must enter the parameter record in the portion. Select the Where Used List in
the display or change mode to display all portions that use a particular parameter
record.
Integration
You only create the parameter record in order to generate the due dates for the
budget billing amounts.
The following functions are possible:
• Create parameter record

• Change parameter record
• Delete parameter records
You can only delete a parameter record if it is not used in a portion.
Portion
Definition
The portion groups utility contracts according to regional and organizational criteria
for billing purposes.
Use
You use the portion to:
• Group contracts for billing purposes according to regional criteria

You usually allocate contracts to a portion indirectly by allocating that portion to a meter reading
unit. You store the meter reading unit in the installation. A single contract is allocated to an
installation.
However, you can also enter a portion directly in the contract as an alternative portion.
This overrides the indirect allocation.
• Provide the scheduled billing dates
• Determine the due dates for the budget billing amounts
The budget billing period and the billing period must be the same length.
You use the period length of the portion, which you specify in months or days, to define how
often the contract is billed as well as the budget billing period. The number of billing runs refers
to one year for the month portion. The day portion, however, can be larger than one year. If the
day portion is larger than a year, the end is equal to the defined number of days.
• Activate dynamic scheduling
This enables you to modify schedule records in accordance with the factory calendar and a
specified number of workdays. To activate dynamic scheduling, you must specify the relevant
settings in Customizing under Utilities Industry → Basic Functions → Portioning and Scheduling
→ Dynamic Scheduling → Define Control Parameters for Dynamic Scheduling.
The system generates the due dates for the budget billing amounts using the data
in the parameter record and the date of the end of the billing period.
Integration
The portion is connected to the parameter record (which contains the budget billing
data) and to the meter reading units. The system uses the base dates of the portion
as base dates for periodic meter reading.
• Create portion
• Change portion
• Delete portion
You can only delete a portion if it is not used in a meter reading unit.
If schedule records still exist for the portion, you must delete these before you can delete the
portion.
If you are using the portion as an alternative portion in a contract, you must delete this
reference before you delete the portion.
• Alternative portion contract
An alternative portion in a contract groups together installations that have a different meter
reading unit. These installations are then billed together. In order for this to happen, billing and
invoicing must be executed with the alternative portion as the selection criteria.
For further information, see note 630244.
Meter Reading Unit

Definition
A meter reading unit groups together installations (and the devices and registers
installed in them) according to regional criteria for meter reading purposes.
Use
You use the meter reading unit to:
1. Group installations for meter reading purposes according to regional criteria

To allocate an installation to a particular meter reading unit, you enter that meter reading unit in
the installation. You cannot overwrite this allocation.
2. Provide the scheduled meter reading dates
3. Define the street route
SAP recommends that you do not group more than 1000 registers in a meter unit. This due
to the following reasons:
1. The meter reading unit is a worklist for a meter reader. This
means that a meter reading unit is designed to be the number of
registers that a meter reader can read in one day.
2. Performance
Meter reading units are required for creating and outputting
meter reading orders as well as for the fast entry of meter
reading results. The system reads all meter reading orders for a
meter reading unit on a scheduled meter reading date. A large
meter reading unit (that is, a unit that contains a large number
of installations and corresponding devices and registers) puts a
greater strain on the system performance.
Structure
On the maintenance screen of the meter reading unit the fields are divided into two
groups:
1. Fields for organizational data

Here you can allocate other meter reading units to a main meter reading unit, for example.
Meter reading orders and meter readings are created and executed for these meter reading
units in conjunction with the main meter reading unit.
2. Fields for scheduling data
Here you can maintain the scheduled meter readings for one year. Note that the system
proposes dates from the portion as the dates for periodic meter reading. You must not change
these dates. The system determines the length of the billing period in the portion. It uses this to
derive the number of schedule records for periodic meter reading.
Integration
When you allocate a meter reading unit to an installation, the system proposes the
meter reading unit associated with the address from the regional structure. This
proposal is based on the object address, the premise and the combination of billing
class and division category.
3. Create meter reading unit

4. Change meter reading unit
When you change a meter reading unit, you must regenerate the existing schedule records.
This is not possible for dynamic schedule records. You can use the standard transaction to
change dynamic meter reading units. You must then use the dynamic scheduling transaction to
regenerate the existing schedule records.
1. Delete meter reading unit
You can only delete a meter reading unit if this is not used in an installation and schedule
records do not exist.
Schedule Records
Definition
Schedule records contain the dates generated periodically for meter reading and
billing. In dynamic scheduling the meter reading dates for the registers to be read
are split evenly over the workdays of a month.
Use
When a portion and meter reading units are created, these schedule records can be
used to generate schedule records for the following year. The base dates of the
master schedule records are used to generate the appropriate periodic schedule
records. Once you have entered the necessary budget billing data in the portion,
budget billing dates are also generated for the portion.
The dates of the generated schedule records are used to schedule the meter
reading for the next period (years, months). The scheduled meter reading date for
the schedule records is the date when extrapolation for consumption during the
next period expires. Similarly, the data of the schedule records for billing (that is,
the gas date and allocation date) is used for scheduling billing and for the statistical
allocation of billings.
Schedule records can be created in advance for a period that you define. You should
create schedule records for at least one year in advance. This because a
predecessor is always required, for example, for post processing a move-in or a
move-out.
Generating schedule records from 03/01/03 to 12/31/03

If the customer wants to execute an action for the schedule record in March, he or she will
not be successful because they cannot access the schedule record for February. Schedule
records were generated starting from 03/01/03. This means that there is no previous record
available.
Schedule Record for a Portion
The schedule records of the portion are used for scheduling billing and allocating
budget billing due dates to the portion schedule records.
The budget billing period is directly linked to the end of the billing period.
The following dates for the schedule records are transferred into the billing order:
• Scheduled billing date
• Billing procedure
• Scheduled meter reading date
You cannot change meter reading schedule records for which meter reading order
creation has already been executed.
Period Key
The period key enables you to create a text for each budget billing cycle in each
budget billing period. If you want to allocate a period key to all schedule records of
a portion, you must first of all create a single schedule record (transactions EA43,
E43A). You must then adjust this manually (transaction: Change Schedule Record;
E40B). In the change mode, you can use the budget billing dates to allocate an
individual period key to every date within every budget billing cycle.
You can then generate other schedule records after this change (transactions EA43,
E43A).
You cannot regenerate a schedule record that you created with a period key.
Schedule Records for a Meter Reading Unit.
The schedule records for the meter reading unit regulate the due meter readings.
This includes creating meter reading orders, meter reading announcements, and
customer meter reading orders, and printing or downloading meter reading orders.
The following dates for the schedule records are transferred into the meter reading
order:
• Scheduled meter reading date
• Scheduled meter reading category
• Allocation date
• Gas date
Integration
You must create schedule master records for the portion and meter reading unit
before you can generate the schedule records.
• Create the schedule record

o Portion or meter reading unit
You use this function if you want to generate individual schedule
records for a specific period.
o Portion and/or meter reading unit
You use this function if you wish to generate several schedule
records for a specific period.
o All meter reading units of a portion
You use this function if you wish to generate schedule records for
all the meter reading units allocated to the portion you enter.
• Change schedule record
• Display schedule record
• Delete schedule record
o Schedule record for a portion
You can only delete schedule records that do not have any billing
orders. You must reverse the billing order before you can delete the
schedule records.
If the schedule records are not used in a billing order, you can
check whether the schedule records to be deleted were already
used in billing documents. This check can cause long runtimes
because the billing documents have to be analyzed.
SAP recommends that you only execute this check in a productive system as an exception.
o Schedule record for a meter reading unit
You can only delete schedule records that do not have any meter
reading results or meter reading orders.
• Analyze schedule records
Dynamic Schedule Records
To generate dynamic scheduling, you must define entries in Customizing under
Utilities Industry → Basic Functions → Portioning and Scheduling → Dynamic
Scheduling → Define Control Parameters for Dynamic Scheduling. The fields for
dynamic scheduling in the portion are now ready for input. Dynamic schedule
records are only generated if you have selected the field Dynamic Scheduling in the
portion. Dynamic schedule records can only be generated or changed using special
transactions.
Scheduling
Purpose
Scheduling groups the sub-division of the service territory into portions (billing
units) and meter reading units in the system, and generates dates for the following
functions:
• Meter reading
• Billing
• Creation of budget billing amounts
Prerequisites
The service territory of your utility company must be divided into portions and
meter reading units.
Process Flow
Scheduling comprises the following stages:
1. ...
1. 1. Create parameter record
In the parameter record you store the control data for generating the due dates for the budget
billing amounts. You need a parameter record to create a portion.
2. 2. Create portion
The portion groups utility contracts according to regional and organizational criteria for billing
purposes. You can group contracts according to their billing class and division category.
You use the period length of the portion, which you specify in months or days, to define the
number of times the contract is to be billed and the budget billing period. You use the date of
the end of the billing period, to define when the billing period occurs within the year and the
base date of the portion. You are always required to specify a parameter record. The system
generates the due dates for the budget billing amounts using the data in the parameter record
and the date of the end of the billing period.
3. 3. Create meter reading unit
The meter reading unit is an organizational unit which groups utility installations for meter
reading purposes. The number of installations you allocate to a meter reading unit might, for
example, correspond to the number of installations to be read by the meter reader in one day.
You allocate an installation to a meter reading unit by entering the meter reading unit in the
installation. You base this allocation primarily on regional criteria. You can restrict the
allocation of a meter reading unit to an installation by maintaining the combination of billing
class and division category.
You allocate a portion to a particular meter reading unit by entering the it in that meter
reading unit. This enables you to specify the number of contracts to be billed, that is, the
number of installations for which meter readings have been taken.
In the meter reading unit you define the base dates for meter reading for one year. You can
predefine base dates with different meter reading reasons, such as periodic meter reading,
service territory transfer with billing, interim meter reading without billing, or control reading.
The basic data for periodic meter reading (the end of the meter reading period and the
number of periodic meter readings) is copied directly from the portion. If, for example, the
length of the billing period is six months, two periodic meter reading dates are set. You can
specify the dates for the other meter reading reasons within the annual period. You can select
the planned meter reading category (for example, interim meter reading, meter reading by the
customer). However, you should take organizational criteria into account.
4. 4. Generate schedule records
Once the schedule master records of the portion and of the meter reading units have been
defined, the system can use these master records to generate schedule records for the next
few years. In this process, the appropriate periodic schedule records are generated from the
base dates of the master records. The budget billing dates are also generated for the portion.
The dates of the generated schedule records are used to schedule the meter reading for the
next period (years, months). The scheduled meter reading date for the schedule records is
the date when extrapolation for consumption during the next period expires. Similarly, the
data of the schedule records for billing (that is, the gas date and allocation date) is used for
scheduling billing and for the statistical allocation of billings.
Result
After scheduling, portions, meter reading units and their corresponding schedule
records are available.
Create Parameter Record
Procedure
1. ...
1. 1. When you create the parameter record, you can transfer existing
values from another parameter record and use these as a template.
Every parameter record can contain up to 5 budget billing cycles. You can select the following
values:
o 00: No budget billing amounts are levied
o 01: Budget billing amounts are levied every month
o 02: Budget billing amounts are levied every 2 months
o 12: Annual payer; one budget billing amount is levied.
2 When you define a budget billing cycle, you must enter the budget billing cycle as well as the
scheduled print date of the budget billing request or the creation of the partial bill in the BB
req./part. bill field.
3 In the field Months inv.-1st BB, you define the time between the end of the last billing period and
point when the first budget billing amount is levied.
4 If you want to use the parameter record to create portions with a duration of days, you can enter
the number of days after the start of this period that you want the first budget billing item to be
calculated in the field Days to Bud. Bill. The system uses this number of days to calculate the
other budget billing items.
A parameter record is always necessary even if you do not want to levy a budget billing
amount.
You must therefore create at least one parameter record.
Create Portion
Procedure
1. ...
1. When you create a portion, you can transfer existing values from another
portion and use these as a template.
2. Dynamic Scheduling
When you create a portion, you must decide whether you want the portion and the corresponding
meter reading units to be used for dynamic scheduling. Set this indicator if you want the portion to
be used for dynamic scheduling.
3. End Bill. Per. (End of Billing Period)
Here you can determine the date when the portion is billed for the first time. This date is used as
the base date for calculating the end of the billing periods or floating backbilling periods.
This date cannot come before the end of the meter reading period or the scheduled meter
reading date of all allocated meter reading units.
4. All Date Billg (Billing Allocation Date)
This date enables you to statistically allocate billing. It is used during cross-contract billing to
allocate billing orders and documents. The date is also copied to the billing order.
This date cannot come after the end of the billing period. The end of the billing period cannot
come before the end of the meter reading period or the scheduled meter reading date of all
allocated meter reading units.
If you use budget billing procedure 3 (payment plan) in your system and a payment plan has
already been created for this portion, you can no longer change the allocation date.
5. Sch. Bill. Date (Scheduled Billing Date)
This date specifies the day the system starts billing contracts that belong to a portion. The factory
calendar is used for this.
This date displays the point in time when a billing period is prepared. Billing orders that have the
status billable after this date are not processed. The date, therefore, acts as the selection date for
determining billable billing orders during mass and single billing.
6. Inv. Print Date
Here, you can define the date for the scheduled bill printout
7. Gas Alloc. Date (Gas Allocation Date)
If you use thermal gas billing, you can use this date to allocate relevant data, such as calorific
value, temperature, gas law deviation factor).
8. Period Characteristics
You can enter the period length of the portion in days or months.
If you use months, you can choose the period lengths 1, 2, 3, 4, 6 and 12.
If you use days, you can enter any period (in days).
9. Calendar Settings
If you define a factory calendar, you can set the Correct Non-WD (correct non-working day)
indicator. If a date in a schedule record falls on a day that has been defined as a non-working day
in the factory calendar, this indicator ensures that the date is moved to a working day.
If you create a day portion, you can set the Include Factory Calendar indicator. If you also enter a
factory calendar in the Factory Calendar ID field, this ensures that the days you have defined are
only calculated in work days.
10.Intervals for Billing on a Monthly-Basis
When you create a period of a month, you can also define intervals that determine the billing
period:
1. If the period to be billed is within the interval you have entered, billing is executed to the
month.
2. If the period exceeds the interval, billing is executed to the day.
If you require more than one upper and lower limit for the intervals, you can use an enhanced
interval procedure. You can make the settings for this in Customizing under:
SAP Utilities àContract Billing à Billing Master Data à Rate Structure à
Rates à Period Control à Basic Calculation Procedures à Month-Based
Calculation Using Interval
11.BB/Bill Dates (Group Due Date of Budget Billing Items and Bill)
Here, you can define whether you want to group the due date together with the next budget billing
amount or with the next bill.
12.Cat. BB Extrap. (Type of Waste Disposal Extrapolation)
If a specific value has not been entered in the contract, the system uses the default value
selected in the meter reading unit. The values in the meter reading unit have the following effects:
1. 01 (automatically)
The values for the billing period are extrapolated using the following
logic (priority in descending order):
1.If the budget billing period contains billing-relevant changes to
the service frequency, the values are extrapolated based on the
expected services and the service frequency.
2.If there are billing-relevant values in the same period of the
previous year, these are used for extrapolation.
3.If there are billing-relevant values in the previous period, these
are used for extrapolation.
4.Values are extrapolated based on the expected services
(determined from the interval of the service frequency).
2. 02 (using service frequency)
Values are extrapolated based on the expected services (determined
from the interval of the service frequency).
1. 03 (using the previous period)
The billing-relevant values from the previous period are used for
extrapolation. If this is not possible, values are extrapolated based on
the expected services (determined from the interval of the service
frequency).
2. 04 (using the previous year’s period)
The billing-relevant values from the period of the previous year are
used for extrapolation. If this is not possible, the following takes place:
1.The billing-relevant values from the previous period are used for
extrapolation.
2.Values are extrapolated based on the expected services
(determined from the interval of the service frequency).
1. Dun Due Date (Dun the Last Due Date of a Budget Billing Plan)
This indicator is only used for the statistical budget billing plan procedure.
When it is set, the Cannot Be Dunned in BB Plan field is not set.
2. Define Budget Billing Cycles
When you select the budget billing cycle, you can specify the number of budget billing amounts
that are charged. If you want to levy budget billing amounts, at least one permitted budget billing
cycle must be set with the number of budget billing amounts.
3. Budget Billing Cycle
You can define a cycle in the portion as a standard cycle. You can only use budget billing cycles
that are defined in the allocated parameter record. If you do not levy budget billing amounts, no
data is saved in the budget billing data table TE423 (Budget Billing Dates) when the schedule
records of the portion are generated.
If you define more than one cycle, the entries for every cycle are saved in the table TE423.
4. Billing Class / Division Category
You can restrict how the portion is used by entering a billing class and a division category. You
have the following options for this:
1. Restricted portion
In the meter reading unit, you can only use the constellations of billing
class and division category that are entered in the portion. You can
also not make any restrictions.
2. Portion not restricted
The meter reading unit can be restricted or unrestricted.
Create Meter Reading Unit

Procedure
1. ...
1. 1. When you create the meter reading unit, you can transfer existing
values from another meter reading unit and use these as a template.
2. 2. Portion
You must enter a portion when you create a meter reading unit. You must have already created the
portion before you use it here. When you enter the portion, the system automatically determines
the periodic meter reading dates for a year.
The end of the meter reading period is copied from the portion and corresponds to the end of the
billing period date.
The scheduled billing date is copied from the portion and used as the meter reading allocation date.
The interval between the meter reading and the end of the meter reading period is determined from
the meter reading allocation date and the end of meter reading period. You can shift the meter
reading allocation date by changing the interval.
The end of a meter reading period cannot come after the end of the billing period of the
allocated portion.
An alternative portion entered in the contract overrides the portion in the meter reading unit.
3. 3. Dyn. Sched. (Dynamic Scheduling)
All meter reading units allocated to a portion with dynamic scheduling are also processed by
dynamic scheduling. You cannot set the dynamic scheduling indicator manually. The system sets
the indicator automatically if the portion entered is allocated to dynamic scheduling.
4. 4. Meter Reading Together with (Meter Reading Together with Leading
Meter Reading Unit)
The new meter reading unit can be read together with another meter reading unit. Make sure that
the meter reading periods of both meter reading units end at the same time. If you want the meter
reading unit to be read together with another meter reading unit, you must set the Main Meter
Reading Unit indicator in the meter reading unit that you enter in this field.
5. 5. Meter Reading Unit for Contracts that are Billed in Advance
Set this indicator if you want to use the meter reading unit for contracts that have to billed in
advance. The system executes advance billing during every periodic billing run.
6. 6. MDE Number (Number for Mobile Data Entry)
If you have an external system that can be used to download meter reading orders for mobile
data entry, you can enter an MDE number here. This number is transferred to the new meter
reading orders when they are created. The system executes a download for these selected meter
reading orders when the orders are output.
7. 7. Number of Previous Meter Reading Results
You can enter the number of previous meter reading results in this field. These are the meter
reading results from the periodic meter readings that were already entered in the system for the
corresponding register at the time the order was created and that should be printed on the bill. If
only a few previous meter reading results have been entered for the register, the system only
prints these.
8. 8. Key Date ( Key Date for Billing on a Monthly Basis)
This field is only used for periods defined as months. It is only important in the following cases:
If a corresponding access control for an operand has been selected for monthly billing in
connection with a key date
If a corresponding period control has been selected in a rate step for monthly billing in connection
with a key date
9. 9. MR Center (Meter Reading Center)
This field is a customer-specific field in the meter reading unit. It is used to group different meter
reading units into another logical unit. This unit can then be evaluated by a customer-specific
program.
10.10. Calendar Settings
When you define a factory calendar, you can also set the indicator that corrects non-working
days. If a date in a schedule record falls on a day that has been defined as a non-working day in
the factory calendar, this indicator ensures that the date is set to the previous non-working day.
11.11. Schedule Record Intervals in Days
When you create a meter reading unit, you can also maintain extra intervals:
Intervals
Field name Description

MR-end MR per. Interval between the meter reading
and the end of the meter reading
period:
Specifies the scheduled meter reading date of

the schedule records.
Order cr. - MR Interval between order creation and
the scheduled meter reading date:
Specifies the date when the meter

reading order is created.
Days Print – MR Interval between printing the meter
reading orders and the meter
reading:

reading orders are printed.
Download - MR Interval between download and
meter reading:
Specifies the download date.

Announce OC Interval between meter reading
announcement and order creation:
Specifies the date of the meter

reading announcement.
CMROP-order cr. Interval between printing an order for
a meter reading by a customer and
the order creation:

reading orders for a customer meter
reading are printed.
12.12. Include Factory Calendar
If you set the indicator for these fields, the days that you have entered are regarded as working
days.
If you do not set the indicator, the days that you have entered are regarded as calendar days.
The days between order creation and the meter reading are the upper limit for the download
intervals. They are also the upper limit between the printout of meter reading orders and the
meter reading.
13.13. Entry Interval
The entry interval defines a period before or after a utility company takes a meter reading. A
second meter reading can be interpolated in this period. This means that the utility company does
not have to take another meter reading.
The meter reading interval is a period in which only one meter reading and one billing run can be
executed. If a meter reading order or a meter reading result already exists in a meter reading
interval, the system suppresses the meter reading order that has the lowest priority meter reading
reason.
14.14. Meter reading dates
You have several different options for defining a meter reading date:
Meter reading dates
Field name Description

MRP end End of a meter reading period:
Used as the base date for

determining the dates of other meter
reading periods.
The date cannot come after the end of the
billing period for the allocated portion.
Alloc.Date Allocation date for the meter reading:
Used during the demand value

inclusion in billing. Allocates the
meter reading result to a certain
month.
You can also use the meter reading allocation
date to allocate the meter reading result to a
season.
MR reason Meter reading reason:
In addition to periodic meter reading,

you can also use the following meter
readings:
02: Interim meter reading with billing
05: Service territory transfer with billing
09: Interim meter reading without billing
10: Control reading
Sched. MRC Scheduled meter reading category:
Specifies the kind of meter reading to

be executed:
01: Meter reading by utility company
02: Meter reading by customer
03: Automatic estimation
04: Meter reading interpolated
Estim. in Bill Meter reading results are estimated
in billing:
If you set this indicator, you can only

use the meter reading unit in flat-rate
installations or dynamic period
control (DPC) installations.
The meter reading results are
estimated in billing by dynamic
period control.
Adjust BB Plan Adjust budget billing plan during
interim billing
Set this indicator if you want adjust

any existing budget billing plans
during interim billing. You can only
use this field for meter reading
reason 02 (interim meter reading
with billing).
15.15. Print Settings
You can enter printing forms in the meter reading unit. These forms are used in specific
transactions.
You can still restrict the meter reading unit even if you have not made restriction for the billing
class and division category in the portion entered. If you do make a restriction, it affects how the
meter reading unit is used in the installation.
If the portion does contain entries, you can either not use any of the restrictions, or only use the
variants specified in the portion.
16.16. Billing Class and Division Category
You can restrict how the meter reading unit is used by entering a billing class and a division
category. You have the following options for this:
o The portion has a restricted billing class and division category
In the meter reading unit, you can only use the constellations of
billing class and division category that are entered in the portion.
You also have the option of not making any restrictions.
o Portion is not restricted
The meter reading unit can be restricted or unrestricted.
17.17. Meter reader
You can enter meter reading-specific data for the meter reader, here. You can, for example, enter
the number of the meter reader who has to take a meter reading, or who has actually taken the
meter reading result.
18.18. MR by Customer (Meter Reading by Customer)
If you set this indicator, the system creates customer meter reading orders for the meter reading
unit.
If the customer does not confirm any meter reading results, new meter reading orders are
created. In this case, however, the new orders are generated for meter reading by utility
company.
19.19. MR Time (Hours) (Meter Reading Time in Hours)
You can allocate the required meter reading time in hours to a meter reading unit. You can
subtract this entry from the meter reader’s available time. This provides you with the remaining
time that can still be scheduled for the meter reader in question.
20.20. Subcontractor
If a subcontractor is taking the meter readings on behalf of your company, you can enter the
subcontractor's number in this field. The data entered here is used just as information.
Result
When the meter reading unit is saved, all meter reading data is saved in table
TE425 (meter reading dates). A data record is saved along with the accompanying
meter reading date for ever meter reading reason over the period of one year.
Generate Schedule Records

Procedure:
Generate Schedule Records for Portion
You can use the following transactions to generate schedule records:
• Create Schedule Record for Portion or Meter Reading Unit (transaction EA43)
• Create Schedule Record for Portion and/or Meter Reading Unit (transaction E43A)
You can only generate schedule records for a period that does not contain any
billing orders.
When schedule records are generated, billing-relevant data for every schedule
record is stored in the budget billing date table TE423. Budget billing data is saved
for every defined cycle depending on the period length.
If two cycles are defined in a portion, the dates for both cycles are saved in the
budget billing table, regardless of which cycle is entered as the default cycle in the
portion.
The TERMTDAT field in table TE423 is always the same as the end date of the portion’s
billing period.
If the dates are different, this normally means that the portion has been changed without
regenerating the schedule records.
Regenerate Schedule Records for Portion
You can use the following transactions to regenerate schedule records:
You can only regenerate schedule records that do not have any billing orders.
If you have changed a portion, you can regenerate the schedule records directly by
saving the portion. This is not possible for dynamic scheduling. In this case, you
must use transaction E1DY to regenerate the schedule records.
Generate Schedule Records for the Meter Reading Unit

You can use the following transactions to generate schedule records:
• Create Schedule Record for all Meter Reading Units of a Portion (transaction E43B)
Intervals defined in the meter reading unit are calculated using the end of the meter
reading period. They are then saved in the schedule record. However, the date for a
meter reading by a customer is not calculated using the interval up to the end of
the meter reading period. In this case, the system uses the defined interval minus
the order creation date. If meter reading orders or meter reading results exist for
the period of the schedule record to be generated, this schedule record cannot be
overwritten.
When schedule records are generated, any existing schedule records that do not
have any meter reading results or meter reading orders are overwritten.
Regenerate Schedule Records for a Meter Reading Unit

You can use the following transactions to regenerate schedule records:
• Create Schedule Record for all Meter Reading Units of a Portion (transaction E43B)
You can only regenerate schedule records that do not have any meter reading
results or meter reading orders.
• Master Data
• Purpose
• This component contains data for the Utilities Industry (IS-U) component that remains unchanged
over a long period of time. The graphic below illustrates the master data and shows how the
various objects are related to each other.
• Master Data in IS-U
•
•
• There are 2 different types of master data: technical and business. These are shown in the
graphic below:
• SAP Business Partner (SAP BP)

• Purpose
• The component SAP Business Partner enables you to create and manage
business partners centrally. This is of prime interest if a business partner plays
different roles for a company, such as sold-to party and ship-to party.
• SAP Business Partner is designed to utilize technical benefits such as data
integrity and freedom from data redundancy, and to place greater emphasis on
aspects relating to customer maintenance and acquisition of new customers.
• Features
• You can create a business partner in different business partner roles, and during
the course of the business relationship the business partner can assume other
business partner roles. No new data has to be created each time, meaning that
redundant data creation and retention is avoided, and there can be no
inconsistencies.
• By using SAP Business Partner, it is possible to merge the partner data already
held by a company in more than one system in such a way that the potential for
new contracts within the same customer contact can be identified.
• When you enter data, the central data related to SAP Business Partner, and the
application-specific data are integrated seamlessly on the processing screen.
• Seamless integration of customer-specific data is possible without modification,
ensuring full future maintenance, because defined interfaces exist for this
purpose.
BP Role Contract Partner

Definition
A contract partner is connected with the company through contract accounts and through the conclusion
of contracts. Contract accounts can therefore only be assigned to a business partner and services billed
accordingly if you have created this business partner in the role of contract partner.
Use
Since a contract partner receives services from the company and has to be billed for these services, you
also have to store control and payment data for the contract partner.
In addition to bank details, you can enter general data on the contract partner, such as the business
partner type and creditworthiness. Creditworthiness is determined and updated automatically, but you can
overwrite this.
A company must have the following information on a contract partner:
• Address: Name, form of address, academic title, name suffixes and prefixes, personal data, street
address, postbox address, communication methods
• Control/payment transactions: Bank details and general data (creditworthiness)
• Relationships: Relationships to other business partners (see Relationship Categories)

Data in the future
You do not have to activate business partner master data changes to have immediate effect; instead you
can enter a date from which the changes are effective. This data is not written to the database but
recorded in change documents.
To activate such data, you should start report BUSPCDACT daily if possible, as it writes the planning to
the database.
You can also make scheduled changes using direct input; however, you need the primary key to do this.
You can delete inconsistent data when you are in display mode for change documents.
Tax numbers for business partners
You can define any number of tax numbers. You assign these to tax number categories that control the
usage and check of tax numbers.
Checking dependencies of master data changes
If you delete the bank details of a business partner, but these are still used in a contract account, you
receive a corresponding message and can go to maintenance of the contract account to remove this
inconsistency. This check does not apply to scheduled master data changes.
Check digit for contract partners
When you create a contract partner, you can add a check digit to the contract partner number. The
prerequisites are as follows:
• You add the check digit procedure using event 1051. Sample function module
FKK_SAMPLE_1051_2_CHECKDIGITS for two check digits is supplied by SAP.
• The contract partner is created with internal number assignment.
• The number range is configured such that it begins with a leading zero (check digit procedure
with one check digit) or with two leading zeros (procedure with two check digits).
Utilities Industry (IS-U) component
In the Utilities industry component, you can define additional data for the contract partner, for example,
the following general data:
• Driving license number
• Social insurance number (USA)
• Employee classification
• Account category (as default value for contract account)
BP Role: Contract Partner (IS-U)

When you create a contract partner, you can also create a standard customer in the background in the
Sales and Distribution (SD) component. This standard customer may, for example,
• use services or maintenance services
• purchase goods
• pay charges and taxes
You can use a predefined standard customer as a reference and then change the data.
BP Roll Installer (IS-U)
Definition
An installer is a person licensed by a utilities company to carry out installation work.
Structure
With the BP role installer you can enter general data and status management in
addition to the usual address data. In the general data you can define data such as
the license for certain divisions, operating purpose of the company and the
identification number of the license. In the status management you can define data
such as the type of license and the date of the initial license.
Changes to Payment Data

Use
Changing bank data and payment card details in the master record of a business
partner.
Integration
You can change payment data in the master record of the business partner and in
dependent objects simultaneously. For example, you can change the bank details of
a customer who changes from a cash payer to a direct debit payer in his business
partner master record and his contract account.
Features
In the transaction Maintain Bank Data (FPP4), you can do the following centrally for
a business partner:
• Create new bank/payment card details

• Change existing bank/payment card details
• Delete existing bank/payment card details in the contract account and subsequently in the
business partner master record
• Create customer contacts
• Print confirmation letters
You can also control follow-up actions, such as reversing dunning notices, by means
of flexible rules.
The processing takes place in three steps:
Mode Function Call via Button

Create Create New Bank/Payment
Card Details with quick info Create
Change Change Existing
Bank/Payment Card Details with quick info Change
Delete Delete Existing Bank/Payment
Card Details with quick info Delete
Activities
Make the system settings required in the Implementation Guide for Contract
Accounts Receivable and Payable under Basic Functions → Contract Partner →
Changes to Payment Transactions. If you set the indicator Create Bank ID in the
client-specific settings in Customizing, in event 1053, you can determine a new
bank details ID for a business partner. If you set the indicator Create Credit Card ID,
in event 1054, you can determine a payment card ID for a business partner. As
standard, the first ID for the bank/payment card details is created with 0001, the
second with 0002. If no ID is determined here, the system prompts the user to enter
a new ID in a dialog box (see function module FKK_EVENT_1053_DIAL).
With a function module processed in event 1083, you can make further changes to
the contract account when you save the data. In this event, you can, for example,
define that the field Posting Control Group changes in the contract account if a
customer changes from being a cash payer to a direct debit payer.
You define the event modules specified under Program Enhancements → Define
Customer Specific Function Modules. See also the documentation for the sample
function modules FKK_SAMPLE_1053, FKK_SAMPLE_1054, and FKK_SAMPLE_1083.
If you want to send confirmations, define the form required for the correspondence
types 0036 and 0040. To define a standard form proceed as follows:
1. 1. In the Implementation Guide for Contract Accounts Receivable and

Payable, choose Basic Functions → Correspondence → Define Standard
Form Classes for Correspondence and define the form class
FI_CA_BANK_MAINTAIN for correspondence type 0036, and form class
FI_CA_CCARD_MAINTAIN for correspondence type 0040.
2. 2. Create a copy of the standard form FI_CA_BANK_MAINTAIN_SAMPLE
or FI_CA_CCARD_MAINTAIN_SAMPLE and adjust it accordingly.
3. 3. In the Implementation Guide for Contract Accounts Receivable and
Payable, choose Basic Functions → Correspondence → Define Application
Forms for Correspondence and enter the new forms for the
correspondence types 0036 and 0040.
Changing Payment Data
Prerequisites
You have the authorizations to change bank and payment card data. If the existing
authorizations are insufficient, the system terminates processing.
When you display the contract accounts, only those contract accounts for which you
have display authorization appear. You can only select contract accounts for which
you have change authorization. If you do not have the relevant authorizations, the
system issues an error message for every action that it could not carry out.
Procedure
1. ...
1. 1. From the SAP menu, choose Master Data → Business Partner →

Maintain Bank Data.
2. 2. Enter the business partner required and, in the field Valid From, the
date from which the change to the bank/payment card data is to be valid.
3. 3. Confirm your entries.
4. 4. Make the desired changes and save your entries.
The system selects the program mode automatically. If there are no bank details for
the business partner entered, the system selects the mode Create. In all other
cases, the system selects the mode Change. In the Implementation Guide for
Contract Accounts Receivable and Payable, under Basic Functions → Contract
Partner → Changes to Payment Transactions → Define Processing Variants, you can
prevent the system selecting the mode automatically for a processing variant by
setting the indicator No Automatic Mode in the area Control. In the field Transaction
Mode, you can also define which object the transaction is to start with. You can
override this setting during processing via the menu functions Goto → Change Bank
Data, or Goto → Change Payment Card Data. Via the parameter 8UV, you can define
the processing variant required in the user data.
With the button with the quick info Other Partner, you can switch to a different
business partner in the maintenance of the bank data. If you select with the
quick info Back in the standard toolbar, you can also select a different business
partner or change the validity date for the business partner entered and start the
processing again.
By selecting the corresponding button in the toolbar, you can change the mode.
Bank Details Area

If bank details already exist for the business partner, these appear in the field
Existing Bank Details. You can select the bank details required from the drop-down
list, or determine the details with the button with the quick info Search.
Under New Bank Details, enter the new bank details and with the corresponding
selection buttons, define whether these bank details are to apply only as payment
method for incoming payments, only for outgoing payments, or for both.
Contract Accounts Area
The following contract accounts appear here:
• Contract accounts where the business partner selected is entered as the contract account holder.
• Contract accounts where the business partner selected is entered as the alternative payer.
• Contract accounts where the business partner selected is entered as the alternative payee.
• Contract accounts where the business partner selected is entered as the payer.
If you enter a different date to the current date in the field Valid From, the system
selects the contract accounts valid from this date. If, for example, the business partner is not
the contract account holder, and only the alternative payer, alternative payee, or payer for
the contract account from a date in the future, for technical reasons, the contract account
may not be selected under certain circumstances if you call the transaction before this future
date. The system only selects the contract account when you call the transaction on the date
when the change takes effect and the business partner is, for example, the alternative
payer.
If you select a line in the list, when you save, the system only makes the change for
the contract account selected. The defaults set by the system automatically and
listed below also apply.
Automatic Selection of Contract Accounts in the List
Mode Automatic Selection

Create If the business partner has no bank details, the system selects all
contract accounts. If the business partner has bank details, the
system does not select any contract account.
Change The system selects all contract accounts that contain the bank
details selected. You cannot change this selection.
Delete The system selects all contract accounts that contain the bank
details selected. You cannot select any other contract accounts
for changes.
Correspondence/Contact Area
Here you can create a customer contact. If you set the indicator Print Confirmation,
a confirmation is printed when you save.
Special Cases
Special Case 1: Alternative Payer/Payee
If the contract account contains an alternative payer/payee, the payment details
entered in the contract account belong to this alternative payer/payee.
If you want to change the payment details of the contract account holder, this must
not have any influence on the payment details of the alternative payer/payee.
Contract accounts with alternative payers/payees appear in the list in the column
Alt.Payer/Payee with the icon with the quick info Alt. Payer/Payee if, for the
changes you want to carry out, you have selected a transfer type that would change
the payment details for the alternative payer/payee. You can see the business
partner number of the alternative payer/payee in the columns Alternative Payer and
Alternative Payee.
The contract account contains an alternative payer and you have selected the transfer
type Incoming Payments. The icon with the quick info Alt. Payer/Payee appears.
The contract account contains an alternative payee and you have selected the transfer type
Incoming Payments. The icon with the quick info Alt. Payer/Payee does not appear.
Which accounts can you select?
Whether you can select a contract account with this icon in the list for changes
depends on the transfer type you have selected and the existing data in the
contract account.
• Case 1
You have selected the transfer type Incoming and Outgoing Payments. The contract account
contains an alternative payer, but no alternative payee. In this case, you can define the bank details
of the contract account holder as the bank details for outgoing payments and therefore select the
contract account for the change.
• Case 2
You have selected the transfer type Incoming Payments. The contract account contains an
alternative payer. In this case, you cannot initially select the contract account for changes.
However, if the contract account holder wants to be the payer for his contract account, you can
click on the icon with the quick info Alt. Payer/Payee to switch to the maintenance for the
contract account and delete the alternative payer there. Once you have saved the contract account,
you can select it for the change in the list.
How does the system behave when you save the changed contract
account?
There are different cases depending on the option selected:

• Case 1
You have selected the transfer type Incoming and Outgoing Payments. There is an alternative
payer, but no alternative payee.
 You save without carrying out any actions.
The bank details entered are only stored in the master record of the contract account holder.
 You select the contract account and save.
The bank details are only defined as the bank details for outgoing payments.
 You delete the alternative payer in the contract account, select the contract account, and
save.
The bank details are defined as the bank details for incoming and outgoing payments.
• Case 2
You have selected the transfer type Incoming Payments. There is an alternative payer, but no
alternative payee.
 You save without carrying out any actions.
The system only saves the bank details entered in the master record of the contract account
holder.
 You delete the alternative payer in the contract account, select the contract account, and
save.
The bank details are only defined as the bank details for incoming payments.
Special Case 2: Alternative Payment Details

In the following cases, the icon with the quick info Alternative Payment Details
Exist appears in the column Alternative Payment Details.
• Case 1
The contract account contains different payment details to those you have selected.
The contract account contains the bank details ID for incoming payments 001, but in the drop-
down list, you have selected the bank details ID 002. The transfer type Incoming Payments is
selected.
• Case 2
You have selected the transfer type Incoming and Outgoing Payments. The existing payment
details are different.
The contract account contains the bank details ID 001 for incoming payments, and the bank
details ID 002 for outgoing payments.
The system treats a contract account with alternative payment details as follows:
 To prevent you changing the contract account in error, the system does not select it.
However, you can select the contract account for changes.
 Via the icon with the quick info Alternative Payment Details Exist, you can switch to the
maintenance for the contract account and make any changes required.
Special Case 3: Business Partner Is Payer/Payee

If the business partner entered is not the holder of the contract account, but is
entered as alternative payer/payee in the contract account, the icon with the
quick info <Business Partner Number> Is Alternative Payer appears in the column
BP Is Payer/Payee. The following is valid for the maintenance:
• If the bank details selected are used in the contract account, the system selects this contract
account. You cannot change this selection.
• If other bank details are used in the contract account, the system does not select the contract
account; however, you can select it manually.
• If the business partner no longer wants to be the alternative payer/payee for this contract account,
you can switch to the full screen maintenance of the contract account via the icon with the quick
info <Business Partner Number> Is Alternative Payer and remove the business partner from the
field Alternative Payer or Alternative Payee.
Special Case 4: Business Partner Is Payer

If the business partner entered is not the holder of the contract account, but is
entered as payer in the contract account, the icon with the quick info Paid by
<Business Partner Number> appears in the column BP Is Payer. The contract
account is only displayed for information purposes and you cannot select it.
If the business partner no longer wants to be the payer for this contract account, via
the icon with the quick info Paid by <Business Partner Number>, you can switch
to the maintenance for the contract account and remove the business partner from
the field Payer and remove the contract account from the field Paid By.
BAPIs for Central Business Partner (CBP) (IS-U)

Use
The Business Object Repository (BOR) contains the following Business Application Programming
Interfaces (BAPIs) for business partners:
• UtilBusinessPartner.CreateFromData (creating a Business Partner)
• UtilBusinessPartner.Change (changing a business partner)
• UtilBusinessPartner.GetDetail (displaying a business partner)
• UtilBusinessPartner.GetList (displaying a business partner list)
Additional information about BAPIs
• for general information, see the BAPI User Guide and the BAPI Programming
Guidelines
• for specific information, see the documentation on the respective BAPIs in the BOR.
Merging Business Partners (IS-U)
Purpose
You can use the business partner merging function in connection with the central
business partner (SAP R/3 application component CA-BP Contract Accounting –
Business Partner) and Contract Accounts Receivable and Payable (FI-CA Financial
Accounting – Contract Accounting).
Implementation Considerations
The following SAP notes contain further information on business partner merging:
Title of SAP Note SAP Note Number

FAQs for Transferring Open Items (FP40) 616098
IS-U Transactions and Batch Input 432178
Merging Business Partners 624341
Move-In: No Meter Reading Results Proposed 503243
Integration
Part of the central business partner concept is that every natural or legal person as
well as every group is only created once in a system. There are different reasons
why a business partner is created several times in one system. Business partners
that have been created more than once are referred to as duplicates. Duplicate can
occur due to the following reasons:
• Migration from legacy systems without merging business partners

• Migration from different legacy systems without a duplicate check
• New creation of business partners in SAP R/3 Systems without duplicate checks
Data Cleansing
The Cleansing Tool (transaction CLEAR_INT) enables you to process duplicates. It
has been available since ABAP Release 5.0A and is already used by the SAP
business partner (as of SAP CRM Release 3.0, for example).
These data cleansing functions are not released for systems with industry add-ons.
For further information, see the release information about Changes to Data
Cleansing on the SAP Service Market Place under
http://service.sap.com/releasenotes → mySAP.com Application Components → SAP
R/3 → SAP R/3 Enterprise (English) → Chapter 04 Cross Application Components
(page 12).
Features
For further details about business partner merging, read the following information
on business partner objects and further functions and tools:
• Objects in Contract Accounts Receivable and Payable

• Objects and Enhancements in SAP Utilities
• Customer Change
• Objects and Enhancements in SAP CRM
• Automatic Business Partner Merging
In the following, the business partner to be removed from the system is referred to
as the source business partner. The business partner that replaces the source
business partner is referred to as the target business partner.
Objects in Contract Accounts Receivable and Payable

Definition
Business partner-dependent objects from Contract Accounts Receivable and
Payable (FI-CA) must be handled separately during business partner merging in
order to ensure that they remain consistent after the business partners have been
merged. These objects include, the contract account, the business partner’s open
items, his or her creditworthiness and clarification cases.
Use
Master data
Contract account
Each contract account is only allocated to one business partner. You cannot
immediately allocate the contract account to another business partner. First of all,
you must close the contract account and create another one before you can do this.
Set the indicator Mark Contract Account for Deletion (field LOEVM in table FKKVKP)
in the old contract account
However, the source business partner can still be used as a reference in the
following contract account fields:
1. Payer (field GPARV in contract account table FKKVKP)

2. Alternative Payer (field ABWRE in contract account table FKKVKP)
3. Alternative Payee (field ABWRA in contract account table FKKVKP)
4. Alt. Dun. Recipient (field ABWMA in contract account table FKKVKP)
5. Correspondence Recipient (field RECEIVER in contract account table FKKVK_CORR)
6. Alt. Bill Recipient (field ABWRH in contract account table FKKVKP)
When business partners are merged, you must determine the corresponding
contract accounts and change the fields above to the target business partner.
When you do this, note the following:

1. ...
1. You must also enter a contract account in the Paid By field

(VKONV in table FKKVK) for the payer
2. When you change the alternative payer and recipient, you must
also change the bank details and payment card data
accordingly.
3. You must also change any addresses defined in the contract
account for the business partners mentioned above.
Transaction Data
Open Items
In Contract Accounts Receivable and Payable (IS-U-CA), you can use the Transfer
Items (FP40) transaction to transfer items to another contract, contract account or
another business partner. During this process, the system creates transfer
documents, which you can also reverse.
This is also possible for open items that have been entered in installment plans and
collective bills.
The system can create the corresponding histories (dunning and installment plan
histories) for documents created in the target account.
Note the following points for open items:

1. Items that have been submitted to a collection agency cannot
be transferred.
2. The returns history for transferred items is not updated.
3. The interest history and accompanying interest supplement are
not updated.
In SAP Utilities, transferring open items is part of the customer change (see
customer change).
SAP note 616098 contains frequently asked questions (FAQs) about the Transfer
Items function.
For further information about transferring items, see the SAP Utilities
documentation in the SAP Help Portal under http://help.sap.com → SAP for
Industries → SAP for Utilities → Contract Accounts Receivable and Payable →
Business Transactions → Transferring Open Business Partner Items.
Clarification cases
When you process clarification cases, there is no a function that automatically
recognizes merged business partners.
You can enter the source business partner number in the following fields and
evaluate the payment lot during processing:
1. External Business Partner Number (field BPEXT in the business partner table BUT000)
2. Contract Account Number in Legacy System (field VKONA in the contract account table
FKKVK)
3. Reference Number of Business Partner in Contract Account (field EXVKO in the contract
account table FKKVK)
The disadvantage of this procedure is that you can only enter and evaluate one
number for each field.
Business partner creditworthiness

Every business partner has creditworthiness data (defined in the Utilities Industry
Menu under Business Master Data → Business Partner →Display/Change
Creditworthiness). If necessary, this data can be transferred from the source to the
target business during business partner merging.
Creditworthiness data is not transferred with the functions Customer Change (SAP
Utilities) or Transfer Items. As a result, you must manually transfer the source
business partner’s creditworthiness to the target business partner.
Automatically transferring data causes problems here because a separate decision

has to be made in each case as to whether the creditworthiness is transferred or
not. A company that takes over an insolvent company, for example, does not
necessarily want the insolvent company’s creditworthiness to be transferred.
Objects and Enhancements in SAP Utilities

Definition
In addition to FI-CA objects, SAP Utilities also contains objects and enhancements
that are dependent on the business partner and must, therefore, be taken into
consideration when business partners are merged.
Use
Master data
Utility contract
In a utility contract, you cannot change a business partner who was allocated using
the contract account. As a result, you must end the existing utility contracts before
you can allocate another business partner to the utility contract.
You can use the customer change function to do this.
Owner allocations
Every premise can be allocated to a business partner, who is then defined as the
owner. All existing owner allocations for the business partners to be merged must
be allocated to a single business partner.
Depending on the Customizing settings made under SAP Utilities → Customer

Service → Process Execution → Owner Allocation → Define Type of Owner Allocation,
you must execute the following actions:
• Maintenance via Premise

• You must enter the owner’s target business partner directly in the premise.
• Owner Allocation:
• You must change the owner allocation in the Utilities Industry menu under Customer Service →
Process Execution → Owner Allocation → Change Owner Allocation (transaction ES52).
Transaction Data
Budget billing plans
During a customer change, you can deactivate the budget billing plans for the
terminated contracts without invoicing them and transfer them to the new
contracts.
All budget billing plan items must be open. If necessary, you must use a clearing reversal to
make the payments on account. Once you have successfully changed the customer, you
must use account maintenance to allocate the payments on account to the new budget
billing plan.
Security Deposits
During a customer change, you can transfer the security deposits from the
terminated contracts to the new contracts.
Other documents from Contract Accounts Receivable and Payable

As with the customer change in SAP Utilities, other documents (that is documents
that are not mentioned here) from FI-CA are not included in this process. This
especially applies to cleared documents.
Transaction Data from Sales and Distribution (SD)
The business partner is entered in sales documents from the Sales and Distribution
(SD) component.
SD sales documents that have the source business partner entered as the payer are
transferred to the target business partner. This only takes place if the sales
documents have not yet been invoiced.
FI-CA documents that originate from SD are transferred together with the open
items.
SD transaction data cannot be transferred to the target business partner automatically.
Business Partner Contacts

Contacts are created with a reference to a business partner.
Contacts cannot be automatically transferred to the target business partner.
Constraints
When merging business partners in SAP Utilities, you must note the following
information for the objects and data below:
• Payment plans
• Payment plans with the categories AMB and BBP cannot be transferred. If these kinds of
payment plans exist, you cannot execute a customer change.
• Open items in deregulation
• In SAP Utilities, you cannot use the Transfer Items (FP40) transaction to transfer open items in
the deregulated scenario Bill Processing by Third Party.
• Collection item
• Documents submitted to a collection agency cannot be transferred using the Transfer Items
(FP40) transaction.
• Creditworthiness data for business partner
• A business partner’s creditworthiness data is not automatically transferred to the target business
partner.
Customer Change
Use
You use the customer change function to transfer the utility contracts of a contract
account, including any resulting receivables, from one business partner to another.
This can, for example, be necessary when merging business partners.
• Create customer change

• Process customer change subsequently
• Reverse customer change
• Transfer post open items due to customer change
Integration
You can use the function SAP Utilities → Customer Service → Process Execution →
Move-In/Out and then the menu option Others → Create / Reverse Customer
Changeto call the customer change.
Use the methods for the BOR object MOVEINOUT to integrate the customer change
in the Customer Interaction Center (CIC) or the front office. Transfer the parameter
OK code with the value “…”.
Prerequisites
Before you can a execute customer change, the contracts to be transferred must
have been invoiced at least once.
If you also want to transfer budget billing plans, the budget billing plan items must
all be open. If necessary, you must reset all clearings and set the accrued
receivables to payments on account. Therefore, we recommend that you execute
the customer change as close as possible to the last bill in order to avoid this
preparatory work.
Customizing
You define Customer Change Reasons in Customizing for SAP Utilities under
Customer Service → Process Execution → Move-In/Out → Define Reasons for
Customer Change.
You can also choose whether or not the following objects are also transferred during
the customer change:
• Security deposits
• Budget billing plans
• Open items
• Dunning information
Also see the Customizing documentation for the individual components and the
F1 field help.
Features
When a customer change is created, the system terminates the transfer contract
using a move-out, and creates a new contract by means of a move-in. The move-out
date is set as the end of the billing period of the most recently invoiced billing
document belonging to the transfer contract.
In addition, you can append an actual move-out date to the move-out, and an actual
move-in date to the move-in. This enables you to document when the move-out
customer actually vacated the apartment, and when the move-in customer
occupied it. If this data becomes valid at a future date, the changes to the business
partner and contract account data of the move-out customer are stored as
scheduled changes, with the actual move-out date as the validity date. For the
move-in customer the changes to business partner and contract account data are
also stored as scheduled changes, but with the actual move-in date as the validity
date.
When you create a move-out, an adjustment reversal of the most recent billing
document takes place for the transfer contract and a new billing document is
created with the value 08 (Customer Change). This billing document contains the
billing amount “0”. In addition, the most recent billed meter readings are copied
when the move-in is created. Note that constellations in the rate structure can have
the result that the billing documents from the adjustment reversal do not have the
amount “0”.
Depending on the Customizing settings, no new meter reading results are entered.
Instead, the last billed meter readings are copied when the move-in is created (see
OSS note 503243).
When you save the move-in document, the open items of the transfer contract can
be posted to the target contract created as a result of the move-in (this depends on
the Customizing settings described above). Note that is only possible if transfer and
target contract have the same company code. Open items that have already been
cleared are not transfer posted. You use the Transfer Items transaction (FP40) for
this purpose.
Depending on the Customizing setting you made previously, security deposits and
dunning information can be transferred.
Interest history and supplements are not copied during transfer of the open costs.
Budget billing plans are deactivated by the move-out, once you have set the
payment on account. Depending on the Customizing settings, a new budget billing
plan is created from the deactivated budget billing plan when you save the move-in
document. You then allocate the credit payments using the account maintenance.
The customer change assigns a posting block to the transfer contracts. You can
display this block in the move-out document. You can change the block using
methods ReleaseFicaLock and SetFicaLock of BOR object MOVEOUTDOC.
Constraints
• Open items that have been sent to a collection agency cannot be transferred.
• The returns history is not transferred to the new target business partner.
• The interest history and supplements are not copied when you transfer the open items.
• The business partners credit rating data is not transferred.
Alternatives if customer change is not possible

If a contract has not yet been invoiced, proceed as follows:
• Reverse the move-in document: Execute move-in with the correct business partner. You can use
the move-in document as a template.
• Create an intermediate bill.
• Wait for the next bill and then execute the customer change.
Objects and Enhancements in SAP CRM

Definition
If you integrate SAP Utilities with SAP CRM, you can use the data cleansing tool in
SAP CRM to manage the business partner merging cases and, in part, process them
in SAP CRM.
Use
When objects are replicated between SAP CRM and SAP Utilities, any changes to the
target business partner are made in SAP CRM. The exception to this is the contract
in SAP CRM. In this case, the target business partner is changed in SAP Utilities by
the customer change.
For further information about transfer functions for other objects in SAP Utilities, go
to Objects and Enhancements in SAP Utilities for Business Partner Merging.
Business Partner Agreement in SAP CRM

The business partner agreement in SAP CRM (corresponds to the contract account
in SAP R/3) is integrated in data cleansing as of SAP CRM Release 4.0.
Automatic Business Partner Merging
Use
You can use BAPIs or BOR methods to automate individual steps of business partner
merging. For further information on this, see the SAP note 624341 (Merging
Business Partners).
Features
You can use the following BAPIs for automatic business partner merging:
BAPI Description
BAPI_ISUACCOUNT_GETDETAIL Display contract account
BAPI_ISUACCOUNT_CHANGE Change contract account
BAPI_ISUPARTNER_GETDETAIL Display contract account
BAPI_ISUPARTNER_CHANGE Change contract account
BAPI_ISUPROP_GETDETAIL Detailed information on owner allocation
BAPI_ISUPROP_CREATEFROMDATA Create owner allocation
BAPI_ISUPROP_CHANGE Change owner allocation
BAPI_CTRACDOCUMENT_TRANSFER Transfer open FI-CA items
BAPI_CTRACCONTRACTACCOUNT_GD1 Read detailed FI-CA contract account data
BAPI_CTRACCONTRACTACCOUNT_CH1 Change FI-CA contract account
Use mostly IS-U BAPIs to change master data in SAP utilities since these function modules
contain additional fields for interfaces.
SAP does not recommend that you use the batch input procedure to automate steps. For
further information on this, see the SAP note 432178 (IS-U Transactions and Batch Input).
Requirements for automating the business partner merging have been included. If
you require any support, contact SAP.
Contract Accounts
Purpose
This component enables you to create and manage contract account master data.
In Contract Accounts Receivable and Payable, each business partner posting is
assigned to one business partner and to one contract account. In the contract
account master record, you can define, for each business partner, the procedures
that apply when posting and processing the line items of a given contract account.
These include, for example, payment and dunning.
Integration
Master data can be changed automatically by certain business transactions. In this
way, for example, a return can result in a processing lock being set.
Features
You can assign more than one contract account to a given business partner.
Similarly, a single contract account can be assigned to more than one business
partner. Note however, that in the industry components listed below, different rules
apply. You can transfer data manually or automatically. Contract accounts tend to
be managed on an open item basis. See Open Item Management. The system
logs changes to master data. See Logging Changes.
Telecommunications (IS-T) component

In this component, a contract account can be assigned to one business partner only.
Utilities Industry (IS-U) Component

In Utilities,one contract account contains all those contracts belonging to one
business partner for which the same payment and dunning terms apply. You assign
your business partner contracts to the contract accounts. Although one contract
account can contain more than one contract, each individual contract is assigned to
one contract account only. This does not apply to one-time accounts.
For more information on contracts, see the Utility/Disposal Contracts section in the
Utilities Industry component.
Insurance (FS-CD) Industry Component

You assign contracts to the contract accounts for which there is a business partner.
Each contract is only assigned to one contract account, however one contract
account may have several contracts assigned to it.
Contract account master data is usually created and changed from the operational
system using an interface.
Industry Component Public Sector Contract Accounts Receivable and Payable (PSCD)
You set up the contract accounts of a business partner for the relevant taxes
(property tax, income tax, and so on). You assign contract objects to a contract
account for which relevant taxes are levied. If different taxes are levied for a
contract object, you can make assignments to several contract accounts.
For more information about the contract objects, see the documentation for the
industry-specific component Public Sector Contract Accounts Receivable and Payable
under Contract Object.
Contract Account Category

Definition
A contract account category defines certain attributes for a contract account.
Use
You have to assign a contract account category to each contract account when you create it. The fields
that appear when you create a contract account are among the things controlled by the contract account
category.
Structure
The contract account category determines the following contract account attributes:
• Whether you are allowed to assign only one business partner or more than one to a contract
account
• Whether you are allowed to assign only one contract or more than one
• Whether you are allowed to maintain a contract account online
• The number range that is allowed for external or internal number assignment
• Whether it is a collective invoice account (IS-U)
• Whether it is a one-time account
• The editing screens or data fields that you can use to edit the contract account
Contract Accounts
Definition
Structure used to bill the posting data for contracts or contract items for which the
same collection/disbursement agreements apply.
Contract accounts are managed on an open item basis within Contract Accounts
Receivable and Payable.
Use
Alternative correspondence recipient
You can define an alternative correspondence recipient in the contract account (see
Recipient and Sender Determination).
Planned changes to the contract account

You do not have to activate contract account changes to have immediate effect, but
rather you can enter a date as from which the changes should become effective.
This data is not written to the database but recorded in change documents. The
planned changes function only applies to changes to the contract account. You
cannot schedule the creation of a contract account.
To activate this data, you should run program BUSPCDACT on a daily basis. This
writes the scheduling to the database. You can use the application object FICA to
activate planned changes to the contract account.
When you are in display mode for change documents, you can delete inconsistent
data, for example, data that arises when planned changes are cancelled.
Check digits in the contract account

When you create a contract account, you can add a check digit to the contract
account number. The prerequisites are as follows:
1. You add the check digit procedure using event 1051. (Sample function
module FKK_SAMPLE_1051_2_CHECKDIGITS for two check digits is supplied
by SAP)
2. The contract account is created with internal number assignment.
3. Only procedures with one or two check digits are supported. The number
range is configured such that it begins with a leading zero (check digit
procedure with one check digit) or with two leading zeros (procedure with two
check digits).
Contract account enhancements

You can make enhancements using the Business Data Toolset (BDT) in the menu for
transaction CAWM.
Structure
Every contract account master record consists of general data that is the same for
all business partners assigned to the contract account and business partner-specific
data that can be set differently for each business partner in the contract account.
The master data is structured according to the processes that depend on the
contract account data, such as incoming and outgoing payments, correspondence,
dunning, and so on.
Integration
All transactions relating to contract accounts access data from the contract account
master record (such as payments and dunning). Several transactions change data
in the contract account master record (such as payment locks for returns).
Contracts (IS-U)
Definition
Contracts in IS-U.
Use
Contracts represent the entities that are billed. You can bill one or more contracts
together using a contract account.
Structure
You can divide the data from contracts into three categories:
1. • General data
2. • Data relevant to billing (business)
3. • Data regarding move-in and move-out.
Integration
Contracts are linked to installations in IS-U; these installations contain technical
data with regard to billing. In the case of a move-out, the installation remains and
the contract is ended. In the case of the next move-in, a new contract is created
and linked to the installation. Only one contract can ever be assigned to an
installation at any one time.
Controlling Specifications in Contract Accounts

Use
Using the contract account, you can enter general data as well as data relating to payment, tax, dunning,
and correspondence.
Features
Frame on screen: You can define:
General data
Cross-partner data The key under which the contract account is managed in the R/3 system
and under which it may have been managed in an operational system.
Account management data • Whether this business partner is an associated company, by

specifying the unique key for the trading partner
• That the account is set for deletion. If there is no dependent data,
the account is deleted when the archiving program is executed.
• Account relationship. If several business partners are assigned to
a contract account, you can define the roles here that a business
partner has for the account. You can only assign one business
partner as the owner of the account.
• The authorization group that a contract account belongs to, so that
it can only be edited by people with the corresponding
authorization.
• Posting lock at contract account level. You can define here that no
documents be entered, cleared, reversed, or reset. You can also
choose between a posting lock and a clearing lock. If you have set
a lock, during clearing processing in online mode the open items
of a locked contract account are given an indicator and cannot be
set to active.
• That all items posted to the account receive a clearing restriction.
This has the effect that this item can only be cleared by specific
business transactions (for example, year-end settlement in a
utilities company).
• The tolerance limits that apply to outstanding payments.
• The underlying clearing category for clearing postings.
• The planning group that the business partner belongs to and how
many additional days are taken into consideration before an open
item is paid (cash management).
• That an interest key is defined at contract account level. This is
used in interest calculations to determine interest frequency,
amount limits and transfer and tolerance days as long as no other
interest key has been defined at a more specific level.
Invoice creation • That invoices are sent to an alternative invoice recipient.

• Which collective invoice account is used by this contract account
together with other contract accounts.
• The tax jurisdiction valid for calculation of tax (US/Canada)
• That no invoice is created as a result of specifying a lock reason
for a master data record.
Payments/taxes
Incoming and outgoing • That payments are processed by an alternative payer or
payments alternative payee
• The payment method that is to apply
• Which bank is used for incoming and outgoing payments
• Which card ID is valid for incoming and outgoing payments
• The reason for locking the contract account for incoming or
outgoing payments. Several limited-time locks are possible.
Taxes • That the withholding tax code is set for incoming and outgoing
payments in the relevant country. That several characteristics are
defined for each tax code, the tax rate, for example.
• The number and validity period of the certificate issued for
exemption from withholding tax.
• For which country an activity was carried out. You only have to
change the default value here if it differs from the country key of
the business partner's standard address.
• The tax criteria for sorting companies.
• The regional code for automatic address preparation.
• The county code for classifying different areas from a tax point of
view.
Dunning/
correspondence
Dunning control • That the dunning notice is sent to an alternative dunning recipient
but that the actual business partner can also receive the dunning
notice
• The grouping category to which the contract account's due items
are assigned when executing the dunning run.
• The dunning procedure with which the business partner is dunned.
• A dunning lock reason for open items. Several limited-time locks
are possible.
In addition, you also have the option of using additional industry-specific fields.
Control Data in Contract Accounts (IS-U)

Use
There are a number of attributes in the contract account that are specific to IS-U.
These can be divided into various areas.
General data, such as:
• Indicator for additional bill
• Transaction currency
• Terms of payment
• Account class
• Settlement category
• Account determination ID
• Application form
• Language
Dunning control:
• Indicator for additional dunning notice
Payment control, such as:
• Automatic debit procedure
• Number of automatic debits performed
• Number of returned automatic debits
• Indicator for recurring entry request
• No payment form indicator
Features
Several business partners can be assigned to the contract account. There is always
just one account holder. You cannot post to the other business partners.
In the Business Object Repository (BOR), you will find the following Business
Application Programming Interfaces (BAPIs) for contract accounts:
• BAPI_ISUACCOUNT_CREATERFROMDATA (creating a contract account)
• BAPI_ISUACCOUNT_GETDETAIL (displaying a contract account)
• BAPI_ISUACCOUNT_GETLIST (displaying a list of contract accounts)
You can find further information on BAPIs in the following:
• For general information, see the BAPI User Guide and the BAPI Programming Guidelines
• For information on individual BAPIs see the accompanying documentation in the BOR
Link Between Contract Accounts and Business

Partners
Use
You must assign at least one business partner to each contract account. Depending on the industry, you
may also be allowed to assign several business partners to a contract account.
Prerequisites
You can only assign additional business partners to a contract account if the respective contract account
category allows you to do this.
Features
The master data in a contract account can be divided into one part that is the same for all business
partners in the contract account (in other words, cross-business partner) and into another part that is
business partner-specific. You can set the business partner-specific data differently for different business
partners.
Link Between Contract Accounts and Contracts (IS-U)

Use
Several contracts are grouped together in a contract account. A selection of these
contracts can be invoiced together. You can make sure that several of them are
invoiced together using indicators in the contracts. Otherwise this remains optional,
that is, contracts are only invoiced together if invoicing happens to take place at the
same time.
Prerequisites
A contract must always be assigned to a contract account.
Logging Changes
Use
The system logs changes to fields in the contract account. You can display the changes when you
maintain the account online. In addition, the system records who created a contract account and when,
and who made the last change and when.
Features
Select (in the menu of the You see:
transaction):
Extras → Creation Data When a contract account was created or last changed and by
whom. There is a difference here between general and
business-partner-specific data.
Extras → Account Changes All the changes to an account. When you choose this function,
the system displays a selection list of all the fields in the
account that have previously been changed. In addition, the
system displays cross-business partner and business partner-
specific details regarding the account’s creation data and any
business partners that have been created.
By selecting individual fields, you can choose the change data.
After confirming the entries, a list of all the changes appears,
specifying the person who made them and the date of the
change.
Extras → Field Changes Changes to the field on which the cursor is positioned. After
choosing this function, a list with the changes made to this field
appears, specifying the person who made them and the date
of the change.
The system does not create change documents for process locks. There is, however, a history function
that you can call up from the dialog box for locks.
Automatic Master Data Transfer

Use
You use this function to transfer the contract account master data from legacy or
operational systems.
Features
Data is generally transferred in two steps:
1. ...
1. 1. The relevant data is read from the operational system and placed in
a sequential file (operational system sender structure) by the data
selection program. This transaction takes place outside of the R/3
environment and is not supported by R/3 programs. Therefore the data
selection program can make changes to data at this point.
2. 2. The R/3 transfer program reads the data from the sender structure,
changes the data, and places the data in the receiver structure. Data can
be changed or converted in this last step.
Activities
For more information, and the programs involved, see the Implementation Guide for
Contract Accounts Receivable and Payable: Basic Functions → Contract Accounts →
Data Transfer.
Transferring Master Data Automatically (IS-U)
Use
You use this function to transfer contract account data from a legacy system to IS-U
for the first time. It is available within the IS-U migration workbench.
Integration
You need the IS-U migration workbench to prepare and carry out the data transfer.
To do this, go to the Customizing menu for SAP Utilities and select Tools → Migration
® Establish settings for IS-U migration.
Prerequisites
You must have transferred business partners in the IS-U migration workbench
before transferring the contract accounts.
Migration Customizing for the contract accounts must have been maintained
completely.
Features
You create the contract accounts from the legacy system’s data using direct input.
Creating, Changing and Displaying Contract

Accounts
Use
You can create or change contract accounts both online and from the operational system (see Transferring
Master Data Automatically).
Only one business partner’s data is ever displayed. For more information on editing or displaying another
business partner’s data, see Displaying or Editing Other Business Partners.
Features
If you want to change or display a contract account, you can enter the contract account number or the
business partner.
The business partner is determined automatically if only one business partner has been assigned to the
contract account.
If more than one business partner has been assigned to the contract account, then a dialog box in which
you can choose a partner to be edited appears.
If several contract accounts were assigned to a business partner, a dialog box appears showing all the
contract accounts assigned to that business partner. You can select a contract account from the dialog
box and display it for processing.
Using authorization object F_KK_FCODE, you can issue authorizations for master data dialogs. You can
determine, for example, which user is no longer authorized to assign partners to a contract account. See
the authorization documentation for more information.
Creating Contract Accounts

Prerequisites
To create a contract account, you must have created a business partner to whom you assign this contract
account. You can assign additional business partners to the contract account depending on the industry
and contract account category.
In addition, in the system, a contract account category must have been maintained that you assigned to
the contract account when you created it.
Procedure
1. Select one of the following paths:
Roles
Edit contract account master data (SAP_FI_CA_CONTRACT_ACCOUNT) → Create contract
account
SAP Menu
Master data → Contract account → Create
The initial screen appears.
2. Enter the following data:
○ A business partner who is assigned to the account. At least one partner must be
assigned to each account.
○ A contract account category (see Contract Account Category),
○ You can either assign a contract account number yourself or have the system assign the
number.
3. Choose Continue.
The first data entry screen appears.
4. Enter the required data. Using the navigation buttons, you can navigate between the various data
screens.
5. Save the contract account.
Result
You have created the contract account and made all business partner assignments.
Assigning Additional Business Partners

Prerequisites
The contract account category allows more than one business partner to be assigned to a contract
account. You have already assigned a business partner to the contract account.
Procedure
Roles
Edit contract account master data (SAP_FI_CA_CONTRACT_ACCOUNT) → Change contract
account
SAP Menu
Master data → Contract account → Change
Enter the required contract account.

The first data entry screen appears.
2. If you choose Goto → New partner, a dialog box appears in which you can assign an additional
business partner to the account.
After carrying out the function, all fields that contain business partner-specific data appear with
their default values and the general data remains unchanged.
Displaying or Editing Other Business Partners

Prerequisites
One or more business partners must be assigned to the contract account.
Procedure
Using the Other partner function, you can switch between the data for individual partners for the contract
account.
Roles
Edit contract account master data (SAP_FI_CA_CONTRACT_ACCOUNT) → Display contract
account
SAP Menu
Master data → Contract account → Display
Enter the required contract account.

2. In the menu choose Goto → Other partner
A dialog box with the business partners who have already been assigned to the contract account
appears.
3. Choose a business partner.
The data for this business partner is displayed and can be edited.
Selecting Addresses for Business Partners

Prerequisites
You have maintained several addresses for a business partner and want to use each of these addresses
for a specific purpose (for example, for dunning notices).
Procedure
1. In the transactions Create Contract Account/Change Contract Account, call up the input help for
the field Name of Address on the tab pages General Data, Payments/Taxes, or
Dunning/Correspondence.
A dialog box appears with the addresses maintained in the master record of the business partner.
2. Select the required address by double-clicking on it.
Result
The selected address is copied into the field. In the contract account master record, the indicator Fixed
next to the address field is now selected. It indicates that a specific address has been selected which is
not the business partner's standard address.
You can use this function for each business partner for the contract account,
regardless of whether this is the owner of the contract account to be
created/changed or an alternative business partner (for example, dunning
recipient).
If you do not select an address, the system automatically uses the standard
address of the contract account owner for all business transactions.
Creating, Changing and Displaying Locks

In the contract account master record, there is one process lock field for dunning, posting, invoicing,
correspondence dunning, interest calculation, incoming payments, and outgoing payments respectively.
You enter a lock reason in this field if you want to lock an account. You can set the lock for a limited
period or set multiple locks for each business transaction.
Prerequisites
You have maintained the lock reasons for dunning and payment in Customizing for Contract Accounts
Receivable and Payable.
Procedure
1. Call up the contract account you want to change or display.
2. Enter a lock reason in the Lock On field on the Change Contract Account:
Dunning/Correspondence Data screen for dunning control, incoming or outgoing payments.
3. If you want to set a lock for a limited period or if you want to set or display multiple locks, press
the arrow key next to the Lock field.
A dialog box appears where you can display or enter the lock interval or the lock itself.
You can also display the lock history from this dialog box. Changes related to the locks
are written in the lock history and are not logged with change documents.
You can change and delete locks in this dialog box.
Note the following:
• If you only specify one lock reason, the lock will be for an unlimited period of time.
• If you only enter one lock reason, you can change or delete this. If multiple or limited-time locks
have been set, press the arrow key to make changes. You can then make changes in the dialog
box that appears.
• If you have set multiple or limited-time locks, the Lock field contains a ~ . In this case, choose the
arrow key to display the locks.
Result
The contract account is locked for the business transaction selected either for a limited or unlimited
amount of time, depending on the lock reason.
Assigning Contracts to Contract Accounts (IS-U)

Procedure
Contracts are created in utilities when a move-in is entered (transaction EC50E).
Contracts are automatically allocated to a contract account. You can either select
an existing contract account or create a new one.
You can find more information in the section on move-in.
Result
Once you have saved the move-in, the number of the allocated contract account is
stored in the contract.
Loans (IS-U)
Use
Note that this function does not replace the standard loan management function in
Treasury. This functions helps you manage very simple loans, such as a loan given
to a customer if an appliance (a heat pump, for example) has to be bought. It is not
possible to manage premiums or discount. The system only supports fixed interest
rates for the whole term.
Integration
Before you can use the loan function, the system has to be set up to manage
installment plans. The individual interest calculation function must be set up to
enable you to calculate interest.
Features
You can manage both interest-free loans and loans with a fixed interest rate. A
repayment plan is created for repayment of a loan. You can select the same due
date lists as those for an installment plan. Each installment through to the last
installment is of the same amount. The installment includes an interest and
repayment component. As with an annuity loan, interest is calculated on the basis
of the individual due dates of the installment. A small interest amount and a higher
repayment amount are payable at every due date. Note that once you have created
the loan, you are no longer able to change either the amount or the due date of the
individual installments.
When you create a loan, you have to specify parameters required for creating an
installment plan (such as due date lists) and other data such as net loan proceeds,
interest rate etc. When creating a loan, you have to post a document with the net
loan proceeds as well as a repayment plan for the loan. This document comprises
two line items, one of which contains the net loan proceeds and the other a
receivable in the same amount. If you have created a loan with interest, an interest
document is also posted. Depending on the due date of the repayment plan, this
interest document contains its own line item with the interest amount for the due
date.
You can group important control parameters as default values in a loan category.
You can create several loan categories so that you avoid having to manually enter
fixed parameters for the most common loans over and over again. The parameters
proposed by this loan category can be overwritten manually.
You can define an alternative recipient for the disbursement. You can also define an
alternative contract account and if necessary, an alternative business partner. This
would make sense if the disbursement were not being made to the customer who
has been given the loan, but directly to the contract partner supplying the appliance
or performing the service. The credit can also contain an explicit alternative
payment method enforcing direct disbursement of the amount.
After you have created and saved the loan, a letter can be sent to the customer.
This letter is managed in the same form class as an installment plan letter.
Settlement type 20D is used when distributing a payment between the source items
in a loan plan (interest and repayment) in settlement control.
Correspondence for Master Data Changes

Use
Using correspondence type 0030 (master data change), you can follow immediate
and planned changes to the master data of your business partners (business
partner, contract account, contract reference).
Prerequisites
In the Implementation Guide for Contract Accounts Receivable and Payable, under
Basic Functions → Correspondence → Define Fields for Creating Master Data
Changes, you have entered the tables to be considered for the correspondence (for
example, BUT000 – general business partner data). You can only define tables that
contain object classes defined by SAP, since the key for selecting the change
documents is different for each object class and is created in module
FKK_SAMPLE_1915. If you want other tables and therefore object classes to be
considered, a program enhancement is necessary. The object classes defined by
SAP are delivered in system table TFK070QC, which contains the following entries:
ADRESSE, ADRESSE2, BUPA_BUP, FMCA_PSOB, FMCA_PSOBVKK, MKK_VKONT. When
you enter a table in Customizing, the system automatically checks whether your
entry is valid. Use the input help to display the valid entries.
Once you have entered the tables, in a second step, you define the fields to be
monitored for each table (for example, STREET in table ADRC). If the system writes
a change document for a field that you have defined here in Customizing, this field
is displayed in the correspondence. To determine which tables and fields you have
to enter in Customizing, proceed as follows:
1. ...
1. 1. In the menu, choose Display Business Partner or Change Business

Partner.
2. 2. Enter a business partner, specify the screen selection, and choose
Continue.
3. 3. In the menu on the detail screen, choose Extras → Partner Changes
and select the required fields in the selection dialog box. If you choose
Technical Field Names On/Off, the system displays the table and field
names.
4. 4. Choose Continue.
A list of the change documents previously created appears.
The same procedure applies for the transactions Display Contract Account and
Change Contract Account. In the menu of the detail screen, choose Extras →
Account Changes.
Features
You have to trigger the creation of the correspondence manually. The program
selects all change documents created for the business partner on the same day and
then creates an individual correspondence. Only the change documents for the
fields defined in Customizing are considered in the correspondence. This means that
the user can decide which master data changes he wants to follow and inform the
customer about.
Only actual changes to existing data and changes made on the current date are
considered. This means that new master data, such as business partners and
addresses, are not taken into account in the correspondence.
You cannot list or individually select the selected changes for the correspondence
before the correspondence is created.
For correspondence type 0030 you can use events 1914 (print event) and 1915
(creation event). Read the documentation for function modules FKK_SAMPLE_1914
and FKK_SAMPLE_1915. You can determine industry-specific additional data for the
contract reference with a module for event 1916 (FKK_SAMPLE_1916). The module
FMCA_SAMPLE_1916 is defined for determining data for the contract object for the
industry solution Contract Accounts Receivable and Payable for Public Sector.
FI_CA_MASTERDATA is defined as the standard form class in Customizing. At the top
level (document level), the form class contains a 1:1 level to the business partner.
The hierarchy below contains the level for the change documents, whereby the
process logic determines that first the change documents and then the planned
change documents are listed (see application form example
FI_CA_MASTERDATA_SAMPLE). In the application form, you can display the old and
the new value for a changed field. Note that certain fields only contain IDs (table
keys), that is, links to the actual data (for example, bank details ID for incoming
payments). The determination of details for these IDs and other ID fields is not
supported in the standard. However, you can implement this in the customer-
specific application form.
Activities
1. ...
1. 1. In the menu of the transactions Change Business Partner, Display

Business Partner, Change Contract Account, and Display Contract
Account, choose Extras →Additional Extras → Correspondence.
2. 2. On the processing screen that appears, make selections for the
business partner, contract account, and contract reference and make
specifications for printing.
You must specify a business partner. If you do not make any restrictions
for the contract account and/or contract reference, changes to all contract
accounts and contracts (contract references) of this business partner are
considered, instead of only changes to the selected objects.
3. 3. Confirm your entries.
The correspondence is created.
Example
Example 1
A customer informs you that she has recently married and informs you of her new
last name. She requests written confirmation that her data has been changed.
Once the clerk has entered the new name in the field Last Name (BUT000-
NAME_LAST) in the transaction Change Business Partner, he creates a
correspondence that documents the change made and sends it to the customer.
Example 2
A tenant informs you that the bank details for the collection authorization that you
have will change in two months. The clerk enters the new bank details in the field
Bank Details ID for incoming payments (field FKKVKP-EBVTY) in the transaction
Contract Account and schedules the change for the date specified. Using the
correspondence for master data changes he informs the tenant about the change
planned in the system.
Utility Contracts
Definition
Utility contracts are utility service agreements between the utility company and its
business partners. The following contract categories exist:
• Delivery contracts, for example for residential contracts, nonresidential contracts, cable television,
telecommunications
• Purchase contracts for small power producers, solar installations and other forms of energy
transmission
• Plant consumption contracts for generation and distribution installations of the utility company
• Company consumption contracts, for example for the electricity consumption of offices at the utility
company
• Waste disposal contracts for the waste disposal industry.
For more information, see Waste Disposal Contract in the Waste Disposal Industry (IS-U-WA)
component.
Service contracts (for example, for maintenance and repair) are not managed in this
component; the Customer Service (CS) component is used instead. Service contracts are
billed in the Sales and Distribution (SD) component.
Use
A contract is related to a division. It links one single contract account to one
installation (see graphic for the Master Data (ISU-BF) component). However,
several contracts can be grouped together in one contract account.
A contract contains control data for contract billing and contract accounts
receivable and payable. This data includes:
• General data (for example, contract account)

• Move-in and move-out data
• Schedule data (for example, start date and cancellation date)
• Data relevant to billing
• Account assignment data (for example, account determination ID)
• Sales data
• Deregulation data (for example service providers)
• Data relevant to budget billing
Important Contract Data
With the exception of move-in and move-out data, you can change, display and
check all data of multiple contracts of a contract account simultaneously, if none of
these contracts have been terminated.
You can change the screen layout by configuring the tabstrips. For more
information, see the Move-In: Screen Layout component.
Multiple Contract Change

Use
You use this function to display or process several contracts of a contract account at once.
The function is useful because it enables you to enter and change the data that is the same for all
required contracts in one step.
Prerequisites
For the contract, you require:
• That a contract account exists
• That a move-in has been completed
To process a move-in, you choose Utilities industry → Customer service → Process

execution → Move-in.
Features
To access multiple-contract maintenance, enter the contract account. You can determine the contract
account key either by displaying the possible entries (by choosing F4) or using the data finder (by
choosing Environment → Find contract account).
In the maintenance screen you can place the cursor on a particular contract and double-click in order to
branch to the full screen of that contract.
In addition to the standard functions, you have the option of switching from display mode to change mode,
requesting another contract account for processing, or executing the overall check.
From the contract, you can branch to other IS-U objects (such as the installation or the contract account)
by double-clicking the relevant field.
You can only change entries that can also be changed in the normal contract maintenance screen
(Utilities Industry → Master Data → Business Master Data). You change other entries in the contract using
the Move-In, Move-Out, and Move-In/Out functions (which you can find under Utilities industry →
Customer service → Process execution).
Connection Object
Definition
A connection object is usually a building but can also be a piece of property or a facility, such as a
fountain or construction site.
Since an address is allocated to a connection object, the connection object links premises, device
locations and connections to the postal regional structure.
Integration
The connection object is a functional location from the Plant Maintenance (PM) application component.
Therefore, maintenance is managed using the functions of the Service Management (PM-SMA)
component, for example, if you wish to organize the repair and maintenance of devices at the connection
object level. Maintenance and repairs are billed using the Sales and Distribution (SD) application
component.
Other Information
For each connection object you can define any number of static notes. These can be printed on meter
reading orders, for example, to give field service employees extra information. Example include "Ring Mr
Y’s doorbell," "Beware of the dog," and so on. You can also sue the dynamic notes predefined in the
system (for example "Installation blocked for meter reading," "Meter reading already entered.")
Connection
Definition
The connection provides the technical link between the utility grid and the installations.
The connection processing function is optional. You will require it if you wish to manage the technical data
for the connections (for example, length of the line).
Use
The connection is modeled as a piece of equipment with the equipment category A: Connection from the
Plant Maintenance (PM) application component.
You can change the equipment category A in Customizing for Plant Maintenance
and Service Management by choosing Master Data in Plant Maintenance and
Service Management → Technical Objects → Equipment.
Maintenance and service (such as initial creation of a connection, or malfunction repair) are managed
using the functions of the Customer Service (CS-SO) component. In the Sales and Distribution (SD)
application component, quotations are created and services are billed.
The connection is allocated to the connection object when the device is installed, or when the location of
the equipment is changed in the functional location.
For more information, see:
• Plant Maintenance
• Equipment
• Service Connection (Workflow)
• Service Connection with Customer Quotation (Workflow)
• Service Connection Order Processing (Workflow)
Premise
Definition
The premise is an enclosed spatial unit that is supplied with energy, for example, an apartment or factory.
Use
A premise can have several utility installations. Since the premise is division-independent, you can
allocate electricity and water installations to the same premise, for example.
The premise is allocated to a connection object and to the address of that connection object.
For each premise you can maintain the following fields:
• Additional street data enables you to manage additional information on the street name of the
connection object. You can also store different street names.
• Storage data helps field service employees to quickly identify premises.
You can enter an owner for a premise. This owner must pay outstanding bills if the premise is empty (see
also Owner Allocation).
Technical Installation
Definition
Technical Installation
Use
You can allocate one technical installation to a premise for each division.
A piece of equipment that has already been created can also be allocated to the premise as a technical
installation. However, to do this make sure that the ISU field (IS-U data) in the Equipment category has
not been selected. You find this field in IS-U Customizing under Device Management → Technology →
Device → Define IS-U Equipment Categories.
At present, you cannot change or delete a technical installation.
Integration
The technical installation is created as a piece of Equipment.
Creating a Technical Installation

Use
You can create a technical installation when you create a new premise or change an already existing
premise.
Procedure
1. Choose Utilities industry → Technical master data → Premise → Create or Change.
If you are in change mode, enter a premise.
2. Choose Premise → Techn. inst. (technical installation) → Create.
3. Enter the division and, if necessary, a description.
A temporary equipment number is displayed in the Equipment field.
4. Save the premise.
The technical installation is created in Plant Maintenance and Service Management (PM). as a
piece of equipment with its own number.
5. To maintain the technical installation as a piece of equipment, proceed as follows:
a. Display the technical installation.
b. Double click the equipment to call it.
The Display Equipment: General Data screen appears.
c. Choose Equipment → Create.
Result
You have created a technical installation and allocated it to a premise.
Installation
Definition
An installation groups together the devices, registers, and, if applicable, reference values that belong to
the same division and are allocated to the same premise, and that are therefore billed together, such as
an on-peak and an off-peak rate meter.
An installation is allocated to one contract only. In exceptional cases (such as an installation under
construction or an installation without an owner) an installation is not allocated to a contract.
Use
The billing-relevant installation data to is managed historically. This enables you to change the rate
category within a billing period, for example, without any problems.
In addition to divisions such as electricity, gas and water, you can also allocate the waste management
division to an installation. For more information, see the Waste Managementcomponent.
To calculate charges that are not based on measurements, reference values are used. These charges
are made for the provision of energy or water. The following types of reference values exist:
• General reference values (for example, location, value to be billed, indicator for billing relevancy)
• Streetlights (for example, address, ownership status, operation modes)
The energy charge is calculated according to the burning hour calendar.
• Heating installations (for example, description, charging control, special agreements)
• Containers
Integration
To enable you to control meter reading and billing processes, the following components have been
integrated:
Component Function
Regional structure You can store temperature areas and meter reading units for streets
(ISU-BFRS) and cities in the regional structure. These can then be copied to
installations.
Portioning and In scheduling you define the meter reading dates. These dates are
Scheduling (ISU- dependent on the meter reading unit to which the installation is
BFPS) allocated.
The rate, on which the billing of the installation is based, is dependent
Rate Structure on the general rate category to which the installation is allocated. You
(ISU-BIBDRS) can override the general rate category with the individual rate
category of the installation (if you have made specific arrangements
with the customer, for example).
The registers and rate data of devices installed in the installation are
Installation maintained in the installation structure.
Structure (ISU-
DMDIIS)
Profile
You can allocate a load profile to an installation. The allocation is related to the identification of the
corresponding load profile.
Regional Structure Proposal
You can have the system propose the franchise contract from the regional structure proposals. To do this,
select the time slice you want to processes and choose Edit → Regional proposals.
Deregulation Data
The entries you make in the deregulation fields of the installation affect how the deregulation scenario is
determined.
Other Information
You can change the Valid fr. (valid from) date or the premise of an installation as long as a contract has
not yet been allocated to that installation, and no devices have been installed.
Point of Delivery (PoD)

Definition
Point to which a utility service is supplied, or for which a utility service can be
determined.
Use
A point of delivery can be identified by a unique key, called the point of delivery ID. This key is used
for communication with external systems. It ensures that, for example,
misunderstandings and incorrect data allocations can be avoided, even if a
customer switches utility companies.
Structure
Communication Types
There are two communication types:
• Communication in the deregulated energy market

This refers to communication between different utilities in a deregulated energy market. For
example a distributor may exchange consumption information with a supplier.
A distributor has measured the consumption of a point of delivery (customer’s consumption

in a given installation) and uses the point of delivery ID to send this information to the
customer’s supplier. The supplier then bills the customer based on the consumption data.
• Technical Communication
Refers to communication with an automated meter reading system (AMR), for example. This type
of communication is used in the Energy Data Management component (IS-U-EDM) for importing
profile values.
An AMR sends information on the measured load shape using the point of delivery ID (and
the register code of the register) to IS-U-EDM.
Point of Delivery Roles
When you define a point of delivery, you can assign it one of the following roles:
• Deregulation point of delivery

When you create an installation, the system automatically creates a deregulation point of delivery,
to which you can allocate a point of delivery ID.
If you require a point of delivery for communication in a deregulated energy market then you must
define it as a deregulation PoD. You can allocate a deregulation point of delivery to one or two
installations. If you allocate two installations (dual contract model), ensure that the same devices
(registers and so on) have been installed for billing purposes in both installations. A deregulation
point of delivery can be allocated to one installation only. However, several technical points of
delivery can be allocated to the same installation.
• Technical point of delivery
You require a technical point of delivery in the following cases:
 You require a point of delivery for technical communication with systems that do not use the
point of delivery ID common to the respective market.
 You require a point of delivery for technical communication with systems whose
measurement systems do not conform to market requirements, such as a device that
measure several points of delivery.
You can allocate logical registers or installations to a technical point of delivery. If you do this, the
allocation applies to all the registers contained in the installation.
A technical point of delivery distinguishes between the following point of delivery categories:
•  Normal point of delivery category
•  Virtual point of delivery category
A virtual point of delivery category is a summary of several normal point

of delivery categories. For example, the virtual point of delivery category
can summarize the consumption of the normal point of delivery
categories.
In Customizing, you define point of delivery types and allocate these to the SAP predefined point
of delivery categories.
Integration
The graphic below depicts the integration of the point of delivery in the IS-U data
model.
The data model for the point of delivery is integrated in the following tables:
The individual tables have the following functions:
Table Function
EUIHEAD Definition of the point of delivery
EUITRANS Link between point of delivery and point of delivery ID
EUIGRID Link between point of delivery and grid
EEDMUISETTLUNIT Link between point of delivery and settlement unit
EUILZW Required for technical points of delivery
Link between point of delivery and register
EUIINSTLN Required for deregulation points of delivery
Link between point of delivery and installation
For more information on the role of the point of delivery in Intercompany Data Exchange (IDE), see
point of delivery.
Application Examples
The following examples use selected processes to indicate when you must use a
deregulation point of delivery and a technical point of delivery.
• Example 1: Installation with Load Shape Measurement for Watt-Hour and Reactive Consumption
• Example 2: Installation with Load Shape Measurement for Watt-Hour and Reactive Consumption,
as well as Check Reading for Watt-Hour Consumption
Point of Delivery Transaction
You find the point of delivery transactions Create/Change/Display in the Easy Access
Menu under Technical Master Data → Point of Delivery.
The following information describes the individual fields and tab strips.
Group Box for PoD Description

The individual fields have the following functions:
Field/Symbol Function
Enables you to display different histories
History
Enables you to return from times slice display to
Header data the normal view
You cannot enter data in the To field. To restrict
New time slice the validity of the point of delivery ID, insert a new
time slice. To do this, choose New Time Slice. In
the From Day field, enter the date and time at
which you want the new time slice to become
valid. The previous time slice finishes on the start
date of the new time slice.
If you use the Metering Code structure category,
Default value you can generate a consecutive number for the
point of delivery ID. To do this, choose the Default
Value entry in the Consecutive Number field.
Valid to Validity period for the PoD ID
Structure category The system automatically proposes the structure
category defined in Customizing as the default
value (Master Data → Point of Delivery → Define
Structure of Point of Delivery ID).
Fields of the PoD ID Various fields are shown depending on the
structure category you selected
Header Tab Strip

Field Function
PoD Description Text that describes the point of delivery
Point of delivery type Enables you to select one of the point of delivery
types defined in Customizing. You define point of
delivery types in the IMG under SAP Utilities →
Master Data → Point of Delivery Define Point of
Delivery Type.
PoD role See the Point of Delivery Roles unit
Technical PoD
Deregulation PoD
Grid tab strip
Date From Period for which the grid is allocated to the point
of delivery
Date To
You can restrict the period for which the grid is
Date allocated to the point of delivery
Grid Grid that you create beforehand in the
Intercompany Data Exchange menu
Distributor The system automatically displays the distributor
allocated to the grid, provided you have allocated
a distributor in the Intercompany Data Exchange
menu under Grid.
Choose Copy to copy your entries to the list
Copy
Origin tab strip
The Origin tabstrip is for information purposes only. The entries you make here
have no effect on the function.
You can define source systems and number ranges for sources systems in
Customizing under Tools System Modifications User-Defined Functions for Energy
Data Management Source Systems.
Allocation tab strip

Valid to Validity period for allocation
You can restrict the validity period for the
Date allocation.
Register and Installation tabstrips
To allocate the point delivery to a register, choose Register and enter a device,
material, register, or piece of equipment.
You can also allocate the point of delivery to an installation. This allocation applies
to all the registers allocated to the installation. To do this, choose the Installation
tabstrip and enter the installation to which you want to allocate the point of
delivery.
Settlement tab strip

On this tab strip, the settlement units are displayed. These automatically originate
from the combination of services for the point of delivery.
However, you can also manually allocate the point of delivery to a settlement unit.
To do this, choose Allocate Sett. Unit Manually. A dialog box appears in which
you can use the F4 help to enter the required settlement unit in the Settlement Unit
field.
In the list on the tab strip you can recognize the settlement units to which the point
of delivery was manually allocated by the Manual field.
To delete a manual allocation, choose Delete Sett. Unit Manually..
To change the settlement relevance, choose Sie Change Settlement Relevance.

A dialog box appears in which you can change the date and select or deselect the
Settle field. If the field is selected, the consumption for the current point of delivery
is taken into account when the settlement unit is settlement for the given period.
In the list on the tab strip, you can establish the settlement relevance of the point of
delivery using the Settlement field.
PoD Service tab strip

Once a move-in has taken place for the installation, to which this POD is allocated,
all the services for this POD are displayed.
You must have defined the default mechanisms in the IDE menu under Services.
Service on the Basis of the Operational Area or Services on the Basis of Service
Provider Relationships.
You define the default mechanism to be used in Customizing under SAP Utilities →
Intercompany Data Exchange → Basic Settings Define Control Parameters.
The service can have various statuses, which can be identified using the following
icons:
Service exists or is created when you save
Optional service exits Is not created if you remove

the data from the Service provider field and save
Optional service is proposed Is created if the
Service Provider field contains an entry If the
entry is remove from the field, no service is
created
Service exists but conflicts with the service
proposed by the system Service either no longer
exists in Customizing or is not proposed in the
current circumstances because, for example a
contract (billable service) already exists for the
same service type
Data Exchange tabstrip

Contains all the data exchange processes relevant to the current point of delivery. The data exchange
processes are only created at service provider level. If you want to define a different
due date control for individual points of delivery then you can redefine the current
definition for the given PoD.
If you click on a data exchange process the data exchange definition appears.
To redefine a data exchange definition at point of delivery level, choose

Redefine DATEX Definition. The definition appears.
In the list on the tabstrip you can recognize the redefinition by the symbol in the
Redefinition column. The symbol means that the data exchange definitionwas
imparted to the point of delivery by the service provider.
To undo a redefinition, choose Undo Redefine DATEX definition.
If you do not want a data exchange process to be active for the current point of
delivery then you must first redefine it. The definition appears. Select the Inactive
field and leave the dialog box.
In the list on the tab strip you can see whether a data exchange process is active by
the Inactive field.
To synchronize scheduled data exchange tasks, choose Synchronize. For more
information on synchronization see Synchronization of Scheduled Data Exchange Tasks.
The individual fields have the following functions:
Field Function Symbol

Import/export Direction of DATEX
process Export process
Import process
Data exchange process Data exchange process
Description of data
exchange process
Sender/recipient Identifies sender and
recipient in DATEX Recipient
process
Sender
Own service type In export processes, the
service type comes from
the sender of the
messages
In import processes, the
the recipient of the
messages
Own service provider Own service provider
Name of service provider
Sender/recipient Identifies sender and
recipient in DATEX Recipient
process
Sender
External service type In export processes, the
the recipient of the
messages
In import processes, the
the sender of the
messages
Technical ServProv Service provider to which
a service type from the Technical service
technical service provider
category has been
allocated.
This service category
described technical
systems, such as
automated meter reading
systems.
External ServProv External service provider
Name of service provider
Redefinition Redefinition
Redefinition
Impart by service
provider
Inactive Data exchange process
inactive for PoD
Point of delivery
Valid from Validity period for data
exchange definition
Valid to
No Due Date Control No due date control is
allocated to the data
exchange process,
meaning you cannot
actively schedule the
process. The due date of
process execution
cannot be maintained.
Only process execution
data communication are
logged.
Text for Due Date
Control
Data Exchange Format z. B. MSCONS
Text for DATEX format Description of data
exchange format
Migration of Points of Delivery
For more information, see Migration of points of delivery.
Example 1
Device 4711, containing the registers listed below, is allocated to installation 0815:
Device 4711 Register Code Interval Length

Reg 1 Watt-hour energy 15 mins
Reg 2 Reactive consumption 15 mins
When you created installation 0815, deregulation point of delivery POD 1 was
created automatically. Allocate the point of delivery a POD ID, so that you have the
allocation shown below:
Point of Dereg POD Tech POD Installation Reg 1 Reg 2

Delivery
(PoD)
POD 1 X X
You can now use the point of delivery ID of POD 1 and the corresponding register
code to import the profile values of the profiles allocated to the registers.
You therefore do not have to use a technical point of delivery in order to import
profile values.
The Consumption role category is allocated as a default setting. If you do not

specify a role category, as is the case in the following graphic, the profile values are
imported for the profile that is allocated to the register with the Watt-hours register
code and the Consumption role (colored light gray in the graphic).
However, if you do want to import the profile values of the profile that is allocated
to the register with the Watt-hours register code and the Forecast role (schedule
profile colored light gray in the following graphic), you must specify the Forecast
role category.
In order to use a deregulation point of delivery in a profile value import, the system
from which you import the data must work with the same market-standard point of
delivery ID as IS-U-EDM.
If this is not the case (if for example the automated meter reading system from
which you import the values has its own numbers), you must use a technical point
of delivery for the import.
Point of Dereg POD Tech POD Installation Reg 1 Reg 2

Delivery
(PoD)
POD 1 X X
POD 2 X X X
You still require the deregulation point of delivery to export the data and send it to
other market players.
Communication in the deregulated energy market is still based on the deregulation
point of delivery.
Example 2
Device 4712, containing the registers listed below, is allocated to installation 0816:
Device 4712 Register Code Interval Length

Reg 2 Reactive consumption 15 mins
In the installation, register Reg. 3 performs the same meter reading tasks as
register Reg. 1. For this reason, the same register code is used for identification
purposes.
Registers allocated to a point of delivery must have a unique meter reading task as
described by the register code. In the following graphic, this allocation is not unique.
If you want to import profile values of the profile allocated to the register with the
Watt-hours register code and the Consumption role then 2 profiles are possible
(colored light gray in the graphic).
The load shapes for registers Reg.1 and Reg.3 cannot therefore be imported via the
same point of delivery, necessitating the use of technical points of delivery for the
profile import.
Point of Dereg Tech Installat Reg 1 Reg 2 Reg 3

Delivery POD POD ion
(PoD)
POD 1 X X X X
POD 2 X X
Point of delivery POD 1 us used to import load shapes for registers Reg. 1 and Reg.
2. Point of delivery POD 2 is used for register Reg. 2.
Point of delivery POD 1 is still used for communication in the deregulated energy
market. You must therefore define POD 1 as both a technical and deregulation
point of delivery.
The technical point of delivery role has a higher priority has a higher priority than
the deregulation point of delivery role . As soon a technical point of delivery is
created, the system uses it for selection purposes.
Note that in this case, you also must allocate data at register level for POD 1 (already
allocated at installation level).
Alternatively, you can use technical points of delivery to model the complete profile
value import, as illustrated in example 1. This would result in the following
allocation:
Point of Dereg Tech Installat Reg 1 Reg 2 Reg 3

Delivery POD POD ion
(PoD)
POD 1 X X
POD 2 X X
POD 3 X X X
Create Deregulation Point of Delivery

Use
When you create an installation, the system automatically creates a deregulation point of delivery.
Deregulation points of delivery are required for communication in the deregulated energy market .
To allocate a point of delivery ID to a deregulation point of delivery, proceed as described below.
Procedure
1. From the SAP Easy Access menu, choose Utilities Industry → Technical Master Data →
Installation → Create.
2. Make the entries required in order to create an installation.
In the lower half of the screen is the Point of Delivery group box.
3. Make the entries required for the point of delivery ID and enter the ID of a grid in the Grid field.
Note that you must have defined the grids in the Intercompany Data Exchange menu.
When you make this entry, the system allocates a grid to the point delivery. The grid is used
during the move-in to determine the default values for service, for example.
If you have not entered a point of delivery ID, you do not have to enter a grid in the installation.
However, if you have already entered a point of delivery ID then you must enter a grid. The grid is
a new entity created to IS-U Release 4.63. This means that if you upgrade your system from IS-U
4.62, there are no grids allocated to the points of delivery. If the system cannot find a grid
allocated to the point of delivery, the functions that require the grid (such as the default definition
for services) automatically search for a grid in the regional structure.
In Energy Data Management the Settlement settings determine whether you have to specify a
grid. If you have made these settings, you must ensure that all the points of delivery are allocated
to grids when you upgrade your system.
4. Save your entries
You can create an additional installation for the point of delivery by entering the
same point of delivery ID in the second installation. To do this, you must observe
the following:
• The installations must be allocated to the same premise
• The installations must have different service categories
Create Technical Point of Delivery

Use
You create a technical point of delivery if:
• You require a point of delivery for technical communication with systems that do not use the point
of delivery ID common to the respective market.
• You require a point of delivery for technical communication with systems whose measurement
systems do not conform to market requirements, such as a device that measure several points of
delivery.
Procedure
1. From the SAP Easy Access menu, choose Utilities Industry → Technical Master Data → Point of
Delivery → Create.
2. In the Structure Category field, choose one of the given categories.
The system automatically proposes the structure category defined in Customizing as the default
value (Master Data → Point of Delivery → Define Structure of Point of Delivery ID).
3. Enter the required data in the individual point of delivery ID fields.
If you use the Metering Code structure category, you can generate a consecutive number for the
point of delivery ID. To do this, choose the Default Value entry in the Consecutive Number field.
If you have defined default values in Customizing for the selected structure category (in Field
Settings under SAP Utilities → Master Data → Point of Delivery → Define Structure of Point of
Delivery ID), these values are displayed in the point of delivery ID fields. Note that if you set the
NI field (field is not ready for input), you cannot change the default values. To change the default
values, you must reset the NI field.
4. In the Valid field, the current date is displayed as a default value, and the time 00:00:00.
To change the validity of the point of delivery ID, enter a different date and/or time.
5. You cannot enter data in the To field.
To restrict the validity of the point of delivery ID, insert a new time slice. To do this, choose New
Time Slice. In the From Day field, enter the date and time at which you want the new time slice to
become valid. The previous time slice finishes on the start date of the new time slice.
6. In the PoD Description field, enter a short text to describe the point of delivery.
In the PoD Type field, choose one of the given types.
Set the Technical PoD field.
Choose Continue.
7. On the Grid tab strip, you can allocate a grid to the point of delivery, and define the duration of
this allocation.
You use grids to represent the distribution grid of a distributor in the system. By allocating a grid
to the point of delivery, you can calculate the results of settlement not only for each settlement
unit, but also for each grid.
Enter the period for which you want to allocate the grid to the point of delivery.
The Day From field contains the current date as a default value. However, you can change this
date.
In the Grid field, choose one of the grids previously defined in the Intercompany Data Exchange
menu.
The system automatically displays the distributor allocated to the grid, provided you have
allocated a distributor in the Intercompany Data Exchange menu under Grid.
Choose the Copy icon to copy the entries to the list.

8. The Origin tabstrip is for information purposes only. The entries you make here have no effect on
the function.
You can define source systems and number ranges for sources systems in Customizing under
Tools → System Modifications → User-Defined Functions for Energy Data Management → Source
Systems.
9. Choose the Allocation tabstrip.
10. To allocate the point delivery to a register, choose Register and enter a device, material, register,
or piece of equipment.
You can also allocate the point of delivery to an installation. This allocation applies to all the
registers allocated to the installation. To do this, choose the Installation tabstrip and enter the
installation to which you want to allocate the point of delivery.
To restrict the allocation data, choose Date.
In the Proration Day field, enter a new from-date and choose Prorate.
The system inserts a new line with a new time slice.
Place the cursor on the line containing the required time slice and choose Select.
11. Choose the Point of Delivery tabstrip.
Once a move-in has taken place for the installation, to which this POD is allocated, all the
services for this POD are displayed.
You must have defined the default mechanisms in the IDE menu under Services →
Service on the Basis of the Operational Area or Services on the Basis of Service Provider
Relationships.
You define the default mechanism to be used in Customizing under SAP Utilities →
Intercompany Data Exchange → Basic Settings → Define Control Parameters.
14. When you have made all the required entries, save the data.
Device location
Definition
These are locations within the connection objects where devices can be installed.
The devices can belong to different divisions.
The address of the connection object is allocated to the device location. In addition, a particular premise
can also be allocated, and a description of the device location can be entered. This means that the exact
location of an installed device is determined using the device location.
Use
The device location is a functional location from the Plant Maintenance (PM) application component.
Therefore, maintenance is managed using the functions of the Service Management (PM-SMA)
component, for example, if you wish to organize the repair and maintenance of devices at the device
location level. Maintenance and repairs are then billed using the Sales and Distribution (SD) application
component.
Services
Definition
Used to describe a service supplied to a point of delivery.
Service can be billable or non-billable. All the own or external services that are
billed and/or invoiced are modeled as a contract in IS-U. This contract is also
described as billable services. All other services are non-billable services.
The most important attributes of services are:
• Service type to describe the type of service
Service types can be freely defined. In Customizing you must allocate them to a predefined SAP
service category.
All the service types that do not correspond to one of the predefined service categories can be
allocated to the Other service category. If you want to continue using a service type based on the
Other service category internally, you must modify the templates individually.
• Service provider as a service agent
For more information on service providers, see service providers.
• Validity period of service
In the case of a billable service (contract), the validity period is based on the move-in and move-out
dates. The service type is contained in the corresponding installation.
Structure
The non-billable services are modeled as a separate entity in the point of delivery.
Device Management
Purpose
This component manages technical data, installations, meter readings, and the inspection of devices.
Integration
The 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 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 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 to distinguish 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 Component
Procurement Purchase Requisition and Purchase Order from

(MM-PUR)
Delivery Goods Receipt from Inventory Management

(MM-IM)
Outward movement (such as scrapping or Goods Issue and Return Delivery from MM-IM
sales)
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) application component.
• PM: Equipment
• LO-MD:
○ Material Master
○ Serial Number Management
• MM-PUR:
○ Purchase Requisitions
○ Purchase Orders
• MM-IM:
○ Planning Goods Receipts

○ Goods Receipts for Purchase Orders
○ Goods Receipts for Orders
○ Other Goods Receipts
○ Goods Issues
○ Transfer Postings and Stock Transfers
Technical Device and Connection Data

Purpose
This 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 a connection object to the
supply line.
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.
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.
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.
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.
For example, the command group for street lights might consist of the commands switch-
on, decrease demand, and switch-off.
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
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.
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:
• Meter
• 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
• Serial Number Management
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.
If you use MM, we recommend the first option above.

Prerequisites
You have maintained the following in IS-U:
• Register groups
• Input/output groups
• Command groups
• Inspection point groups (optional)
• Winding groups (only required for transformers)
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.
Device
Purpose
This component manages the devices of a utility company.
Devices can:
• Meter
• Control (such as audiofrequency ripple control receivers)
• Process data (such as correctors)
• Protect or adjust (such as pressure regulators)
Integration
A 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 PM
• The 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.
• Technical Objects (PM-EQM): Equipment

• Logistics Basic Data (LO-MD):
○ Material Master
○ Serial Number Management
• Purchasing (MM-PUR):
○ Purchase Requisitions
○ Purchase Orders
• Inventory Management (MM-IM):
○ Planning Goods Receipts

○ Goods Receipts for Purchase Orders
○ Goods Receipts for Orders
○ Other Goods Receipts

○ Goods Issues
○ Transfer Postings and Stock Transfers
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.
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.
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.
Creating Devices in Plant Maintenance

Prerequisites
The 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 →List editing → Create.
1. Choose Utilities industry → Device management → Technology → Device → Create.
You branch to the initial screen for creating material serial numbers.
2. 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.
3. Enter the required data. Choose Transfer.
You branch to the screen Create material serial number: IS-U data.
4. Enter the required data.
5. Save your data.
Result
The 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.
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
2. 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 order for 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 to your own criteria. Choose Classification.
5. Save your data.
You can now enter further devices as above.
Result
The 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.
Device Installation
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
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.
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.
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.
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.
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
1. 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
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.
Device Installation
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
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.
Device Installation
Purpose
You can install devices in the following ways:
• Technical installation only, for example if a meter is not to be billed. This would apply in the case
of a control meter or a meter that belongs to the utility company.
• First technical, then billing-related installation, for example if
○ Meters in an apartment building are installed first and assigned to apartments later
○ Both steps are carried out by different agents
• One technical installation and several billing-related installations. This would apply in the case of
a pressure regulator or an ARCR that controls several installations.
• Full installation, as in the case of a single-family home.
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:
1. 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),
2. The installation order is executed and returned.
3. 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:
a. If the device belongs to a device group, the entire device group must be installed in the
case of technical installations and full installations.
b. 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.
Device Removal
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
You 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.
Device Removal
Purpose
You can install devices in the following ways:
• Technical removal only, if a device (such as a control meter) has undergone technical installation
only.
• Billing-related removal 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.
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
• 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.
For more information see the following in the Technical Objects (PM-EQM) application
component:
○ Functional Locations
○ Equipment
○ Equipment at Functional Locations
Process flow
Device removal includes the following phases:
1. 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).
2. The removal order is executed and confirmed.
3. 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.
Device Replacement
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
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
Device Replacement
Purpose
This 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.
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
You enter the installation on 10/12. The installation took place on 10/08. A device
• 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.
For more information see the following in the Technical Objects (PM-EQM) application component:
• Functional Locations
• Equipment
• Equipment at Functional Locations

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.
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.
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.
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
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
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
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.
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
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
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
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
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.
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.
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.
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.
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) for February
10, 2000.
3. Perform a billing-related device installation of device D1 in the installation 2 (Inst.2) February 10,
2000.
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 orDevice → General Inventory
Management → Goods Movement → Transfer Posting.
Procedure
1. ...
1. 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. 2. Terminate any device allocations or relationships you have created
for the newly installed device.
3. 3. Perform the replacement reversal.
The new device is technically removed and the old device is technically installed.
4. 4. Establish any device allocations or register relationships you require
for the re-installed device
5. 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. 6. Perform a stock transfer for the device removed.
7. 7. Perform a stock transfer for the device removed.
Result
The replacement has been fully reversed. The device now has the status Installed
again.
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. ...
1. 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. 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. 3. Reverse the device replacement.
This produces the following results for March 01, 2000:
4. 4. Perform a billing-related device installation of device D1 in

installation 1 for March 01, 2000.
5. 5. Perform a billing-related device installation of device D1 for March
01, 2000 in installation 2.
Device Modification
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)
Device Modification
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
You enter the modification on 10/12. The installation took place on 10/08. A device
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 The device has undergone technical installation.
slice
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.
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.
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.
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.
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.
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
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.
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.
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.
Creating Device Allocations

Prerequisites
The devices have undergone a technical installation.
You now wish to maintain device allocations.
Procedure
1. Choose Device installation → Installation structure → Device allocations → Maintain
You branch to the initial screen.
2. 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.
3. 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.
4. Once you have entered all allocations, save your data.
5. 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.
6. Enter a meter reading result for the device on the date of the change.
7. Save your data.
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.
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, 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 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 balancing
consumption 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 Rate
Billing-Relevant
D1 1 RA '' RT10
G2 1 RA X RT10
Rate data from installation B:

Device Register Rate Type Register Not Rate
Billing-Relevant
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 Rate Billing Unit of Weighting
Not Bill.- Measurement Procedure
Rel.
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 Rate Billing Unit of Weighting
Not Bill.- Measurement Procedure
Rel.
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
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
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

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

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.
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:
a. 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
a. 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
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
a. 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.
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.
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
You branch to the initial screen.
2. Choose a device location or 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.
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.
3. 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.
4. Save your data.
5. 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.
6. Enter a meter reading result for the device on the date of the change.
7. Save your data.
Meter Reading
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 (ISU-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 general information, see the BAPI User Guide and BAPI Programming
• For more information, see the BAPI documentation in the BOR.
Weighting Procedure
You can only extrapolate from a base period, if it is representative. Whether a period is representative or
not is a result of the original weighting procedure.
The weighting procedure involves internal system procedures that are applied to existing meter reading
results, period consumption values or period demand values, in order to determine expected values for
extrapolation and proration
Weighting procedures are predefined as:
• Linear weighting
• Weighting of energy feeding
• Degree day weighting
• Sprinkling water portion
• General weighting
You must define the following with regard to weighting procedures in Customizing:
• Weighting key
You can define weighting key in Customizing for SAP Utilities under Device Management
® Meter Reading ® Weighting Procedure ® Define Weighting Key
Allocate user-defined weighting keys to weighting procedures predefined by SAP.
For further information read the documentation for the IMG Activity.
• Weighting unit
You can define weighting units in Customizing for SAP Utilities under Device
Management ® Meter Reading ® Weighting Procedure ® User-Defined Weighting ®
Define Weighting Unit.
A weighting unit is a fixed value, such as energy feeding volume or issue quantity of
energy or water that was issued in a certain period in a service territory.
The periods for the distribution of weighting units are always indicated by the month or
day and are year-independent.
The weighting portion of a certain period results from the relationship of the weighting
units for this period, to the total weighting units for a year.
Example:
Weighting units valid from 01.01 (100) : Total weighting units (1000)
= Weighting portion from 01.01 to 02.01. (10%)
For further information read the documentation for the IMG Activity.
You must also enter the following in the Utilities Industry menu:
• Minimum portion in percent
Enter the minimum portion in percent, in the rate. The rate is under the following path in
the Utilities Industry menu: Billing ® Master Data
The minimum portion in percent is used to determine the minimum requirements for the
representativeness of the base period.
If you enter a low minimum portion in percent, the meter reading results are used from a
short period for extrapolation.
If you enter 100% as the minimum portion, the system uses the existing meter reading
results as a basis for extrapolation, as long as meter reading results are available for a
complete billing period.
• Period length of the portion
Enter the period length in the portion. The portion is under the following path in the
Utilities Industry menu: Scheduling ® Schedule Master Record.
The period length of the portion defines the intervals for billing the associated contracts.
Linear weighting
The linear weighting procedure does not take seasonal fluctuations into account. For linear weighting, the
weighting units are distributed equally over the year, whereby the system takes one weighting unit into
account for each day. The total of the weighting values is 365 for one year or 366 for a leap year.
Weighting of energy feeding or degree day weighting

These weighting procedures take seasonal fluctuations into account.
The total weight for one year is 1000.
The weighting portion for January is 200: 1.000 = 20%
The weighting portion for February is 150: 1.000 = 15%
and so on.
User-defined weighting
In addition to the weighting procedures defined by SAP, you can define your own weighting procedures.
The total weight for one year is 1,200.
The weighting portions for months January to December are 100: 1.200.
Mixed weighting procedure

The mixed weighting procedure also takes seasonal fluctuation into account.
Enter the weighting key in the rate for the weighting of energy feeding procedure, degree day weighting
procedure or for the sprinkling water portion. Enter a consumption fixed value to be weighted linearly
or a consumption percentage for weighting in the installation structure at register level or in the
register data during device installation.
The consumption value to be weighted linearly is a fixed value per day that is weighed linearly for
extrapolation, independently of the weighting procedure (for example, 5 weighting units per day).
The consumption percentage for weighting is a percentage portion of the total weighting units per day. It
is split linearly for extrapolation, independently of the weighting procedure (for example, 20% of the total
weighting units per day).
The absolute or percentage sprinkling water portion, not taken into account for wastewater calculation, is
specified for the water division. The difference between the applied fresh water quantity and the sprinkling
water portion is equal to the waste water portion to be calculated.
If you enter a consumption value to be weighted linearly, you must also enter a validity period for which
this value is taken into account
The total weight for one year is 1,100.
The weighting portion for January is 150: 1.100.
The weighting portion for February is 125: 1.100.
and so on.
Determining whether a period is representative

To determine whether a base period is representative, use the following calculation:
Minimum portion in percent ∗ Length of meter reading period
= Minimum length of base period
or
Weighting portion of period = Minimum portion
Example:
• The following meter reading reasons exist:
Periodic meter reading
Final 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)
Control 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 as
follows:
Minimum portion in percent (50%) ∗ Length of meter reading period (365 days)
= Minimum length of base period (182.5 days)
In the example, the previous period must be at least 182.5 days in order to be representative.
or
In the example, the base period must include at least 50% of all weights.
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 next meter 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.
Extrapolation
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:
or
Minimum portion in percent ∗ Length of meter reading period
= Minimum length of base period
Example
• The following meter reading reasons exist:
○ Periodic meter reading
○ Final 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)
○ Control 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:
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:
Determined consumption of base period: Determined weight of base period
= Consumption per unit of weight
2. To determine the expected consumption of the forecast period, multiply the consumption per unit
of weight by the weight of the forecast period.
Consumption per unit of weight ∗ Weight of forecast period
= Expected consumption of forecast period
3. 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:
Period consumption Weight of the period consumption validity period
= Consumption per unit of weight
2. To determine the expected consumption of the forecast period, multiply the consumption per unit
of weight by the weight of the forecast period:
Consumption per unit of weight ∗ Weight of forecast period
= Expected consumption of forecast period
3. 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
Extrapolation for Consumption Registers

Reg. Fact. = Register factor
MR Result = Meter Reading Result
MR Reason = Meter reading reason
The following meter reading reasons exist:
• Periodic meter reading
• Final 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)
• Control meter reading
Wght. Units = Weighting units
Expected meter readings are determined by consumption registers as follows:

1. Determination of meter reading difference P1 to I:
80 kWh – 0 kWh = 80 kWh
2. Determination of consumption to P1 by multiplying the meter reading difference with the register
factor:
80 kWh ∗ 2 = 160 kWh
3. Determination of consumption per weighting unit:
160 kWh: 40 = 4 kWh
4. Extrapolation of consumption for period P1 to P2
4 kWh ∗ 60 = 240 kWh
5. Determination of the meter reading difference for period P1 to P2 by dividing the consumption
value by the register factor:
240 kWh: 10 = 24 kWh
6. Determination of the expected meter reading to P2 by adding the meter reading difference to
meter reading P1:
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 P1 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:
800 kWh – 0 kWh = 800 kWh
2. Determination of consumption to Y by multiplying the meter reading difference with the register
factor:
800 kWh ∗ 2 = 1600 kWh
1,600 kWh: 400 = 4 kWh
4. Extrapolation of consumption for period Y to P
4 kWh ∗ 600 = 2,400 kWh
5. Determination of the meter reading difference for period Y to P by dividing the consumption value
by the register factor:
2,400 kWh: 10 = 240 kWh
6. 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
4000 kWh: 1000 = 4 kWh
2. Extrapolation of period consumption for period Y to P:
4 kWh ∗ 800 = 3,200 kWh
3,200 kWh: 10 = 320 kWh
reading Y:
800 kWh + 320 kWh = 1120 kWh
Example 3: Forecasts from Previous Periods and Changes to Period Consumption Values in the
Base Period
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:
5,000 kWh: 1000 = 5 kWh
2. Extrapolation of period consumption for period Y to P:
5 kWh ∗ 600 = 3,000 kWh
3,000 kWh: 10 = 300 kWh
reading Y:
800 kWh + 300 kWh = 1100 kWh
Example 4: Forecasts from Previous Periods and Changes to Period Consumption Values not in
the Base Period
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:
(800 kWh – 720 kWh) + (720 kWh – 500 kWh) = 300 kWh
2. Determination of consumption to Y by multiplying the meter reading difference with the register
factor:
300 kWh ∗ 2 = 600 kWh
600 kWh: 300 = 2 kWh
4. Extrapolation of consumption for period Y to P
2 kWh ∗ 600 = 1200 kWh
1,200 kWh: 10 = 120 kWh
reading Y:
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
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:
a. Determination of meter reading difference Y to I:
800 kWh - 0 kWh = 800 kWh
b. Determination of consumption to Y by multiplying the meter reading difference with the
register factor:
800 kWh ∗ 2 = 1600 kWh
c. Determination of consumption per weighting unit:
1,600 kWh: 400 = 4 kWh
d. Extrapolation of consumption for period Y until the change date:
4 kWh ∗ 400 = 1600 kWh
e. 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:
a. Determination of period consumption per weighting unit by dividing the period
consumption by the weight of validity period.
5,000 kWh: 1000 = 5 kWh
b. Extrapolation of period consumption for the period from the change date to P:
5 kWh ∗ 200 = 1,000 kWh
c. Determination of the meter reading difference for the period from the change date to P by
1000 kWh: 10 = 100 kWh
2. 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 T1 to T2.this value was changed to 1200 kWh / year.
With a weighting portion of 30%, period T2 to T1 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 T5, because a period consumption change only influences forecast periods that follow directly
after.
1. Determination of meter reading difference T2 to T1:
1200 kWh - 1000 kWh = 200 kWh
=> Consumption to T2 = 200 kWh
200 kWh: 300 = 2/3 kWh
3. Extrapolation of consumption for period T4 to T5:
2/3 kWh ∗ 300 = 200 kWh
=> Meter reading difference for period T4 to T5 = 200 kWh
4. Determination of the expected meter reading to T5 by adding the meter reading difference to the
meter reading from T4:
2000 kWh + 200 kWh = 2200 kWh
The expected meter reading at time T5 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 T2 and T3.this value was changed to 1200 kWh / year.
With a weighting portion of 30%, period T2 to T1 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 T2 and T3 do not influence extrapolation for time T5 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 T4 and T5, 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.
1,200 kWh: 1000 = 1.2 kWh
2. Extrapolation of consumption for period T4 to T5:
1.2 kWh ∗ 300 = 360 kWh
3. Determination of the expected meter reading to T5 by adding the consumption to the meter
reading from T4:
2,000 kWh + 360 kWh = 2360 kWh
The expected meter reading at time T5 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 T6 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 (T5 = 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.
3,000 kWh: 1000 = 3 kWh
2. Extrapolation of consumption for period I to T4:
3 kWh ∗ 300 = 900 kWh
3. Determination of the expected meter reading to T4 by adding the consumption to the meter
reading from I:
2,000 kWh +900 kWh = 2,900 kWh
The expected meter reading at time T4 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.
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. ...
1. 1. Determination of the highest meter reading from previous reading

Y2 over a representative interval (Y2 to I):
180 kW
2. 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 Y2 to I is representative.
Demand registers always refer to the linear weighting procedure in their rate.
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 Y2 to I is representative. This means that

extrapolation is based on meter reading results rather than on the period demand.
1. ...
1. 1. Determination of the highest meter reading from previous reading

Y2 over a representative interval (Y2 to I):
180 kW
2. 2. Determined demand = expected demand:
180 kW
Example 2: Forecasts from previous periods without minimum portions with period
demand
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
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:
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 The system goes back one year from
reading results in the previous year the forecast date and looks for a
with the same allocation month as the representative period
expected meter readings
It is not important whether the period It is important that the period of
of previous year is representative 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.
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.
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.
On installation of the device, a period consumption value of 4000 kWh/year is

entered for the register.

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. ...
1. 1. Determination of meter reading difference Y to I:
800 kWh – 0 kWh = 800 kWh

2. 2. Determination of consumption to Y by multiplying the meter reading
difference with the register factor:
800 kWh ∗ 2 = 1600 kWh

3. 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. 4. Determination of consumption to Y by multiplying with the billing
factor:
16,000 kWh ∗ 1.5 = 24,000 kWh

5. 5. Determination of consumption per weighting unit:
24,000 kWh: 400 = 60 kWh

6. 6. Extrapolation of fictitious consumption for period Y to P:
60 kWh ∗ 600 = 36,000 kWh

7. 7. Determination of the actual, new consumption for period P
based on the quotient of the new and the old billing factor
8. 8. (36,000 kWh : 1.5) ∗ 2 kWh ∗ 2 = 48,000 kWh
9. 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

dividing the consumption value by the conversion factor (gas):
24,000 kWh : 12 = 2,000 kWh

2,000 kWh : 10 = 200 kWh

12. 12. Determination of the expected meter reading to P by adding the
meter reading difference to meter reading Y:
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.
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 P2:
1,905 kWh -1,000 kWh = 905 kWh
905 kWh: (90 + 91) = 5 kWh
3. Extrapolation of consumption for period from P2 to the time of data change (April 01, 1997):
5 kWh ∗ 90 = 450 kWh
4. Determination of proration meter reading at the time of the rate change by adding the
consumption to the meter reading at P2:
1,000 kWh + 450 kWh = 1,450 kWh
Proration meter reading on April 01, 1997 is 1,450 kWh.
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. ...
1. 1. Determination of the extrapolation period
2. 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. 3. Determination of the time variability
Transfer of schedule records to the extrapolation period

4. 4. Determination of period consumption
Transfer of period consumption to the extrapolation period
5. 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.
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.
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.
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.
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.
3. Allocate all devices from the top node to the bottom node Devices allocated to the street route.
4. To change the route or to allocate devices to a route:
a. Select either an object, a node or a block.
b. Position your cursor on the item selected.
c. Choose Edit → Reassign.
4. 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.
You can define your own meter reading route with enhancement EDMLSORT.
Mass Changes to Meter Reading Units

Use
You use this function to change the meter reading unit in several installations for a key date.
Prerequisites
1. Define parameter groups
To define parameter groups, go to Utilities Industry → 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.

For more information, see the documentation in the system.
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-
BFPS) 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 Object 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 general information, see the BAPI User Guide and BAPI Programming
• For more information, see the BAPI documentation in the BOR.
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 meter
reading 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.
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 with the corresponding scheduled 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.
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 09/30 10/30 11/30
Installation 1 MR by customer MR by customer MR by utility
Installation 2 MR by customer MR by utility (move- MR by customer

in/out)
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, in which case the scheduled
meter reading category is meter reading by the utility.
The utility company reads meters on 10/30 for installation 2 because the customer has moved
out. A meter reading order for reading by the customer is created for 11/30 during the first order
creation run, as permitted by meter reading control settings.
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.

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:
• 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.
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.
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.
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.
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.
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- MR by customer
in/out)
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.
Reversal
Use
This function allows you to reverse all objects generated via meter reading order creation, including:
• Meter reading orders
• Meter reading results (optional)
• Billing orders
Reversal might be necessary if, for example, you determine the scheduling data was incorrect after you
created periodic meter reading orders for a meter reading unit. A reversal may also be necessary if 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
This means that new meter reading orders are created for all devices when meter reading orders
are created again.
• Are not to be deleted
This means that when meter reading order creation is carried out again, new meter reading
orders are only created for devices that were not read. Meter reading results are processed for
devices that were read.
To reverse orders and results that have already been billed, go to Billing → Billing Execution →Reversal.
You can only reverse and delete meter reading results entered for a device installation, removal or
replacement here.
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.
Monitoring of Meter Reading Results

Features
Portion and Meter Reading Unit
You can display schedule records and billing or meter reading orders.
Each schedule record contains the following information:
Billing Order
• Planned
Number of contracts for which a billing order is to be created
• Actual
Number of contracts for which a billing order was created
• Billed, Billable, Non-Billable, Billing Suppressed
Number of meter reading orders that have been created, that can be billed, or that have been billed
Meter Readings
• Planned
Number of contracts for which a meter reading order is to be created
• Actual
Number of registers for which a billing order is to be created
• Valid, Invalid, Implausible
Meter reading orders that have been prepared, number entered as implausible and number entered
as plausible
Contract, Installation or Business Partner
You can display meter reading results and billing or meter reading orders.
Device
You can display meter reading results or meter reading orders.
Activities
In almost all of the monitoring function’s lists, you can branch to the details of an
object by clicking on the corresponding field or by choosing Edit → Select in the
menu bar.
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.
Device Inspection
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.
Device Inspection
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
The sampling procedure reduces the number of devices to be inspected or certified. Devices are
selected randomly from a large number of similar devices.
2. Device replacement
The devices to be inspected are removed or replaced via the periodic replacement function or via
a special replacement order.
3. Inspection or certification
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.
4. 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.
Sampling Procedure
Purpose
This component allows you to include devices in sample lots. Lots can be created
for devices subject to certification from the electricity, gas, water and district
heating divisions. Sample lots are divided into external and internal lots. This allows
you to inspect devices on the basis of legal requirements or internal quality
standards.
A fixed number of sample devices is drawn from each lot. If the sample devices pass
inspection, the entire lot will be renewed.
Due to the individual responsibilities of the different instances worldwide
(calibration authorities, for example), a general certification of this sampling
procedure is not possible. You should therefore check the permissibility of this
procedure before you implement it.
Different requirements for the described procedures (in particular with regard to the
drawing of samples) are not provided for as standard. You can however use the
interface described below for this purpose. These interfaces provide support for
enhancing or modifying the standard procedure.
This component is optional. You require it if you wish to create sample lots.
Integration
If a lot fails, normally all devices are placed in the periodic replacement list (unless
a device has already been removed) and certified individually. To do this, you need
the Periodic Replacement (IS-U-DM-IS-PR) and Certification (ISU-DM-IS-CT)
components.
The device does not lose certification if it is certified beyond the certification period of the
lot. To override this, go to Customizing and choose Device Management → Inspection →
Basic Settings → Define Parameters for Inspection/Certification. Select the CP (Certification
period of device overrides lot) field.
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, however.
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. ...
1. 1. Lot creation
You create a lot master record that contains the lot data.
2. 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. 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. 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. 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.
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.
Lot Compilation
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.
Compiling Lots
Prerequisites
Before you compile official lots, sample devices must not be drawn from the lot.
Procedure
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.
You branch to the initial screen of the transaction.
2. Enter the lot number and choose Lot → Add → Single devices.
You branch to the entry screen for single devices.
3. 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:
2. Enter the lot number and choose Lot → Add → Via device category.
You branch to the entry screen for selecting devices from the sample lot via the device category.
3. 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.
4. Choose Lot → Determine device to determine the devices that match your criteria.
You branch to a list with the number of devices found for a certain device category.
5. Choose Save to allocate the devices to the lot and return to the initial screen.
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
2. Enter the lot number and choose Lot → Delete → Single devices.
You branch to the entry screen for deleting devices from the sample lot.
3. 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

2. Enter the lot number and choose Lot → Delete → Via device category.
You branch to the entry screen for deleting devices from the sample lot via the device category.
3. 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.
4. 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.
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.
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:
1. • 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.
2. • Random number table
In Germany DIN (German Industrial Standard) 57 418 Part 6/VDE 0418 Part 6, June 1983 applies.
3. • Algorithm for determining the random numbers
4. • 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:
5. • Division
6. • Indicator Single sample lot drawing
7. • Type of certification requirement
8. • Type of sample device (sample device or spare sample device)
9. • Lot size
To carry out a drawing, you need to perform the following activities:
1. ...
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:
1. • The random number is larger than the lot size
2. • The random number is zero
3. • The random number has already been determined
4. • The device has already been a sample device or a spare sample device (this can be changed
via customizing)
5. • The device is in the warehouse (if warehouse devices are not permitted during the drawing)
6. • The device is not allocated to the lot (due to a removal, for example)
7. • The device does not exist
8. • 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.
9. • 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.
10. • 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:
11. • If the first decimal place of a starting number is greater than four, it is ignored and the next
random number is determined.
12. • 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.
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.
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.
2. Enter the number of the lot from which you wish to draw sample devices and choose Enter.
You branch to the next screen for sample device drawing.
3. 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:
a. 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.
However, you must first define percentages in Customizing under Define Determination
of Sample Lot Devices.
b. 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.
To display the results of the drawing, choose Drawing → Display → Drawing 1 details.
2. 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.
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.
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).
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.
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
• 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).
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.
Certification
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.
Certification
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.
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.
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.
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.
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
1. • 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.
2. • 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
3. • 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).
4. • Table TQ32
Enter inspection type 08ISU_01 for inspection lot origin 08.
5. • 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).
6. • 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.
7. • 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).
Operation
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 R/3
system to a subsystem.
QIRF_GET... : These function modules allow you to upload data from a subsystem to
an R/3 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 R/3 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. ...
1. 1. Delivery of the devices
It is irrelevant whether or not the devices are serialized on delivery.

2. 2. Install devices
The devices are serialized at this point at the latest.

3. 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. ...
1. 1. Transaction QM01.
2. 2. Enter material, plant, and inspection lot origin.
3. 3. On the next screen, enter the number of devices that you want to
inspect using the QM lot (inspection lot amount).
4. 4. The serial numbers of the devices are only allocated to the QM lot
when you record the inspection results (transaction QE01).
5. 5. Manual transfer of devices to inspection stock.
Generate QM Lot by Stock Transfer

1. ...
1. 1. Transaction MB1B.
2. 2. Enter movement type U11, plant and, if necessary, storage location.
3. 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. 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. 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. 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
R/3 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, 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:
1. • Table TQ07:
 Define a follow-up action
 Define the function module to be executed for the follow-up action
2. • 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.

My IS-U

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

My IS-U

Hochgeladen von

Copyright:

Verfügbare Formate

SAP Utilities

Postal Regional Structure

Maintaining the Political Regional Structure

Maintaining the Hierarchy

Portioning and Scheduling

Schedule master records are made up of the following objects:

The following functions are possible:

• Create parameter record

• Group contracts for billing purposes according to regional criteria

The following functions are possible:

For further information, see note 630244.

Meter Reading Unit

1. Group installations for meter reading purposes according to regional criteria

1. Fields for organizational data

The following functions are possible:

3. Create meter reading unit

Generating schedule records from 03/01/03 to 12/31/03

• Scheduled billing date

• Scheduled meter reading date

• Scheduled meter reading date

• Scheduled meter reading category

The following functions are possible:

• Create the schedule record

1. 1. Create parameter record

Create Meter Reading Unit

Field name Description

Specifies the scheduled meter reading date of

Specifies the date when the meter

Specifies the date when the meter

Specifies the download date.

Specifies the date of the meter

Specifies the date when the meter

Field name Description

Used as the base date for

Used during the demand value

In addition to periodic meter reading,

Specifies the kind of meter reading to

If you set this indicator, you can only

Set this indicator if you want adjust

Generate Schedule Records

Generate Schedule Records for the Meter Reading Unit

Regenerate Schedule Records for a Meter Reading Unit

• SAP Business Partner (SAP BP)

BP Role Contract Partner

• Relationships: Relationships to other business partners (see Relationship Categories)

BP Role: Contract Partner (IS-U)

Changes to Payment Data

• Create new bank/payment card details

The processing takes place in three steps:

Mode Function Call via Button

1. 1. In the Implementation Guide for Contract Accounts Receivable and

1. 1. From the SAP menu, choose Master Data → Business Partner →

Bank Details Area

Contract Accounts Area

The following contract accounts appear here:

Automatic Selection of Contract Accounts in the List

Mode Automatic Selection

There are different cases depending on the option selected:

Special Case 2: Alternative Payment Details

Special Case 3: Business Partner Is Payer/Payee

Special Case 4: Business Partner Is Payer

BAPIs for Central Business Partner (CBP) (IS-U)

Title of SAP Note SAP Note Number