PWA timesheets is correct, protected actual work is not.

[P]

Never seen this problem before:

PWA Timesheet is confirmed by project resurce to be correct. No changes
submitted is pending for approval. Time periods are closed and actuals are
protected so project manager shouldnt be able to change it.

Allthough it shouldnt be possible, the actuals protected and actual work in
file shows appx 100 hrs more than PWA in a timeperiod closed before the
resource even got a user.

Any clue what happend?


Doing some testing i figured out that for this particular project file it is
possible to manipulate actual work by:
1. adding a new task
2. adding actual work to the new task
3. assigning a new resource to the plan.

Why? And how can i stop it? Are there more possible ways to manipulate
actual work and actual work protected that I am not aware of?

 

[Christophe Fiessinger [MSFT]]

Assuming this is for Project Server 2007, the two are not synched up
automatically, check the following:
http://technet.microsoft.com/en-us/library/cc197478(TechNet.10).aspx
http://blogs.msdn.com/chrisfie/archive/2007/11/20/timesheeting-and-statusing-data-flow-diagram.aspx

 

[P]

Sorry - forgot to mention that we use MSProject 2003.

 

[Gary L. Chefetz [MVP]]

Actual Work Protected, becomes such when it is collected through PWA. IOW,
the system simply looks at each assignment in PWA, and prevents PMs from
changing tasks in the plan file in any way that causes a conflict in actual
work values between the two sources. With protected actual work turned on in
2003, the PWA web work tables rule. In the cases you point out, the actual
work changes do not conflict with PWA assignment data. In the first two
cases, which are pretty much the "same case", there is no assignment so
there's no possible conflict with protected actual as nothing is protected.
In the last case, someone is handling the assignment incorrectly if it is
generating actual work. That fact aside, the work would not fall into the
graces of "protection" until you publish the assignment.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[MJS]

Does this apply to 2007 SP1a also ? We are having issues with actual hours
replicating into the future for the full duration of the assignment. We will
try to synch with protected actuals, it does not change anything in the plan.
Any ideas or suggestions would be greatly appreciated. We conduct PM
metrics for estimate accuracy and these type of issues are very problematic
to provide any meaningful data.

 

[Gary L. Chefetz [MVP]]

2007 handles this differently than 2003. This sounds like a different issue
and discussion.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com