FTP Adjustment Ranges Not Working Properly
(Doc ID 2382388.1)
Last updated on APRIL 13, 2018
Applies to:Oracle Financial Services Funds Transfer Pricing - Version 8.0.5 and later
Information in this document applies to any platform.
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Adjustment ranges were found not to be working properly in a standard FTP 8.0.5 process (with Adjustment Rule defined within).
Case 1: If a range is used for the Reference Term (in the Adjustment Type Selection screen) to calculate Basis Risk Costs, Liquidity Adjustments, Pricing Incentives or other adjustments, all other deals which are not in the specific range are populated with values as well.
Case 2: For two or more ranges, all other are populated with the values of the upper / lower range.
All reference terms were tested: Original Term, Repricing Frequency, Remaining Term, Duration, Average Life and the behavior is the same in all cases.
The problem seems to only appear if the ranges are incomplete, in the case in which the engine populates where it should not. The rule behaves properly if all possible values within their term ranges are accounted for, i.e. the first range could be "0" to "xxx" and the last could be "xxx" to "9999999".
Deals that are outside of range(s) shouldn't be populated with any values.
STEPS TO REPRODUCE
The issue can be reproduced at will with the following steps:
- Login to OFSAA -> FTP
- Define a standard FTP Process with Adjustment Rule of type Liquidity Adjustment and set Range type parameter.
- Run FTP Process and verify results.
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