VAMI Principal Increase And Amend Payment Schedule Did Not Work Ok
(Doc ID 2620890.1)
Last updated on DECEMBER 31, 2019
Applies to:Oracle FLEXCUBE Universal Banking - Version 12.3 and later
Information in this document applies to any platform.
On : 12.3 version, Production Support-SET
VAMI principal increase and amend payment schedule did not work ok
User were able to do VAMI for principal increase and in the same VAMI to adjust payment schedule by increase monthly due payment for principal.
System keep for DSBR only 1 row in CLTB_ACCOUNT_COMP_SCH and for any Principal increase users update dsbr_amount on the line with first due date = value date.
After Patch-set --
Behavior for DSBR was changed. For each VAMI principal increase, new DSBR line is created by the system in CLTB_ACCOUNT_COMP_SCH with new disbursement date.
In order to avoid errors regarding disbursement amount, user has already corrected DSBR tables for all active loans through C38429.
With new behavior of registering DSBR, now VAMI for principal increase + in the same VAMI to adjust payment schedule, system generates error info "Invalid Amount.
Amount has greater precision than what is allowed for the currency RON" during explode.
The problem appear when system try to calculate amount for bullet and calculate a wrong amount with many decimals. Even system return this err message info, if user continue to save and auth VAMI, after auth bullet is adjusted ok.
This wrong behavior is the same for migrated and DSBR corrected loans but also for new loans created after patcheset promotions for which no corrections are applied.
User have many cases like that in production and as workaround with ok behavior user found solution to do 2 different VAMI instead of 1 (VAMI PI and allocate increased amount only on bullet + VAMI to reallocate payment from bullet to monthly schedule due). This workaround will affect in case Principal increase need to be reversed because another subsequent event will exist.
System should calculate the correct amount.
The issue has the following business impact:
Due to this issue, the system is not able to save and auth the VAMI amount calculation is not correct.
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