My Oracle Support Banner

OBCL 14.7.0.5.0:DEV: EXPY Event Is Not Triggered On DD Expiry Date - USNSBT1212010503 (Doc ID 3069826.1)

Last updated on FEBRUARY 03, 2025

Applies to:

Oracle Banking Corporate Lending - Version 14.7.0.0.0 to 14.7.0.0.0 [Release 14]
Information in this document applies to any platform.

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
OBCL 14.7.0.5.0:DEV: EXPY event is not triggered on DD expiry date - USNSBT1212010503


EXPECTED BEHAVIOR
-----------------------
EXPY event need to triggered on DD expiry date

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Issue: EXPY event is not triggered on DD expiry date - USNSBT1212010503
2.Book backdated revolving facility for 100M USD for two years
3.Collect COMFEE and UTILFEE monthly once
4. Book backdated two revolving loans for more than one month
5. Run EOD Till first repayment date for FEE
6. Run two more EOD's
7. Perform CAMD and change DD expiry date to next to next working day
8. Perform Fee amendment and delete all the future unpaid schedules and keep one schedule with start date as DD termination date (Which is same as DD expiry date)
9. Do future dated prepayment for loans with value date Termination date (Same as DD expiry date)
10. Run EOD till expiry date

Changes

  Changes by Adding validation don’t allow the FWDLIQD on or after the EXPY event.
 also validation present to restrict the FWDVAMI after the EXPY date and Modified the same don’t allow the FWDVAMI on or after the EXPY date.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.