How to Calculate Memory Requirements for Risk Manager and Transfer Pricing
(Doc ID 167127.1)
Last updated on MARCH 09, 2018
Applies to:Oracle Financial Services Applications (OFSA) 4.5
Oracle Transfer Pricing - Version: 4.5 to 4.5.39
Oracle Risk Manager - Version: 4.5 to 4.5.39
Information in this document applies to any platform.
Checked for relevance on 16-Jul-2009.
Clarification is needed on the formula provided in the 4.5 OFSA Installation and Configuration Guide in Chapter 6 for calculating memory requirements for Oracle Risk Manager (RM) and Transfer Pricing (TP) processing. The formula is as follows:
(n events * e financial elements * record length)
where the record length = 408 and the maximum number of structures that can be modeled (n events * e financial elements) is 16,000.
Specifically, the following items need to be addressed:
1. "n events" refers to any event. Examples include time of payment, repricing, and maturity. For a payment event, do you need to account for the maximum number of payments for a record? For example, a 30 year loan that reprices every year and has a monthly payment frequency will have 30 repricing events and 360 payment events. What is "n events" in this case?
2. Does "e financial elements" refer only to the cash flow related financial elements? What is the list of potential financial elements referenced in the "e financial elements" component?
3. Since the maximum number of structures (n events * e financial elements) is 16,000, is the maximum memory required = 16,000 * 408?
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