Aggregation Issue With TFM When Billable Charge Chars Are Updated
(Doc ID 2568318.1)
Last updated on JULY 26, 2019
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
Aggregation issue with TFM when billable charge chars are updated.
For our implementation, we need to identify certain TFM billable charges for further processing. We are stamping a characteristic to identify such TFM billable charges on trial executions, characteristics are later removed after trial execution and re-created on next trial if billable charges are qualified for processing again.
We observed that if characteristics are added thru DTO, main table (CI_BILL_CHG) gets updated for VERSION(+1), TOU_CD (updated to null), CHG_TYPE_CD (updated to null). This is causing TFM to create a new billable charge instead of aggregating to existing billable charge if new similar transactions come on same account.
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