My Oracle Support Banner

High Check Exception Not Generated if Low Isn't Executed Even if the High Check Fails (Doc ID 2529497.1)

Last updated on OCTOBER 04, 2022

Applies to:

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


On : version, Environment

Hi-Check exception not generated and only UT log entry is created

Issue description : When a UT is created with usage greater than the threshold defined in the Hi-low check usage rule, Hi-check exception is not generated. However, a log entry is created in the UT log with ‘Current usage high check failed on last year historical usage’ error message

However, UT goes out in Sent status, not stopping due to the error as expected.


 ‘Current usage high check failed on last year historical usage’ error message

The issue can be reproduced at will with the following steps:
1. Set up Dvc, DC, MC, similarly valued measurements, SP, IE, US and UTs for a year which will go out with generally the same usage
2. Add the "next" months measurement with value outside the expected range and make sure it is finalized.
3. Add the "next" months UT [WITHOUT DESIGNATING PREVIOUS USAGE ID] and expect it to fail because it is outside the range allowed by the Hi/Low Usage Check Usage Rule.
4. Notice the record goes to "Sent" status anyway even though there is an error in log for last year hi check it doesn't move on to check previous usage id so it doesn't fail.

The issue has the following business impact:
Due to this issue, users cannot prevent high usage outside the range from being included in bills.


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

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