Orchestrator Gives A System Error When It Executes Check For Measurement
(Doc ID 2724097.1)
Last updated on SEPTEMBER 25, 2022
Applies to:
Oracle Utilities Customer to Meter Base - Version 2.7.0.3.0 and laterOracle Utilities Meter Data Management - Version 2.3.0.2.0 to 2.3.0.2.0 [Release 2.3]
Information in this document applies to any platform.
Symptoms
On : 2.7.0.3.0 version, Framework
ACTUAL BEHAVIOR
---------------
Orchestrator gives a System Error when it executes Check for Measurement
We do not allow estimates to be used as a start read or a stop read. This is a regulatory requirement because they cannot have their initial and final bills get billed using estimate reads.
For our Enable and Disable Service orchestrators, we have defined our Check for Measurement Algorithm such that the lowest condition range for the bottom measurement condition will be at 500000 (which is the lowest range for the regular condition)
In this scenario,
- There is an existing estimate read on 9/23/2020
- Customer stops service on 9/23/2020
- The disable service gives a system error
The system should not be giving a system error and should create the appropriate activity.
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 |