Discarded Usage Transaction Seeder Does Not Nudge Usage Request Status To Error
(Doc ID 2743776.1)
Last updated on JANUARY 19, 2021
Applies to:Oracle Utilities Customer to Meter Base - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 2.7]
Information in this document applies to any platform.
On Oracle Utilities Customer to Meter Base 18.104.22.168.0 version, Meter Data Management
When a bill segment creates a usage request, it can create a usage transaction seeder in Error status due to some error. Usage request is in Awaiting Bill Determinant status. Bill segment is in error with 'UT is in non-final status, refer to usage request xxxx for details'. The issue is when UT seeder is discarded, usage request status remains Awaiting Bill Determinant status, bill segment remains the same error. The expectation is Usage request should be nudged to transition to ERROR status and bill segment should no longer shows UT is in non-final status error.
It seems that X1-TRNUSGREQ (Transition Related Usage Request from UT) is missing from D2-UsgTranSeeder BO Discard status. It is currently plugged in D2-UsageTransaction BO Discard status.
This error cause CCB BILLING batch can not re-generate bill segments due to usage requests are in waiting bill determinants status.
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