How to Use % Tolerance causing Incorrect Exception During Execution of High Low VEE Rule
Last updated on NOVEMBER 29, 2016
Applies to:Oracle Utilities Meter Data Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
In Meter Data Management, the High/Low Check VEE Rule the Tolerance Percent (%) is calculated incorrectly causing the validation to not work as expected, triggering an exception when one is not expected.
Steps to Reproduce
- Create Device, Device Configuration and Scalar Measuring component and connect the device.
- Verify that Allow Negative Consumption is set to 'Allowed' on Measuring Component Type.
- Attach High/Low Check VEE Rule to the Measuring Component with the following parameters:
- High Low Check = Both
- High/Low limits from master config= No
- High Tolerance(%) = 600
- Low Tolerance(%) = 15
- Required Historical Data (%) Basis = IMD Start/End
- Required Historical Data(%) = 10
- Historical Pre-Window = 7
- Historical Post-Window = 7
- Allowed Historical User Edited Data(%) = 100
- Allowed Historical System Estimated Data(%) = 100
- Historical Look First = Last Year
- Comparison Method = Average
- Create Measurements as follows: (Measurement Date/Time(MM-DD-YYYY-HH24.MI.SS); MSRMT_VAL; Reading)
- 04-08-2015-01.00.00; 0; 1077
- 06-05-2015-01.00.00; -500; 577
- 08-04-2015-01.00.00; -833; 99744
- 10-03-2015-01.00.00; -285; 99459
- 06-03-2016-01.00.00; 2317; 1776
- Submit an Manual IMD as follows: Date/Time=08-03-2016-01.00.00, Value=1249
- Verify that the IMD goes into exception due to wrong calculation of high and low values (High Value= 5067.416667, Low Value= -140.915833)
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