FTP 8.1: Adjustment Rule Is by Default Calculating on Adjustment Effective Date
(Doc ID 2852284.1)
Last updated on MAY 23, 2023
Applies to:
Oracle Financial Services Funds Transfer Pricing - Version 8.1.1.1 to 8.1.1.1 [Release 8.1]Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Oracle Financial Services Funds Transfer Pricing（FTP）
Oracle Financial Services Profitability Management (PFT)
Symptoms
After upgrading from V6 to V8.1.1.1, Adjustment Rule is by default calculating on 'Adjustment Effective Date' instead of 'Last Reprice Date'.
User found from Document ID 1911858.1 Is ADJ_EFFECTIVE_DATE Used Automatically for an Adjustment Rule When the Column Is Populated? that there was a product enhancement for Adjustment Rules to refer Adjustment Effective Date when it has not-null value and ignore the date assignment configuration done in the rule.
User believes this was a major shift in behavior from V6 and impacted the business configurations severely as there were some adjustment rules set up to refer Last Reprice Date in their current 6.1.0.3.
On the same record, basis risk adjustment rule operates on last reprice date and liquidity adjustment rule operates on adjustment effective date in their current production.
With this product enhancement, now basis risk rule have also started to refer adjustment effective date, which is not an acceptable outcome for business.
Hence, user expected Adjustment Rule is by default calculating on 'Last Reprice Date' on 8.1.1.1.
Changes
Upgrading from V6 to V8.1.1.1.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |