UT Corrections Generated For KW Reads Inappropriately Due To IMD Start Date/Time

(Doc ID 2349294.1)

Last updated on APRIL 19, 2018

Applies to:

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

Symptoms

Incorrect Subsequence Correction activities are creating based on the UT (usage transaction) start and end periods instead of looking at the UT scalar details start or end date/times.

Scalar IMDs trigger UT Correction Activities based off whether the IMD Start-End overlaps with the Usage Period of an existing Usage Transaction. KW reads are stamped with an end date/time for when the peak occurred, but are also stamped with a start date/time of the previous peak quantity. This can cause this month's peak demand to be mistaken as new read for last month, thus causing the UT Correction.

Steps To Recreate

  1. Create Device, Device Configuration and two Scalar Measuring Components (one with KWH and another with KW UOMs).
  2. Create a Service Point and install the above meter.
  3. Create the following reads on the first measuring component (i.e. KWH).
    09-29-2017 10:51:35AM
    10-30-2017 09:37:04AM
  4. Create the following reads on the second measuring component (i.e. KW).
    09-29-2017 10:51:35AM
    10-30-2017 09:37:10AM
  5. Create a Usage Group and add the two Get Scalar usage rules with KWH and KW UOMs.
  6. Create a Usage Subscription.
  7. Create a Usage Transaction
    Interval Measuring Component:
    Start Date/Time: 09-29-2017 10:51:35AM
    End Date/Time – From: 10-30-2017 12:00:00AM
    End Date/Time – To: 10-30-2017 11:59:59PM
    Scalar Measuring Component:
    Start Date/Time: 09-29-2017 10:51:35AM
    End Date/Time – From: 10-30-2017 12:00:00AM
    End Date/Time – To: 10-30-2017 11:59:59PM
  8. Move the Usage Transaction in ‘Sent’ state.
  9. Create an IMD on first scalar measuring component (i.e. KWH) from 10-30-2017 09:37:04AM to 11-30-2017 08:28:49AM.
  10. Usage Transaction Correction Processor activity is created for the above IMD which is not valid.

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