Show TOC

 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 ManagementInstallationInstallation StructureRegister 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 UtilitiesToolsSystem ModificationsUser-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 UtilitiesToolsSystem ModificationsUser-Defined Enhancements for Register RelationshipsDefine 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.