Is There Any FTP Processing Performance Issues Using Daily Terms for Each IRC?
(Doc ID 2464798.1)
Last updated on OCTOBER 30, 2018
Applies to:Oracle Financial Services Funds Transfer Pricing - Version 6.1 and later
Information in this document applies to any platform.
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Question 1: Is it feasible to define daily terms for each Interest Rate Curve (IRC), for a long period like 7200 days? For example, 200 IRCs would translate to 1.44 million rows for each as_of_date.
Such a structure was inserted in one curve as a test and the User Interface (UI) could not open and load the same.
Additionally, could defining the terms structure in a way that they are always expressed in days (and not in years) have a negative impact on performance of the process? For example, writing 7300 Days instead of 20 Years.
FTP processes were run on such term structure, and they were already quite slow, despite the minimal amount of data we introduced for testing.
What is the impact on performance of the FTP Process and what are the limitations of the FTP engine regarding IRCs?
Question 2: Are there any definite limitations about how many terms can be supported on a rate? Is the performance better if the terms are expressed in days/months/years, not just days?
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