primavera p6 professional version 19.12 was released by oracle on dec 23rd of last year. let me highlight some of the new features, bug fixes and enhancements that you’ll want to know about.
let’s go!
what’s new in primavera p6 professional version 19.12
watch the video to see what’s new. read-on for a detailed list of all of the enhancements.
fewer releases for on-premise users
sometime in 2019 oracle decided to change how often it releases versions for on-premise users.
up till then, on-premise users had seen 2 updates of primavera p6 professional & primavera p6 eppm per year; one in the summer and another late in the year.
now on-premise users will get a single update in december (xx.12).
i was wondering myself what was going on, because we haven’t seen an update since primavera p6 version 18.8.
of course, primavera cloud users have the priviledge of seeing monthly releases, including important bug fixes and new features.
i don’t necessarily agree with oracle’s approach here, but it certainly makes a compelling reason to consider their primavera cloud offering. i myself use some software subscription services and do appreciate the periodic releases to desktop versions.
this is certainly a trend that will continue and maybe we on-premise users will have to jump on-board at sometime.
detailed list of primavera p6 professional improvements in v19.12
| useful for | feature | first released |
| admins | improved instructions for adding external applications to the tools menu. the instructions for adding external applications to the tools menu have been updated and improved. | 18.8.2 |
| cloud users | improved integration with oracle prime projects for scope and work packages. when you are connected to an eppm database, you can view scope % complete, work package id and work package name as columns in the activities page. the percent complete type for an activity in p6 professional is scope when the activity is integrated with oracle prime projects for scope integration. | 18.8.3 |
| legacy | integration with contract management not supported.integration between p6 client and contract management is no longer supported. | 18.8.3 |
| legacy | high level planning has been removed.the functionality to allow resource assignments at wbs and project level to perform high-level resource planning has been removed from p6 professional. | 18.8.4 |
| new – xml | check in and check out to xml. checking in and checking out projects uses primavera xml format. | 19.5 |
| new | dissolve activities with or without lag. you can choose whether or not to retain lag when dissolving activities using the retain lag setting in the calculations tab of the user preferences dialog. if you choose to retain lag, the lag from the dissolved activity's predecessor relationship will be added to that of its successor relationship and applied to the new relationship. | 19.5 |
| cloud users | prime lean task integration with p6 professional. imported tasks from the oracle prime projects tasks app are visible in p6 professional as tasks assigned to activities in integrated projects. you can see the imported tasks on the tasks tab in p6 professional. you can see key data from oracle prime projects about lean tasks in the tasks detail window in p6 professional. you can also add columns to your activities views to see high level information about these tasks. | 19.5 |
| admins | control the export of project data. you can use the export project data privilege to allow only certain users to export projects or download data to excel. | 19.5 |
| fyi | prime rebranding. oracle prime projects has been renamed oracle primavera cloud. references to this application have been updated in p6 professional. | 19.6 |
| users | improvements to stored images functionality. multiple images can be uploaded at the same time. | 19.7 |
| users | project code maximum length changed. the maximum length for project codes in ppm databases is 60 characters. | 19.7 |
| new – xml | scheduling and leveling options can be exported to and imported from primavera xml. when you export projects to primavera xml format, scheduling and leveling options are included. when importing the primavera xml file, you can choose whether to import with the update existing or keep existing import actions against the scheduling and leveling options. | 19.8 |
| users | data date default for apply actuals changed. the default value for the data date to use when applying actuals has changed. the default is that all projects use their own new data date. | 19.8 |
| new – xml | improved currency import. eppm only: you can choose to import projects from primavera xml files using the currency rate in the xml file or the currency rate in your database. if you import using the currency rate in the xml file, calculations convert the values to account for differences in the exchange rates in the xml file and your database. to use the currency rate in the xml file, you must have a matching currency id and name in your database. | 19.8 |
| new – xml | update baselines when importing primavera xml files. eppm only: you can choose to update baselines when importing a project from a primavera xml file. when you select the update existing import action at the project level, matching baselines you import will be updated from the import file. baselines you choose to import but which do not have a match in your database against the project you selected to update will be added to the project. | 19.8 |
| admins | allow or restrict access to 世界杯时间比赛时间 from multiple parent 世界杯时间比赛时间 . you can select up to five 世界杯时间比赛时间 when defining which 世界杯时间比赛时间 a user can access. the user can access and use the selected 世界杯时间比赛时间 and all child 世界杯时间比赛时间 of the selected 世界杯时间比赛时间 . | 19.9 |
| new – xml | update baselines when importing primavera xml files. standalone and ppmdb: you can choose to update baselines when importing a project from a primavera xml file. when you select the update existing import action at the project level, matching baselines you import will be updated from the import file. baselines you choose to import but which do not have a match in your database against the project you selected to update will be added to the project. | 19.9 |
| users | user preferences are saved when you close the user preferences dialog box. any changes you make in the user preferences dialog box are saved when you close the dialog box. | 19.10 |
| new – xml | choose to export primavera xml files into a compressed file. when you export projects in primavera xml format you can choose to have the files exported to a single compressed file in .zip format. | 19.10 |
| legacy | internet explorer 11 is deprecated. microsoft internet explorer 11 is supported in this release, but might not be supported in a future release. | 19.10 |
| cloud users | see the proposed due date from oracle primavera cloud in p6 professional. eppm only: the proposed due date field from oracle primavera cloud can be sent to and received from p6 professional via primavera gateway. | 19.11 |
| new | view user defined fields in a detail tab. a detail tab showing user defined fields (udfs) is available in the following pages: projects, activities, wbs, project expenses, resource assignments, issues, and work products and documents. for ppm installations, the udf detail tab is also available in the risks page. | 19.11 |
| cloud users | oracle primavera cloud quantitative risk analysis data is available on the activities and eps pages. eppm only: in the activities page, you can see which activities were part of the critical path during risk analysis in oracle primavera cloud and how often those activities were on the path in the pre-response criticality index and post-response criticality index columns. in the eps page, you can view the pre-response pessimistic start date, pre-response pessimistic finish date, post-response pessimistic start date, and post-response pessimistic finish date fields calculated in oracle primavera cloud during quantitative risk analysis. | 19.12 |
| eppm | project preference can prevent primary 世界杯时间比赛时间 from updating activity dates in a timesheet. eppm only: the allow primary 世界杯时间比赛时间 to update activity dates option allows project managers control over when and how primary 世界杯时间比赛时间 can update the start and finish dates of the activities in a project. | 19.12 |
| eppm | enable publication when copying projects. when you copy and paste projects, you can select to switch on the enable publication option for the pasted copies of the projects. | 19.12 |
| eppm | allow multiple users to access a portfolio. when you create a portfolio, you can choose to allow selected users to access the portfolio. you can also make existing portfolios available to multiple users and copy and paste portfolios in the portfolio list. | 19.12 |
my opinion on primavera p6 v19.12
while i’ve been waiting since aug of 2018 for an update which seems like a long while, i’m happy to see quite a few improvements to primavera p6 professional in v19.12.
there’s a lot of focus on data movement, especially around p6’s xml file format, and it’s been a long time coming.
we can now update baselines when importing xml projects. we can import zipped xml files. we have better currency support in xml. we can export primavera p6’s scheduling options in xml now – this feature alone might force users to opt for xml over xer files.
perhaps the xer file is on it’s way out. it’s looking that way.
we always have to guess whether primavera p6 professional will become a dead product as far as oracle is concerned, but with some nice features added here, perhaps we’re going to be pleasantly surprised that primavera p6 will continue to live on desktops for many more years.
what do you think? drop me a line in the comments.
