Use

The function allows you to map the relationship between two or more registers.

You find the transactions for register relationships in the Utilities Industry menu under Device Management →

Installation → Installation Structure → Register Relationships

Prerequisites

The device must first undergo a technical installation.

Activities

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

Deleting Registers from the Existing Register Relationship

If you want delete the registers of a device from an existing register relationship, you cannot enter this device

in the initial screen of the Change Register Relationships transaction. If you do enter the device to be

removed, the system issues the message EN478 (at least one register must correspond to initial data) when

you try to save the data.

Enter one of the following objects instead:

Another device from the register relationship

The device location where the devices are installed

The installation where the devices are installed

Make sure when you enter the device location or installation that there is at least one other device in the

register relationship installed in the device location or installation.

Limitations when Processing Register Relationships

General Limitations

All registers affected by the register relationship must be installed over the whole processing period. A register

relationship can only exist once within a period.

Customizing Restrictions

You can find the Customizing settings for register relationships under SAP Utilities → Tools → System

Modifications → User-Defined Function Enhancement for Register Relationships

All devices effected by the register relationship must belong to a division for which the register relationship

category is permissible.

See Define Permissible Register Relationships per Division Category in Customizing.

Only operation codes that have been defined as permissible for this register relationship category can be used

The number of operation codes must be within the range set in Customizing

See Define Operation Code per Register Relationship in Customizing.

If the UM field (units of measurement must match) is selected in Customizing, all registers in the register

relationship must have the same unit of measurement.

See Define Types of Register Relationships in Customizing.

If the SA field (installations must match) is selected in Customizing, all registers in the register relationship

must have been installed (billing-relevant) in the same installation.

See Define Types of Register Relationships in Customizing.

Restrictions for Different Register Relationship Types

Restriction for Active/Reactive Relationship 01

Reactive and active registers must have the same register category. The system does differentiate between

cumulative and balancing registers.

For the reactive register, enterreactive registerin the RA field (difference between reactive, apparent and

active registers).

For the active register, enteractive registerin the RA field.

Restrictions for Serial Switching Relationship 02

Serial Switching only for Consumption Registers

Serial switching is only supported for consumption registers. Primary and secondary registers must therefore

have the register categories cumulative or balancingconsumption register.

Serial switching of demand registers is not possible. In demand registers, the measured demand peaks from

primary and secondary registers do not necessarily occur at the same time. The difference of demand from

the primary register minus the demand from the secondary register does not match the demand that is to be

billed for the primary meter.

If you already have serial switching demand registers in your company, you must map these using special

rates:

You can calculate the difference between primary and secondary register demand using the DEMAND02

variation.

If necessary, you can use DEMAN09 to multiply the demand difference with a reduction factor.

You must define your own type of register relationship if want both demand registers to be read at the same

time.

You can define this in Customizing under: SAP Utilities → Tools → System Modifications → User-Defined

Enhancements for Register Relationships → Define Types of Register Relationships

Serial Switching of Different Secondary Registers

The primary meter can only be the primary meter in one serial switching relationship. You can allocate more

than one secondary meter to one primary meter in a serial switching relationship, however. If this is the case,

the total of all secondary meter consumptions is subtracted from primary meter consumption.

Multilevel serial switching is also possible. A secondary meter can also be a primary meter.

To do this, you must create two serial switching relationships.

Reactive/Active Indicators

Primary and secondary reactive/active indicators must match.

Installation Allocation

During the serial switching period, all secondary meters must be installed (billing-related) in the same

installations as the primary meter.

We also recommend that you select the N (register not billing-relevant) field in the primary meter installation.

You must enter a rate type for the secondary meters in the main meter installation. You must also do this

when the field N (register not billing-relevant) is selected.

( ) Example 1:

Device D1 is allocated to installation A.

Device D2 is allocated to installation B.

You want to create a register relationship with D1 as the primary meter and D2 as secondary meter. Proceed

as follows:

Step 1:Allocate device D2 to installation A.

Rate data from installation A:

Device Register Rate Type Register Not Billing-Relevant Rate

D1 1 RA ' ' RT10

G2 1 RA X RT10

Rate data from installation B:

Device Register Rate Type Register Not Billing-Relevant Rate

G2 1 RB ' ' RT50

Step 2:Create the register relationship.

Device Register Operations Code

D1 1 3 (Primary register)

G2 1 4 (Secondary register)

When you bill installation A, the consumption from device D2 is subtracted from the consumption of device D1

in rate RT10.The consumption of device D2 is not evaluated.

( ) Example 2:

In example 1, device D2 was allocated rate RT10 in installation A, and rate RT50 in installation B. This is only

permitted if both rates have the same weighting procedure, billing unit of measurement, and minimum portion.

This is not the case for example 2.

Device D1 is allocated to installation A. Installation A is a commercial enterprise. Device D1 is to be billed

using rate RT80. RT80 has linear weighting (weigh) and billing unit of measurement (UM) MWh.

Device D2 is allocated to installation B. Installation B is a normal household. Device D2 is to be billed using

rate RT50. RT80 has weighting of energy feeding and the billing unit of measurement kWh.

Both devices must be switched after each other, with D1 as the primary meter and D2 as the secondary

meter.

You can no longer allocate the same rate types to the devices D1 and D2 in installation A. Instead, you must

enter a rate type for device D2 that determines a rate compatible with the RT50 rate.

Rate data from installation A:

Device Register Rate Type Register Not Bill.-

Rel.

Rate Billing Unit of

Measurement

Weighting Procedure

D1 1 RA ' ' RT80 MWh Linear

G2 1 RC X RT30 kWh Weighting of energy

feeding

Rate data from installation B:

Device Register Rate Type Register Not Bill.-

Rel.

Rate Billing Unit of

Measurement

Weighting Procedure

G2 1 RB ' ' RT50 kWh Weighting of energy

feeding

Result

When you enter meter reading results for D2, the plausibility checks are always executed with the billing unit

of measurement kWH and weighting of energy feeding. The plausibility check and extrapolation of meter

reading results from D2 are dependent on whether they refer to installation A or B. The indicator N (register

not billing-relevant) does not effect the entry of meter reading results.

When installation A is billed, both devices D1 and D2 are allocated to the rate RT80. The meter reading

differences in consumption for both devices are converted into MWh. The MWh consumption of the secondary

meter is subtracted from the MWh consumption of the primary meter. Rate RT30 is not used for billing

installation A because the field N (register not billing-relevant) is selected.

If there has been a price change in the billing period, both registers undergo linear proration. This not

completely correct but cannot be avoided. If different weighting occurs, secondary meter consumption in a

prorated time slice may be calculated higher than primary meter consumption.This can occur even when the

total primary meter consumption is larger than the total secondary meter consumption.As a result of this, we

recommend that you avoid using different weighting whenever possible.

Register Discount

You can also offer discount on registers that are serially switched. Note the order in which the serial switching

and register discount are processed in billing:

Firstly, non-discount secondary register consumptions are subtracted from non-discount primary register

consumption (=deduction consumption).

If a register discount is entered for the primary register, the deduction consumption is also discounted.

A register discount on the secondary register does not effect the primary register consumption to be billed.

If, for example, meter reading results from a secondary meter have to be changed due to transformation

losses, you cannot use register discounts.If this is the case, you must enter a suitable register factor for the

secondary meter.The register factor is included in billing before the deduction consumption is calculated.

Restrictions in a Primary Rate – Secondary Rate Relationship

Primary and secondary registers must have the same register category.The system does differentiate

between cumulative and balancing registers.

The entry in the BW field must be the same for the primary and secondary rate register.

Restrictions in Control Relationship 04

Register and control register must have the same register category.The system does differentiate between

cumulative and balancing registers.

The entry in the BW field must be the same for the register and control register.

Restrictions in Volume Correction Factor Relationship 05

Both registers must have the same register category.The system does differentiate between cumulative and

balancing registers.

The register that transfers the volume correction factor can only occur in one register relationship of the

categories volume correction factor relationship and volume correction factor calculation.

The register that inherits the volume correction factor can occur again in a register relationship as an operating

volume register.

Restrictions in Volume Correction Factor Calculation 06

Both registers must have the same register category.The system does differentiate between cumulative and

balancing registers.

The standard volume register can only occur in one register relationship of the categories volume correction

factor relationship and volume correction factor calculation.

The operating volume register can occur again in a register relationship as a volume correction factor

inheriting register.

Restrictions in Resetting Relationship 07

The reset register must be a balancing register.

If a tax group has been entered for the resetting register, it must correspond to the tax group entered for the

reset register.

The resetting register and reset register can only be present in one resetting relationship.

Restrictions in Pulse Relationship 08

Both registers must have the same register category. The system does differentiate between cumulative and

balancing registers.

The entry in the BW field must be the same for the register and control register.

Restrictions in Usage Hour Relationship 09

Only watt registers and consumption registers can be used.

This post is about Installation Groups.

It is a continuation of the a previous post on Serial Switching.That can be found here. As I have

become lazy so there is no presentation , but I have included the screenshots in the post. :)

The concept of Installation Groups was developed for billing serial switchings.It can be used for

other purposes as well where data exchange between installations is needed.

For more on Serial Switching check the help site for Utilities or you can check my blog post too.

There are Cookbooks available for Serial Switching and Installation Groups in the SAP Service

Market Place at http://service.sap.com/utilities -> Product Information -> IS-U/CCS ->

Billing/Invoicing -> Cookbooks & Guidelines.

If you want to use Installation Groups for Serial Switching then you must define the installation

with the primary register as the primary installation in the Installation group and the installation

with the secondary register becomes the secondary installation for the Installation Group.

An Installation Group can have only one Primary Installation and one or many Secondary

Installations.

So like in Serial Switching we can define a Secondary Installation as the Primary Installation for

another relationship,this cannot happen with Installation Groups.  But one can define Installation

Groups with hierarchies.

So there would be one Primary Installation in the Installation Group with heirarchy level as 1.

The Secondary Installations which have Primary Installation as higher level installation will have

hierarchy level as 2.

The other Secondary Installation which have Secondary Installation with hierarchy level 2 as

higher level installations will have hierarchy level as 3.

There is some Customizing needed for creating Installation Groups.

We need to define the Grouping Types, Installation Roles,Distribution Types and Data

Exchange.

For Grouping TypesSAP Utilities->Master Data->Utility Installation->Define Grouping Types

for Installation Groups

GroupingTypes for Installation Group

For Installation RolesSAP Utilities->Master Data->Utility Installation->Define Installation Roles

Installation Role for Installation Group

Assgining Installation Roles to Grouping TypesSAP Utilities->Master Data->Utility

Installation->Allocate Installation Roles to Grouping Types.

Installation Roles assigned to Grouping Type

Distribution TypesSAP Utilties->Contract Billing->Billing Master Data->Rate Structure->Define

Billing Rules for Installation Groups

Distribution Type for the Grouping Type in Installation Group

Grouping Types are metioned for the Primary Installation.

Installation Roles are mentioned for the Secondary Installations.

Depending on the Distribution Type the Grouping Type is used.

Now the Installation Group is to be manitained in the installation.This is done in the Time

Dependent Data block.

For Primary Installation maintain the field Grouping Type.

For Secondary Installation maintain the fields Installation Role and Primary Installation key.

Another important perequisite is that Serial Switching should also be manitained.

Data Exchange betweeen Primary and Secondary Installation is one fo the main function

of Installation Groups.The Data Exchange takes place in two ways and is refered to as taking

part from secondary installation side:

Consumption Relevant : when billing primary installation consumption and billing data is taken

from the secondary installation.

Distribution Relevent : when billing secondary installation consumption and billing data is

taken from the primary installation.

This customizing is maintained in SAP Utilties->Contract Billing->Billing Master Data->Rate

Structure->Define Billing Rules for Installation Groups

Data Exchange between Secondary Installation is not supported.

Data Exchange tasks need to be maintained for each Installation Role

So an Installation Group can have only one Primary Installation.

If business requirement ask for more than one Primary Installation then it can defined as a

secondary Installation with a different role and hierarchy.

An Installation cannot belong to more than one Installation Groups.

Allocation to Installation Groups is historical that means it can change over time.

Changes to the Installation Group properties for a single Installation can affect the Billing of

the entire Installation Groups.

The ISU_INSTGR_DISPLAY report gives an overview of the master data for an entire

installation group.

We can apply Installation Groups in many scenarios like:

1. Data Exchange from Secondary Installation to Primary Installation.

2. Data Exchange from Primary Installtion to Secondary Installation.

3. Multiple Data Exchanges.

4. Budget Billing

5. DPC and Backbilling.

6. Period End Billing etc,Here we look at the first one as its the most general one.

Data Exchange from Secondary Installation to Primary Installation

The prerequisites for this scenario are:

* Serial Switching should be present between the Primary Register and the Secondary Register.

* Primary Installation must belong to the primary register.

* Secondary Installation should belong to the Secondary register.

* the Consumption difference is to be evaluated in the Primary Installation.

* the Data Exchange shall be ‘Consumption Relevant’.

* Always the Secondary Installation should be billed first and then the Primary Installation

because the data exchange happens from the ERCHV tables line items which are generated

only after Billing happens.The data exchange does not read meter readings directly.

Outline of Billing Scheme for Secondary Installations

No. Rate Variant Input Operand1 Input Operand2 Output Operand

1 SUBREG QUANTI14 SUBREGCS SUBCS

2 SUBPR QUANTI01 SUBCS SUBQPR SUBAMT

3 SUBPR QUANTI22 SUBCS

Outline of Billing Schema for Primary Installation

No. Rate Variant Input Operand1 Input Operand2 Output Operand

1 MAINREG QUANTI14 MAINREG MAINCS

2 MAINPR QUANTI02 MAINCS SUMSUB DIFFCS

3 MAINPR QUANTI01 DIFFCS MAINQPR MAINAMT

The Operand SUMSUB should have ERCHV Operand Indicator checked.

ERCHV Operand Indicator should be checked for Operand SUMSUB

The Data Exchange is also to be defined.

Grouping Type Role Source Operand:Secondary Installation Target Operand:Primary

Installation

GT01 IR01 SUBCS SUMSUB

Data Exchange task defined for Installation Role and Grouping Type

So once this is done and the Primary Installation is alloted the Grouping Type in the Time

Dependent Data block and the Secondary Installation is alloted the Key for Primary Installation

and the Installation Role.Check out the new button which comes up.

Primary Installation

Secondary Installation

We can create the Meter Reading Order(EL01) , We can check with the report

ISU_INSTGR_DISPLAY on the Installation Group.

Report ISU_INSTGR_DISPLAY on the Installation Group.

Report ISU_INSTGR_DISPLAY on the Installation Group- Master Data

Report ISU_INSTGR_DISPLAY on the Installation Group- Billing Documents

Report ISU_INSTGR_DISPLAY on the Installation Group- Schedule Records

Enter the Meter Reading Result(EL28)

Entering Meter Reading Result

and proceed with the Billing ,first for the Secondary Installation and then the Primary Installation.

Billing Document for Secondary Installation

Billing Document for Primary Installation

Report ISU_INSTGR_DISPLAY on the Installation Group - Billing Document

Report ISU_INSTGR_DISPLAY on the Installation Group - Billing Document II