Deagg Request is Disaggregating Transactions which are Linked to Cancelled Billable Charges
(Doc ID 2410383.1)
Last updated on MARCH 07, 2019
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.5.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Revenue Management and Billing (ORMB) v2.5.0.3.0 against Oracle Utilities Application Framework v4.3.0.1.0, Disaggregation Request is disaggregating transactions which are related to Cancelled billable charges.
ACTUAL BEHAVIOR
-------------------------
Deagg is disaggregating the transactions that are linked to cancelled billable charges
EXPECTED BEHAVIOR
---------------------------
Canceled billable charges should have no impact or options should be there to exclude such charges
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a disaggregation request for the aggregated transaction which contain a few cancelled billable charges.
2. Run the C1-DSTG->C1-IDENT -> C1-PDTXN -> C1-TXNCU -> C1-DARSU/C1-DRSUA.
3. Observe the following:
a. The Disaggregation request is disaggregating transactions which are related to Cancelled billable charges.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use Deagg feature correctly.
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 |