Contract End Date Not Calculated Correctly when it falls in a leap year (Doc ID 2293756.1)

Last updated on AUGUST 04, 2017

Applies to:

Oracle Service Contracts - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Administration

ACTUAL BEHAVIOR
---------------
Whenever the start date on the service contract is 28th Feb and ends in 2020 which is a leap year, and the duration is in period of year, it adds an extra day to the contract duration.

EXPECTED BEHAVIOR
-----------------------
Correctly calculate contract end date when it falls in leap year

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Go to service contract manager-> launchpad-> search any active contract. Open the contract for update. Change the start date to 28th feb 2017 and duration to 3 year. Now end date comes up as 28th feb 2020 but it should be 27th feb 2010.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms