My Oracle Support Banner

Period Performance Changes Are Not Kept after Closing and Reopening a Project in P6 Professional (Doc ID 3046819.1)

Last updated on SEPTEMBER 18, 2024

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 24.8 and later
Primavera P6 Professional Project Management - Version 23.12.8.0 and later
Primavera P6 Enterprise Project Portfolio Management - Version 23.12.8.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR

In P6 Professional versions 23.12.8.0, 24.8, and 24.9: When storing period performance in a new financial period (i.e. the current period) changes are not committed to the database, resulting in the period performance displaying as if it was never run after the project is closed and reopened.

This issue is limited to running stored period performance from the P6 Professional client.

EXPECTED BEHAVIOR

Changes to period performance should be permanently stored in the database and remain available after closing and reopening a project.

 

The issue can be reproduced at will using the following steps:

  1. In P6 Professional, create a financial period Monthly from 1 Sept to 31 Dec 2024.
  2. Create a dummy project with two Activities and assign a resource for each activity.
  3. Update one of the activities and check the Actual units.
  4. Update the Data Date to 1 Oct 2024.
  5. Store Actuals on the financial period 1 Sept - 30 Sept and Commit the changes.
  6. After closing and reopening the project, all the period performance Actuals are lost from the financial periods.
  7. Viewing the contents of the financial database tables TASKFIN and TRSRCFIN shows that no information has been stored for the project.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.