Prior Day Data Between Mortgage Instrument And Break Funding Charges Not In Sync
(Doc ID 2967085.1)
Last updated on AUGUST 24, 2023
Applies to:
Oracle Financial Services Funds Transfer Pricing - Version 8.0.7.4.0 and laterInformation 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)
Goal
On FTP 8.0.7.4 version, Prior day data between Mortgage instrument and Break funding charges not in sync
When data moves from fsi_d_mortgages to fsi_d_break_funding_charges for partial breaks (Type 2 and type3), the last/next reprice dates of the previous record is being set to same as the last/next reprice date of the current record. This is creating a problem identifying real breaks (e.g., a loan which is repriced earlier than planned).
During Partial break detection system calculates “LAST_REPRICE_DATE” and “NEXT_REPRICE_DATE” using below logic, but this is not aligned with Mortgage data during Roll over scenario of arrangements.
NEXT_REPRICE_DATE
-----------------
case when as_of_date = L_PRIOR_PERIOD_DATE
then case when next_reprice_date <= L_AS_OF_DATE
then case when (decode(reprice_freq_mult,'M',
add_months(next_reprice_date, reprice_freq),'D',next_reprice_date + reprice_freq,
add_months(next_reprice_date, reprice_freq * 12))) > maturity_date
then maturity_date
else
decode(reprice_freq_mult,'M',
add_months(next_reprice_date, reprice_freq),'D',next_reprice_date + reprice_freq,
add_months(next_reprice_date, reprice_freq * 12))
Solution
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
| Goal |
| Solution |
| References |