Usage Transaction To Dos Are Auto-closed Even When They Are In The Being Worked On State
(Doc ID 2324812.1)
Last updated on OCTOBER 01, 2022
Applies to:
Oracle Utilities Meter Data Management - Version 2.1.0.3 to 2.2.0.1.0 [Release 2.1 to 2.2]Information in this document applies to any platform.
Symptoms
When a usage transaction is in issue detected state and a To Do associated to the usage transaction is Being Worked On, the usage transaction monitor batch picks up the usage transaction, closes the To Do being worked on and creates a new one. The monitor should skip the usage transaction when a linked To Do is being worked on.
Steps To Recreate
- Create a usage transaction in issue detected state a. Ensure that auto retry is YES b. Retry until date is future date c. Ensure that a To Do is created in open status
- Assign the created to do a. Verify that the to do status is being worked on
- Run the Usage Transaction Issue Detected Monitor (D2-UTID) batch a. Ensure that execution time is later than the UT’s Retry Date
- Verify that the usage transaction was processed a. To do being worked on is completed b. New To do is created
Changes
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 |