Alignment Exception For A Usage Transaction Does Not Get Resolved When Required Measurement Is Added
(Doc ID 2795256.1)
Last updated on SEPTEMBER 22, 2022
Applies to:Oracle Utilities Customer to Meter Base - Version 126.96.36.199.0 and later
Oracle Utilities Meter Data Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Meter Data Management
Alignment Exception for a Usage Transaction does not get resolved when required measurement is added
Usage Transaction was created with a Usage Calculation Group with two types of Usage Calculation Rules (Alignment and Delay Calculation Rule and Daily Scalar-Usage Calculation). Bill request submitted with three-day window for the end date/time from/to. When required measurement cannot be retrieved from the device, Alignment Exception is raised only when Automated Retry is set to ‘Yes’ and Retry Until Date/Time is set to a future date. If UT is created with Automated Retry set to ‘No’ or have Retry Until Date/Time as a past date, then Alignment Exception is not raised. Also, when Alignment Exception is raised, after the required measurement is created Alignment Exception does not get resolved and UT gets stuck in an ‘Issue Detected’ state. Below are the two scenarios that have this issue.
Scenario 1: Alignment Rule with missing measuring during the billing window
Scenario 2: Alignment Rule with Meter Exchange and missing measurement on the removal date/time
More detail and screenshots on the issue can found on the attached document.
Frequent Scalar MC (xxxxxxxxxxxxx) does not have any end read for the period
The issue can be reproduced at will with the following steps:
1. Create a Device and Device Configuration with three scalar measuring components
2. Create a Service Point and install the above meter>
3. Create 4 Usage Calculation Rules
Alignment and Delay Calculation Rule
Three Daily Scalar Usage Calculation Rule for each scalar channel
4.Three Daily Scalar Usage Calculation Rule for each scalar channel
5.Create a Usage Subscription linked to the Service Point and the Usage Group above.
6.Load reads with date/time of the UT start date/time for all three required scalar channels and DO NOT load reads during the three-day billing window.
7.Create a Usage Transaction with Automated Retry is set to ‘Yes’ and Retry Until Date/Time is set to a future date
8.Usage Transaction is created and processed. Usage Transaction goes into an ‘Issue Detected’ state with Alignment Exception and Measurement Retrieve Exception.
9.Load reads with date/time of the UT end date/time-to (day 1 of the billing window) for all three required scalar channels and recalculate the UT
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