Maximum Hours Exceeded Exception for Interval Interpolation VEE Rule
(Doc ID 2189752.1)
Last updated on SEPTEMBER 24, 2022
Applies to:
Oracle Utilities Meter Data Management - Version 2.1.0.3 to 2.1.0.3 [Release 2.1]Information in this document applies to any platform.
Symptoms
**Any examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
MDM - Oracle Utilities Meter Data Management
VEE - Validation Estimation and Editing
SP - Service Point
MC - Measuring ComponentReplace this with note box text.
**Disclaimer:** This KM article may include the following abbreviations:
MDM - Oracle Utilities Meter Data Management
VEE - Validation Estimation and Editing
SP - Service Point
MC - Measuring ComponentReplace this with note box text.
On Oracle Utilities Meter Data Management version 2.1.0.3 the Interval Interpolation VEE rule is unable to trigger Maximum Hours Exceeded Exception when Maximum Hours to Interpolate have been exceeded.
Steps to Reproduce
Pre-setup:
Configure Interval Interpolation VEE Rule as below.
- Maximum Percentage Missing Intervals : 100
- Estimate if Not Attached to SP : Estimate
- Maximum Hours to Interpolate : 2
- Condition Value for Estimates Created : System Estimate
- Exception Type: Maximum Hours Exceeded
- Severity: Issues
Steps:
- Create Device, Device Configuration, and Interval Measuring Component with 15 mins SPI, Interval measuring component, SP and Install Event.
- Add the following Readings on interval MC
- Configure 32 intervals of data, with 9 intervals as missing i.e. (2hours 15mins). From 2014-06-15-10.45.00 to 2014-06-15-18.45.00
- Verify that a ‘Maximum hours exceeded exception’ is not occurred.
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 |