My Oracle Support Banner

InterestRateCalculation BR LeapYear ReferenceDate Calculation Goes Back 1 Year Instead Of Forward (Doc ID 2772523.1)

Last updated on APRIL 29, 2021

Applies to:

Oracle Insurance Policy Administration J2EE - Version 11.0.2.20 and later
Information in this document applies to any platform.

Symptoms

On : 11.0.2.20 version, General

ACTUAL BEHAVIOR
---------------
InterestRateCalculation BR LeapYear ReferenceDate calculation is going back 1 year not forward.
The InterestRateCalculation Business Rule LeapYear functionality has an option to specify a MethodReferenceDate which is used to determine if leap year interest or non leap year interest should be used.
The determination if the denominator should be 365 or 366 in the interest calculation should go forward a year, but the code is going back to the previous year when using the ReferenceDate configuration.
E.g. 3/1/2019 to 3/1/2020 should be 366 days Actual result 3/1/2019 to 3/1/2018 the code is using 365.


EXPECTED BEHAVIOR
-----------------------
E.g. 3/1/2019 to 3/1/2020 should be 366 days Actual result 3/1/2019 to 3/1/2018 the code is using 365.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run valuation on 3/31/2019 for interest calculated since 3/1/2019 with a reference date of 3/1/2019 in the InterestRateCalculation rule.



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
Cause
Solution
References


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