IMDs Having The Same Period And Reads Are Finalized Instead Of Failing Into Duplicate IMD Checks (Doc ID 2206469.1)

Last updated on NOVEMBER 22, 2016

Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.2 and later
Information in this document applies to any platform.

Symptoms

IMDs having the same period and reads are finalized instead of failing into duplicate IMD checks

ISSUE #1: Although the two IMDs have the same period and reads but having different BO where in the 1st IMD’s BO is D1-ManualIMDScalar and the 2nd IMD BO is D7-InitialLoadIMDScalar, both IMDs are finalized instead of failing into duplicate IMD checks.
Upon checking the IMD’s initial and manual preVEE bo data area, we have found differences on their element tags which causes the duplicate IMD check to NOT detect that there is already an existing FMD. The bo data area of D7-InitialLoadIMDScalar’s preVEE have elements that are not present in the preVEE’s bo data area of D1-ManuallMDScalar.


ISSUE #2: Although the two IMDs have the same period and reads and having same BO of D7-InitialLoadIMDScalar, both IMDs are finalized instead of failing into duplicate IMD checks.
Upon checking the IMD’s initial preVEE bo data area for the two IMD, we have found differences on their element tags which causes the duplicate IMD check to NOT detect that there is already an existing FMD.
The bo data area of the 1st IMD that has been finalized have an extra element tag of ‘’ and the 2nd IMDthat has been finalized has do not have that extra element tag of ‘’.
 

EXPECTED BEHAVIOR
-----------------------
It is expected that the duplicate imd check would find these kinds of duplicates.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Add an IMD
2. Add a second identical IMD using a child BO such as D7-InitialLoadIMDScalar
3. Notice that the second IMD is not stopped in the duplicate IMD check VEE Rule

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot save processing time by avoiding processing on duplicate IMDs.

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms