adjusting actuals - why showing as remaining work?

[reb-clo]

Hi

I have been tasked with the fun job of moving some protected actuals from
one plan to another. I have been doing this by using the adjust actuals
feature in PWA, and zeroing the hours in the old plan.

When I have done this, the hours look fine in the new plan. They are logged
as actual work and there is no remaining work. However, in the resource's
timesheet, it shows the hours I moved as being remaining work and no actual
work has been done. I am using Project Server 2003 with PWA.

Does anyone know why this is? They also don't have the option to change
remaining work, but I wish to keep it this way as these are bucket tasks!
Thanks!

 

[Christina]

This is probably a silly question... but did you Republish the assignment in
the new schedule and overwrite work entered by the resource?

Christina

 

[reb-clo]

This is the process I followed. I wouldn't be surprised if I missed a step!
1. Added resource to new task and published new or changed assignments
2. Adjusted actuals, meaning I entered time again the new task and zeroed
hours against the old task
3. Removed resource against old task and republished to send a cancellation
notice.
4. removed deleted tasks from timesheets using an SQL script.

Perhaps I just need to republish all assignments and sync with protected
actuals?

 

[Christina]

Hmmm... you could try re-publishing all assignments (and overwriting work
entered by resources) to see if that forces the task deletion from the
resources' timesheets. I'm guessing that when the resosurces look at the
task in their timesheet, they are not seeing an "X" next to it to indicate
that it's been deleted?

This has happened to me occassionally and I was told that sometimes these
old tasks become "orphan tasks" in that deleting the task from the resource
did not update the database properly. I'm not sure why this happens or what
one can do to avoid this. To fix this, I have gone into the database and
verified whether the Assignments table reflects that these tasks were deleted
(in the Deleted in Project field). If it is a "0", I've changed it to a "1",
which forces the "X" on the timesheet. At that point, the resource can
"hide" the task so they don't see it anymore.

I try to avoid going into the database but sometimes that the only way we've
been able to fix this problem.

If one of the MVPs has a suggestion for a better (or correct) way to address
this issue, I would definitely be interested.

Christina

 

[reb-clo]

I tried republishing assignments. Just to clarify, this is affecting the new
task - not th old one. I have sucessfully deleted the old task and removed it
from the timesheet. It is the new task which is showing remaining work rather
than actual work. The MSP plan for the new tasks show 0hrs remaining work, so
why do the timesheets show something different?

Thanks,
Rebecca

 

[Christina]

My apologies for not responding sooner... my access to the forum has been
limited at times.

By this time you probably have already resolved the issue. If not,
unfortuantely, I cannot think of anything else to suggest other than what you
have already done. Usually, republishing and overwriting work entered by the
resource triggers the task to reflect as complete on their timesheet.

I'm sorry...

Christina