G
GetOffMyPatch
Hi All,
We recently noticed that our planned burn values were null in our
Trended Burn reports and after investigating some work plans noticed
that some resources had zero baseline work on the summary row. This is
what led us down this track of investigation.
Upon further testing from our side we believe we have uncovered the
issue.
This is what we have found:
After baselining and publishing the work plan everything is fine.
Next the PM enters some actual hours (timephased) for an assignment
and saves and publishes.
Now the assignment work is rest to NULL in the Reporting database thus
impacting the reports.
Here is how you can reproduce
Create a plan with basic tasks and assignments and baseline it
Save Publish to MOPS
Execute the following query to see the actual work and baseline work
values in the reporting database.
-------------------------------------------------------------------------------------------------
select
tuv.taskname,
sum(abd.assignmentactualwork) as [Actual Work],
sum(abd.assignmentbaseline0work) as [Assignment Baseline Work]
from
msp_epmproject_userview puv
inner join
msp_epmtask_userview tuv
on puv.projectuid=tuv.projectuid
inner join
msp_epmassignment auv
on auv.taskuid= tuv.taskuid
inner join
msp_epmassignmentbyday_userview abd
on abd.assignmentuid=auv.assignmentuid
where
puv.projectname='ad_net_3pg_cedicam_Lot D_v2'
and tuv.taskissummary=0
group by
tuv.taskname
------------------------------------------------------
Next edit the work plan in MS project and add some timephased actual
work to some of the assignments
Save and Publish the plan
Execute the query again and you will see the baseline work value will
reset to NULL for the tasks you entered actual work against.
Let me know if anyone can think of any reason why this is not a BUG
Tks,
Shane
We recently noticed that our planned burn values were null in our
Trended Burn reports and after investigating some work plans noticed
that some resources had zero baseline work on the summary row. This is
what led us down this track of investigation.
Upon further testing from our side we believe we have uncovered the
issue.
This is what we have found:
After baselining and publishing the work plan everything is fine.
Next the PM enters some actual hours (timephased) for an assignment
and saves and publishes.
Now the assignment work is rest to NULL in the Reporting database thus
impacting the reports.
Here is how you can reproduce
Create a plan with basic tasks and assignments and baseline it
Save Publish to MOPS
Execute the following query to see the actual work and baseline work
values in the reporting database.
-------------------------------------------------------------------------------------------------
select
tuv.taskname,
sum(abd.assignmentactualwork) as [Actual Work],
sum(abd.assignmentbaseline0work) as [Assignment Baseline Work]
from
msp_epmproject_userview puv
inner join
msp_epmtask_userview tuv
on puv.projectuid=tuv.projectuid
inner join
msp_epmassignment auv
on auv.taskuid= tuv.taskuid
inner join
msp_epmassignmentbyday_userview abd
on abd.assignmentuid=auv.assignmentuid
where
puv.projectname='ad_net_3pg_cedicam_Lot D_v2'
and tuv.taskissummary=0
group by
tuv.taskname
------------------------------------------------------
Next edit the work plan in MS project and add some timephased actual
work to some of the assignments
Save and Publish the plan
Execute the query again and you will see the baseline work value will
reset to NULL for the tasks you entered actual work against.
Let me know if anyone can think of any reason why this is not a BUG
Tks,
Shane