Disaggregation Causing Orphans in Billable Charge Child Tables
Last updated on DECEMBER 30, 2015
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, DB - Database, the TFM disaggregation process deletes billable charges that are associated to the transactions. The deletions occur in the main billable charge table, its key and SQ tables.
This results in records in the characteristic and calculation line tables being orphaned.
The issue can be reproduced at will with the following steps:
1.Run TFM disaggregation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms