Inconsistent Behavior With Disaggregation Batches
(Doc ID 2690629.1)
Last updated on JULY 21, 2020
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, BT - Batch
Inconsistent behavior with Disaggregation batches
Customer had the following requirement:
They have a requirement to do disaggregation at person level. For that, they are putting disaggregation request for all the accounts under the person.
They have custom screen that is developed to create disaggregation request for a person.
Recently, they had come across an issue where all the accounts status are not marked to COMPLETE in CI_TXN_DISAGG_REQ table after execution of all the disaggregation batches.
1. Create disaggregation request from the custom UI for the person. Disaggregation request will be created for all the accounts under the person.
2. Run C1-BSEGD
3. Run C1-PNBD
4. Run C1-IDENT
5. Run C1-PDTXN
6. Run C1-TXNCU
7. Run C1-DRSUA
a. run the TFM, billable charges got created
b. billing was executed
c. then run disagg
d. cancel the billable charge
e. run disagg again to generate disagg request for particular person id
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