My Oracle Support Banner

FRY 14M: MDRM 'CCFLM947': Missing Logic To Identify Recent Date In Case Of Multiple Write Downs: (Doc ID 2597904.1)

Last updated on NOVEMBER 19, 2019

Applies to:

Oracle Financial Services - Regulatory Reporting for US Federal Reserve - Lombard Risk Integration Pack - Version 8.0.6 and later
Information in this document applies to any platform.

Symptoms

FRY14M: Schedules A1 and B1 Cell Id: M947-Loss/Write down date requires to report the date on which the loss or write-down was incurred. If multiple write-downs occurred in a given month, report the date of MOST RECENT WRITE-DOWN for that month

Measure logic used in HRA1054 is just A_WRITE_OFF_DATES.N_DATE_SKEY"

A_WRITE_OFF_DATES.N_DATE_SKEY is joined in DE as mentioned below:

"LEFT OUTER JOIN DIM_DATES A_WRITE_OFF_DATES ON A_WRITE_OFF_DATES.N_DATE_SKEY = FCT_ACCT_WRITE_OFF_DETAILS.N_WRITE_OFF_DATE_SKEY"

Solution is using n_date_skey joins with write off date skey only as the measure for the reported MDRM, hence the logic to pick the latest write off date in case of multiple write offs in a month is missing.

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


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