Disaggregation Not Working as Expected
(Doc ID 3038869.1)
Last updated on AUGUST 09, 2024
Applies to:
Oracle Financial Services Revenue Management and Billing Cloud Service - Version 5.1.0.0.0 to 5.1.0.0.0 [Release 5.0]Information in this document applies to any platform.
Symptoms
The disaggregation is usually run before Monthly Billing and it is giving the disaggregation From Date as the Month's Start date before 6 months.
Scenario:
Account 0000000000000000 ( A1 ) has transactions from 05-JUN-19 to 30-APR-24 which is not billed.
Account 0000000000000000 ( A2 ) has transactions from 17-APR-19 to 30-APR-24 which is not billed.
Account 0000000000000000 ( A3 ) has transactions from 13-AUG-18 to 30-APR-24 which is not billed.
Issue:
When run the disaggregation with from date 01-Nov-2023, the Transactions of the Account A1 and A2 are getting fully disaggregated and going the staging table but for A3, only the transactions on or after 01-Nov-2023 is going to Stage.
Query results AFTER disaggregation.
select acct_nbr,min(txn_dttm),max(txn_dttm),bo_status_cd FROM CI_TXN_DETAIL where txn_header_id='1092' group by acct_nbr,bo_status_cd;--
0000000000000000 13-AUG-18 31-DEC-18 IGNR
0000000000000000 01-JAN-19 31-OCT-23 COMP
select acct_nbr,min(txn_dttm),max(txn_dttm),bo_status_cd FROM CI_TXN_DETAIL_stg where txn_header_id='1092' group by acct_nbr,bo_status_cd;--
0000000000000000 05-JUN-19 30-APR-24 UPLD
0000000000000000 17-APR-19 30-APR-24 UPLD
0000000000000000 01-NOV-23 30-APR-24 UPLD ;
This is causing the logic to fail, to ignore, duplicate transactions ( using a Custom Batch ) since the disaggregation is not working as expected.
The expectation is that for A3 the disaggregation should work for all the transactions (same as A1 and A2).
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 |