Actual Hours and Timesheets

S

Steve

What reasons are there that the actual hours is being calculated to be
inhuman hours (.28, 3.87, 10.68, etc) and is not matching timesheet hours?
We are using the "Hours of Work Done per Day" tracking method with Lock Down
Defaults and Managed Periods enabled.

For example,
I have a resource who has work assigned on a task, but no time entered in
her timesheet for that task. But, somehow, time was entered into the Actual
Work field in Project Professional.

Other times, when I open a project and there is time remaining in a task,
for some reason the actual work field gets recalculated so that the Actual
Work field is all screwy... We have people sync to actuals and save,
everything is ok, but when they reopen the project, the hours are wrong
again. Is this a symptom of us not republishing all information? I just got
on this project and I'm trying to figure out all these problems they're
experiencing... any help? Dale, Gary?

Steve
 
D

Dale Howard [MVP]

Steve --

After you process task updates from PWA into Microsoft Project Professional,
do you then click Collaborate - Publish - All Information? This step is
necessary to "push" all of the latest schedule changes to the relevant areas
of PWA. Let us know.
 
S

Steve

Dale,

Doing this seems to resolve the issue... I'll update our process to have
users perform this step.

Can you provide any insight as to why this happens if we don't republish?
 
D

Dale Howard [MVP]

Steve --

Information in your Microsoft Project plan and the information in PWA will
be "out of synch."
 
Top