My Oracle Support Banner

Earned Value Labor Units and Planed Value Cost Improperly Calculated in the P6 EPPM Extended Schema When Using "Week" Time Distributed Publication Interval for Activities Which Do Not Have Progress (Doc ID 2458685.1)

Last updated on MARCH 30, 2019

Applies to:

Primavera Analytics Cloud Service - Version 18.7 and later
Primavera P6 Enterprise Project Portfolio Management - Version 18.8 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
If an activity is spread across a period of time which falls between two different months (for example, July 29--Aug 04 OR Oct 28--Nov 03), Earned Value Labor Units and Planed Value cost are improperly calculated in the P6 EPPM Extended schema (after the project is published) when using a weekly spread interval for publication.

For example:

EXPECTED BEHAVIOR
-----------------------
When an activity spans across two different months AND publication is set to a weekly spread, values should not be calculated for earned value (ie, Planned Value Labor Unit, Planned Value Labor Cost) when there is no progress on the activity. In addition, the spread data in projectspread should also not include any rollup for earned value when there is no activities in the project which have progress.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. Create new project
  2. Set the following project options (although likely do not relate):
    • Duration Type = Fixed Duration & Units
    • Percent Complete Type = Duration
    • Calendar 7-Day Workweek
  3. Add activity to project (called A1)
    • Original Duration = 5d
    • Planned Labor Units = 40h
    • Start Date: 20-Sep-2018 08:00 AM
    • End Date: 24-Sep-2018 04:00 PM
  4. Assign a resource to A1 with any configured price/unit (ex, $1/h)
  5. Schedule project
  6. Add second activity to project (called A2):
    • Original Duration = 5d
    • Planned Labor Units = 40h
    • Start Date: 31-Jul-2018 08:00 AM
    • End Date: 04-Aug-2018 04:00 PM
  7. Add following columns to display:
    • Schedule % Complete
    • Planned Value Cost
    • Planned Value Labor Units
  8. Note that for A2:
    • Schedule % Complete = 100%
    • Planned Value Cost = $40.0
    • Planned Value Labor Units = 40h
    • This is because the activity start/end is set before the project start.
  9. Adjust the following on project and commit changes:
    • Project Planned Start = 31-Jul-2018 12:00 AM
    • Data Date = 31-Jul-2018 12:00 AM
  10. Note that for A2:
    • Schedule % Complete = 0%
    • Planned Value Cost = $0.0
    • Planned Value Labor Units = 0h
    • This is because the activity start/end is now after the Project Planned Start
  11. Publish Project
  12. Results:
    • P6 does not show Planned Value Labor Cost & Planned Value Labor Unit data for any activity
    • Planned Value Labor Cost & Planned Value Labor Unit values (>0) exist in the extended schema for A2 when the value should be 0:
    • SUM(Planned Value Labor Cost) = 32
    • SUM(Planned Value Labor Unit) = 32
    • If project is scheduled then re-published:
      • Activity A1 dates now match A2.
      • Activity A1 values for Planned Value Labor Cost/Units show 0 in P6 Professional / P6
      • Published data shows SUM(Planned Value Labor Cost) & SUM(Planned Value Labor Unit) = 32 (when it should be 0)
      • 3 rows in the activityspread (since using weekly spread):
        • Start Date - End Date = 15-Sep-19 - 22-Sep-19
        • Start Date - End Date = 29-Jul-19 - 05-Aug-19
        • Start Date - End Date = 01-Aug-19 - 05-Aug-19
    • If any of the activities have a constraint set to start on 20-Sep-2018 08:00 AM, then reschedule and republish the project:
      • The SUM(Planned Value Labor Cost) / SUM(Planned Value Labor Unit) moves back to 0 in extended schema.
      • 1 row in the activityspread (since using weekly spread):
        • Start Date - End Date = 16-Sep-18 - 23-Sep-18
    • If any of the activities have a constraint set to start on 18-Sep-2018 08:00 AM, then reschedule and republish the project:
      • The SUM(Planned Value Labor Cost) / SUM(Planned Value Labor Unit) is still 0 in extended schema (as it should be)

BUSINESS IMPACT
-----------------------
Due to this issue, improper earned value calculations are being brought into external applications which read from the P6 EPPM extended schema (for example, Analytics) causing reports based on SPI or earned value to display results for projects which should not have earned value.

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!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.