My Oracle Support Banner

Usage of IDENTITY_CODE in FSI_D Tables for EPM Applications (Doc ID 2531783.1)

Last updated on OCTOBER 28, 2019

Applies to:

Oracle Financial Services Asset Liability Management - Version 6.0 and later
Oracle Financial Services Balance Sheet Planning - Version 6.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Balance Sheet Planning (BSP)
Oracle Financial Services Enterprise Performance Management (EPM)


Currently using the FSI_D tables as processing area to feed external engines (QRM, Moody's analytics). The problem with the existing solution is that there is no load_run_id or n_run_skey to hold multiple version of instrument information for same date.
Please note that currently only the ALM processing area table and not ALM application.
When exploring the table structure of FSI_D tables, it is found that the column IDENTITY_CODE contains the MIS DATE in char form. The AS_OF_DATE field to holds extraction date.
Can usage of the column - IDENTITY_CODE be customized to store the load run identifier?
Will this usage impact any potential usage of CFE or BSP application in future?


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.