A Global Calendar Inherits Holidiays from the Default Calendar During the Project Check-out/Check-in Process
(Doc ID 2881754.1)
Last updated on SEPTEMBER 14, 2022
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 20.12 to 220.127.116.11 [Release 20.12]
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 20.12 to 18.104.22.168 [Release 20.12]
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 21.12 to 22.214.171.124 [Release 21.12]
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 22.1 and later
Primavera P6 Enterprise Project Portfolio Management - Version 21.12 to 126.96.36.199 [Release 21.12]
Information in this document applies to any platform.
After checking out a project to a local SQLite database and adding a new Global Calendar to it, when the project is checked back in the new Global Calendar inherits holidays and exceptions from the Default Calendar of the original database.
Global Calendars should not inherit holidays or exceptions from another Calendar.
The issue can be reproduced at will using the following steps:
- Add a new project and activity. Assign any non-default Global Calendar.
- Check-out the project to a local SQLite database.
- Login to P6 connected to the local database.
- Add a new Global Calendar and assign it to any of the project's activities.
- Check the modified project back into original database.
- Select Enterprise > Calendars from the menu, select the newly created Calendar and click Modify.
- Note that the calendar has inherited holidays from the default calendar.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!