TFM Billable Charge Creation Date Is Stamped As TXN_DTTM Instead Of System Date

(Doc ID 2416036.1)

Last updated on JULY 02, 2018

Applies to:

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

Symptoms

On : 2.6.0.1.0 version, ENV - Environment

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

In version 2.4.0.1, 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

Changes

 

Cause

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