Usage Transaction Gives System Error
(Doc ID 2745347.1)
Last updated on SEPTEMBER 20, 2022
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.6.0.1.0 and laterOracle Utilities Meter Data Management - Version 2.1.0.3 to 2.2.0.2.0 [Release 2.1 to 2.2]
Information in this document applies to any platform.
Symptoms
UT-Usage Transaction
On : 2.6.0.1.0 version, MDM
ACTUAL BEHAVIOR
---------------
Usage Transaction gives system error
When generating a bill segment, the usage transaction shows a system error without any context.
When a previous Usage transaction is present on the UT page, the Start Measurement date time is being fetched from a previous UT end date time and the system tries to check if there is a measurement found for that date time. Ideally this should have been reported as “Start Measurement not Found” but looks like this is not handled when the previous UT is populated. Right now the “Start measurement not found” to do should have been from those UTs where either there is no previous UT populated (because of initial bill) or could have been on manual meters.
EXPECTED BEHAVIOR
-----------------------
Should have been reported as “Start Measurement not Found”
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 |
Cause |
Solution |
References |