PAXPREPR: Task Dates Incorrect when Creating a Project that Includes a Leap Year
Last updated on MARCH 08, 2017
Applies to:Oracle Project Foundation - Version 12.1.3 and later
Information in this document applies to any platform.
Task and transaction control end dates are not correct on newly created projects. The dates do not take into consideration leap years. For example, a template or project dated 01-JAN-07 through 30-SEP-07, when copied in 2008, results in the start date for tasks and transaction controls is 01-JAN-08, but the end date is 29-SEP-07 not 30-SEP-07 due to leap year. The project date appears to populate from the quick entry form so they are correct.
The Foundation User's Guide says:
"Oracle Projects shifts the effective dates of the project level options by the number of days between the start date in the project template and the start date that you enter. It shifts the effective dates of the task level
options by the number of days between the new task start date and the start date of the task in the project template. If you do not enter start and finish dates in Quick Entry fields, Oracle Projects creates the new project
and its tasks with the same dates as the project template."
On small enough projects, this would not be overly difficult to change, but on projects that have thousands of tasks, it is not feasible to change the date by one day on all these tasks. This functionality would require the
customer to create all new templates in leap years as there will be 1 more day to account for.
This same behavior is seen in the self service application.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms