Prepayment Rule Applied to Products Outside the Defined Node in ALM 8.0.5
(Doc ID 2532631.1)
Last updated on MARCH 19, 2021
Applies to:
Oracle Financial Services Asset Liability Management - Version 8.0.5 to 8.0.6.1.0 [Release 8]Information in this document applies to any platform.
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Symptoms
ACTUAL BEHAVIOR
On 8.0.5 version, Prepayment rule defined on one node in hierarchy is also applied to products in other nodes (other than child nodes).
Prepayment cashflows are also generated for those products which are not a part of any node where Prepayment assumption is defined. Neither has prepayment been defined at leaf level for such products.
EXPECTED BEHAVIOR
FE 180 shouldn't be generated in ALM result tables for products which don't have prepayment defined.
STEPS TO REPRODUCE
The issue can be reproduced at will with the following steps:
1. Define prepayment for few products.
2. Run ALM process with prepayment.
3. Check if FE 180 is generated as part of the process for products which do not have prepayment applied.
Changes
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 |