False Subsequent Correction Notifications Created In MDM - Due To Incorrect Start Date/Time On Usage Transaction
Last updated on DECEMBER 18, 2016
Applies to:Oracle Utilities Meter Data Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
On Oracle Utilities Meter Data Management 18.104.22.168 version, Usage Transactions are created with incorrect Start Date/Time causing false subsequent correction notifications.
Meters that have multiple registers have read times on the registers that are slightly different. Due to the way MDM calculates the start Date/time and the End/Date Time on usage transactions, false subsequent correction notifications are sent to CCB, resulting in over 5,000 false To-Do's in CCB. Every Month (On meters with multiple registers) the previous periods usage transaction will transition to subsequent correction due to the different times of the reads on the multiple registers. When creating the next usage transaction, MDM should look at the latest read Date/Time, rather than the earliest read Date/Time to determine the start Date/Time of the subsequent usage transaction.
It is expected that the UT calculation will not create UT corrections for previous UT period when reads are consecutive, not replaced
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