Mismatch of "Baseline Usage" between PPM and DWH

Document ID : KB000005338
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The "Baseline Usage" values in PPM and DWH do not match under certain circumstances.

Steps to Reproduce:

1. Create a Project

2. Allocate a team member

3. Assign this resource to a task, say Task 0

4. Assign this same resource to another task, say Task 1

5. Create a baseline

6. Lets say the “Baseline Usage” shown at this point is 250 (under the “Team” tab)

7. Running the Load Data Warehouse job will put Baseline Usage = 250, in the DWH

8. Go ahead and delete the assignment made on Task 1 at step 4

9. The PPM UI (under “Team” tab) will still report Baseline Usage at 250

10. But on running the Load Data Warehouse job, the Baseline Usage available in the DWH will be, say 150

11. This results in users seeing different values in the PPM UI (under “Team” tab) and in the DWH.

Environment:
All versions till 15.1 as of this writing. That is 14.2, 14.3, 14.4 and 15.1 have this issue.
Cause:

This is caused by a defect logged via DE31586.

The reason is that PPM picks up Baseline Usage by filtering for “PRJ_BASELINE_DETAILS.OBJECT_TYPE” = “TEAM”, whereas the Load Data Warehouse gets the Baseline Usage data by filtering for “PRJ_BASELINE_DETAILS.OBJECT_TYPE” = “ASSIGNMENT”

Resolution:

The Baseline Usages in PPM and DWH show the same number, if the Baseline is updated, or a new Baseline is created. The numbers will not differ on projects where the Project Managers do not directly remove assignments.

Additional Information:

The two columns of interest here, in the DWH are: DWH_INV_SUMMARY_FACTS.BASE_LABOR_HOURS and DWH_INV_SUMMARY_FACTS.EAC_BASE_HOURS_VAR