Usage Transaction Correction Processor Activity Is Not Created for Scalar Read
(Doc ID 3059642.1)
Last updated on MARCH 19, 2025
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.9.0.1.1 to 2.9.0.1.1 [Release 2.9]Oracle Utilities Meter Data Management - Version 2.5.0.1.1 to 2.5.0.1.1 [Release 2.5]
Information in this document applies to any platform.
Symptoms
Usage Transaction Correction Processor Activity are not being Created for Scalar Reads.
After upgrading to v2.9.0.1.1, there are situations where scalar reads no longer create Usage Transaction Correction Processor activities as they used.
This issue affects initial load, manual and system scalar IMDs, because they share the same algorithm D1-TRAN-UT.
However, this is not a consistent behavior. You can find scenarios where scalar reads do created correction activities.
Changes
This was caused by the patch for the following bug fix:
Unpublished Bug 34468080 - COPY OF BUG 34468076 - COPY OF BUG 34414511 - USAGE TRANSACTION CORRECTION PROCESSOR ACTIVITY IS NOT BEING CREATED
The end date time used by the added query to find scalar measurements can contain one of two values, Date for UT and Date from IMD. This end date is being used to find eligible Usage Subscription.
This date should not be used by the query to find scalar measurements. The query to find scalar measurements should always use the to_date from the IMD.
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 |