System Error Is Being Caused By Back Dated Reads From Field Activities
(Doc ID 2771563.1)
Last updated on OCTOBER 10, 2022
Applies to:Oracle Utilities Meter Data Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.
System error is being caused by back dated reads from field activities
Found out that the system error is being caused by back dated reads from field activities.
During completion process of the field activity in SOM, SOM will try to create an IMD via Create FA IMD completion event.
However since the date/time is back dated, it causes a system error on creation of IMD as it tries to reconcile the estimation reads.
This issue happened a lot during FA replay a few months back, but can still happen on Production now because of back dated data corrections FAs.
Not sure if oracle already seeing this issue and if there is any available patches to allow Create FA IMD completion event to not automatically transition/process an IMD to Finalized state especially if there is a monitor
process involved in the IMD lifecycle. Doing so will allow the activity to complete in SOM, leaving the IMD in Pending letting the monitor batch pick it up for processing.
If it fails, I believe there is a process to manually cover these kinds of issues as part of Billing.
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