Incorect Actual Work Protected

[Paul Lyon]

We are having a critical issue with our Project setup. Every once in a
while, Project decides to make up actual work protected numbers for an
assignment. So a resource will have 1hr in their timesheet, but 11hr of
actual work protected in Project. This obviously wreaks all sorts of havoc
with our numbers.

Has anyone else run into this problem?? What did you do?

 

[Marina]

Hi Paul
Yes we have run into this problem but have not been able to fix/solve it.
It appeared to be a "corrupted" project. I have no suggestions but know that
you are not alone.
Marina

 

[pwlhendriks]

We have the same problem too. Turned out with us, our projectmanagers edited
the actual work (in order to 'adjust' their reports to higher management).
They could also, for some reason, sinc this actual work to the actual work
protected. We've solved this problem socially (telling managers there would
be consequenses if they ever did that again), but i've never come across a
technical solution. Idea's anyone?!

 

[Marina]

In our case, the PM did not change the actuals (I am the PM). It just
"suddenly" started reported different actuals for historic months since the
beginning of the project. We could see the actuals in the project and the
timesheets on the server and they were definitely different for this
particular project.

Marina