My Oracle Support Banner

TFM Billable Charge Creation Date Is Stamped As TXN_DTTM Instead Of System Date (Doc ID 2416036.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Financial Services Revenue Management and Billing - Version and later
Information in this document applies to any platform.


On : version, ENV - Environment

Actual Results:
TFM Billable Charge Creation Date is stamped as TXN_DTTM instead of system date

In version, if a billable charge is created on a transaction having txn_Dttm in past, it still had CI_BILL_CHG.CRE_DT as system date (the day billable charge is created) while after upgrade, this is broken and it is stamping CI_BILL_CHG.CRE_DT as CI_TXN_DETAIL.TXN_DTTM and its impacting all the CM codes which were written based on this logic.

It needs to have CRE_DT as system date when billable charge was created.

Expected Results:
TFM Billable Charge Creation Date should be stamp as system date.

Steps to reproduce
Execute TFM aggregation flow




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.