
P6 Professional 25.12 was released in late December 2025. In keeping with past years release cadence, Oracle released an update to P6 Professional. Here’s a look at what the new features are in P6 Professional 25.12 and some of the bugs that have been addressed.
P6 Professional 25.12 – New features
Improved Flexibility and Control with Global Change
This is a rather helpful feature to eliminate rows of data from your Global Change execution as you can now reduce the need to define complex filters in your layout before starting a global change. In the global change report dialog box, you can now select to apply some changes but not others before committing to the change.
Also, also can preview each of the rows selected by the filter in the global change definition, then individually include or exclude rows before committing the change.
Alert if an Activity’s Status Change Risks Putting Activities Out-of-Sequence
This feature is useful warning that the task’s work update is out-of-sequence; some users may not even be aware of this issue. If you want to be alerted if a change you make to the status of an activity might result in out-of-sequence progress, mark the ‘Warn about out-of-sequence activities’ option on the Assistance tab of the User Preferences dialog box.
Note that this message will show only if you modify an activity manually. The message will not show if an activity is pushed out-of-sequence by Apply Actuals, Update Progress, or any other automated procedure.
It also has triggers that warn and highlight the relationship violated by of out-of-sequence work.To see a list of the predecessors causing the activity to be out-of-sequence, you can click View on the message box. The list also shows each predecessor’s status and their relationship with the activity you are trying to modify.
If you want to prevent further changes you make during the session from triggering the message, you can mark the ‘Do not ask me about this again’ option in the message box.
The message will be triggered in the following circumstances:
- If you try to start or complete an activity whose predecessors with a finish-to-start relationship are not yet complete.
- If you try to complete an activity whose predecessors with a finish-to-finish relationship are not yet complete.
- If you try to start or complete an activity whose predecessors with a start-to-start relationship are not yet started.
- If you try to complete an activity whose predecessors with a start-to-finish relationship are not started.
- If you make any change to a relationship that might put the activity out of progress.
- If you make any change to a relationship between activities that are already out of progress.
Baseline Assignments Imported From XML
When you import a project along with its baselines from an XML file, you can choose whether to import the assignments of baselines as project baseline, primary baseline, secondary baseline and tertiary baseline.
The baselines and assignments must be present in the XML file you import and you must use an import action that allow updates to an existing project. The baseline assignments imported are those that were assigned at the time that the project was exported.
Improved Clarity When Maintaining Baselines
You can view the ID of a baseline when you click on it in the Maintain Baselines dialog box.
Update Baseline According to Multiple Filters
When you update a baseline, you can select whether to update activities that match multiple filters. You can choose whether to update activities that match all filters or activities that match any of the filters you select.
Additional Baseline Variables Added to Report Headers and Footers
Something that could be helpful for documentation purposes is, that you can now include the project baseline, primary baseline, secondary baseline and tertiary baseline in reports by using the appropriate variables in the header and footer of reports created in P6 Professional.
Check Out Baselines with Their Projects
When you check out projects, either to XML or to a local database, you can check out the projects’ associated baselines. Earned value calculations require baseline data, therefore checking out the baselines with the project enables you to evaluate earned value for the checked-out projects.
Two New Fields – Improved Insight into Remaining Time and Effort Required for Scope of Work
Two new fields provide improved insight into the amount of time and effort required to complete the remaining scope of work.
- Estimate Time to Complete divides original duration by scheduled performance index, to provide a projection of the duration required to complete the work based on labor efficiency.
- Estimate Time to Complete – Labor Units divides planned labor units by scheduled per performance (labor units) to provide a projection of the labor effort needed to complete the remaining scope of work.
These new fields aid in assessing labor efficiency, forecasting resource availability, and identifying potential over-run of work due to declining productivity. The new fields are available at activity and assignment levels and can be added as columns in the grid view and the Assignments detail tab of the Activities page.
These columns are also visible on the Earned Value detail tab of the Assignments page. They are also available for filtering, grouping, sorting, bar labels, and activity network box labels.
Improve Efficiency when Loading Large Data Objects in P6 Professional
Transferring large data objects from the database into the computer’s quick-access memory (which we call ‘loading’ the data) can affect P6 Professional performance. Some of the largest data objects used by P6 Professional are calendars, notebooks, and the ‘Notes to Resources’ and ‘Feedback from Resources’ sections on the Feedback detail tab of the Activities window.
Until now, most of these large data objects were loaded when you opened a project, however if a project is extremely large the requirement to load all this data when you open it can cause delays. In certain circumstances it can be more efficient to load such large data objects as and when they are needed.
A new option has been added to the Startup Filters tab of the User Preferences dialog box. If the ‘Load large data objects on demand’ option is switched on, these large data objects will mostly be loaded at a point that causes the least delay when you open a project. If this option is cleared, large data objects will mostly be loaded as they’re needed.
Specifically, if the ‘Load large data objects on demand’ option is switched on:
– All Global calendar data and most Project calendar data is loaded when you log into P6 Professional. Exceptions to the standard definitions of Project calendars (for example irregular non-work time and holidays) are loaded when you open the project, unless the data is required for calculating a column in the selected layout, in which case it is loaded when you log into P6 Professional.
– Notes to Resources and Feedback from Resources are loaded when you select the associated activity, unless either column is visible in the selected layout, in which case they are loaded when you open the project.
– Notebook Topics are loaded when you select the associated activity.
If the ‘Load large data objects on demand’ option is switched off:
– All Global calendar data is loaded when you log into P6 Professional. All Project calendar data is loaded when you open the project.
– Notes to Resources and Feedback from Resources are loaded when you open the associated project, unless the column is visible in the selected layout, in which case the data is loaded when you log into P6 Professional.
– Notebook Topics are loaded when you open the associated project
The ‘Load large data objects on demand’ option is on by default and Oracle recommends you don’t switch it off unless you experience significant delays when opening large projects.
Other Features
Select Multiple Projects to Convert to Baselines
In the Maintain Baselines dialog box, you can select multiple projects to convert each into a baseline of the open project.
‘Load large data objects on demand’ renamed to ‘Large text data fields’
The ‘Load large data objects on demand’ option, on the Startup Filters page of User Preferences, has been renamed to ‘Large text data fields’. The option was introduced in release 25.6, and provides finer control over data loading in P6 Professional.
Improvement to Scheduling/Leveling Log
In the ‘Finish milestone and predecessors have different calendars’ section of the scheduling and leveling log, columns have been added to help you identify the affected predecessor activities. In addition to the name and ID of the milestone activity, its owning project, and start and finish dates, you can now see the name of the calendar it uses. You can also see the names and IDs of the predecessor activities, the calendars they’re using, and the projects they belong to.
Improved Coverage of Permission for Modifying Templates
The global privilege used to allow user to add, edit, and delete the templates used for importing and exporting to Microsoft Project and Primavera formats, now also allows users to edit the template used for exporting to Microsoft XLSX format. The privilege has been renamed to ‘Add/Edit/Delete Microsoft and Primavera Templates’ and users without the privilege assigned cannot modify XLSX templates for importing from and exporting to Microsoft Excel.
Duplicate Assignments are Aggregated to a Single Assignment When Exporting to CPP Format
If the same resource, role, or resource-role combination is assigned to an activity more than once, the cost and unit fields for the duplicate assignments are aggregated for export to CPP format. Assignments are aggregated only if they use the same resource (with no role assigned), role (with no resource assigned), or resource-role combination. See: Oracle Primavera CPP Import/Export Data Map Guide.
New SQL Logging Tool
As we move from dbExpress to ADO.NET, the existing SQL Trace tool is no longer supported. A new SQL monitoring tool is available for analyzing and troubleshooting database interactions. A new Enable SQL Logging option in the database configuration dialog box allows the new tool to log database interactions.
For information on using the new SQL logging tool, see the following knowledge management solutions: “Process for Using Primavera SQL Monitor With P6” (Doc ID 910590.1) or “Process for Configuring and Using SQL Monitor with the P6 Professional Visualizer Application” (Doc ID 1936751.1).
Configure the Read Timeout Value for a Database Connection P6 Professional 25.12 in The Database Configuration Dialog Box
Previously, you could only configure the Read Timeout value for a non-cloud database connection by editing the PrmBootStrapV2.xml file. You can now configure the Read Timeout value for any type of database connection in the Database Configuration dialog box or when configuring a connection from the command line.
Schedule Sheet Integration Between P6 Professional and Primavera Unifier Deprecated
Schedule sheet integration between P6 Professional and Primavera Unifier is supported in this release, but might not be supported in a future release. Oracle recommends using summary sheet integration between P6 Professional and Primavera Unifier.
Summary
Each year Oracle give us an update to P6. This year’s P6 Professional 25.12 release has some pretty useful new features and refinements that will be welcomed by most users. For a mature product, P6 Professional 25.12 continues the to deliver improvements that make our lives a little better and easier!