My Oracle Support Banner

Wrong Action - Invalid UOM/Interval Register Type Combination On Meter Configuration can be saved in system (Doc ID 1476410.1)

Last updated on SEPTEMBER 27, 2022

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.3.1 to 2.3.1 [Release 2.3]
Information in this document applies to any platform.

Symptoms

**Examples provided in this article do not represent real life personal/confidential information**

**Disclaimer:** This KM article may include the following abbreviations:
 
CCB/CC&B - Oracle Utilities Customer Care and Billing
OUAF/FW - Oracle Utilities Framework
OS - Operating System
UOM - Unit Of Measure

On : 2.3.1 version, MR - Meter Read

ACTUAL BEHAVIOR
---------------
Register with UOM/Interval Register Type combination not valid for the Meter Configuration Type allowed to be saved on meter configuration record.

EXPECTED BEHAVIOR
-----------------------
The logic of Register Row Maintenance (CIPMREGR) should include the Interval Register Type together with UOM/TOU combination in checking if a register don’t match with any of Meter Configuration Type’s UOM/TOU/Interval Register Type.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
A user added a meter configuration for a meter, specifying a valid Meter Configuration Type.
The Interval Register Type of one of the registers was updated, yielding to an invalid combination (based on the register list of the Meter Configuration Type).
CC&B allowed the meter configuration to be saved.

If picked up a Meter Configuration Type which has a combination of UOM/Interval Register Type with the Validation value set to "Required" for above scenario, a warning message windows does pop up when
trying to save changes.
For the Meter Configuration Type has the Validation value set to "Optional", the invalid combination of UOM/Interval Register Type is allowed to be saved on Meter Configuration without any pop-up warning messages.

Even the Save is proceed for such status, problem was discovered when the sync batch jobs to MDM were executed and problems in determining the Measuring Component Type was experienced.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.