My Oracle Support Banner

What are the Mapping Requirements for INSTRUMENT_TYPE_CD for EPM? (Doc ID 2642265.1)

Last updated on MARCH 02, 2020

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version 8.0.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 Enterprise Performance Management (EPM)


Currently have both loans and lines of credit mapped into the Loan Contracts table. While it might make sense to map the lines of credit into the Credit Lines product processor table, for various reasons would like to leave those instruments in the Loan Contracts table (i.e. existing GL Recon configuration).  Would like to use an existing OFSAA Portfolio field to flag lines of credit so they may be excluded from cash flow edits and cash flow FTP processes. Would there be any issue with using the INSTRUMENT_TYPE_CD 160 (Credit Lines) to identify records from INSTRUMENT_TYPE_CD 180 (Loan Contracts)?  Typically have made the INSTRUMENT_TYPE_CD mapping consistent with the actual product processor table, but not sure what purpose that serves. Will not load the PAYMENT_SCHEDULE table with records related to the credit line instruments, so that broken linkage should not be an issue. While using the results area for reporting, this is limited to the Common Account Summary and FTP Account Summary fact tables.


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.