Wrong Schedule For COMMITM_FEE Component On Limit 111LMNR232140001 - Root Cause
(Doc ID 2978624.1)
Last updated on OCTOBER 04, 2023
Applies to:Oracle FLEXCUBE Universal Banking - Version 12.3 and later
Information in this document applies to any platform.
After save + auth of point 3 above, the schedule for COMMITM_FEE remains as was initially set by default after limit auth -> multiple monthly due dates starting with 30.09.2023 + bullet (16.07.2024)
Bank wants to correct the limit from production (111LMNR232140001) by updating / modifying / recalc on schedule, comp_calc and any other tables
so that for COMMITM_FEE component only one due_date -> 16.07.2024 (bullet) to remain recorded.
The issue can be reproduced at will with the following steps:
1. insert a new multi-ccy limit and setting COMMITM_FEE (save + auth)
2. vami for attaching the limit to 2 loan accounts (111OTHR232120002 and 111OTHR232120003) -> save + auth
3. commitment amendment for limit in order to:
a) insert a new effective_date (15.07.2024) and RATE_CMT_FEE = 0
b) modify schedule for component COMMITM_FEE in order to have only bullet payment (16.07.2024)
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