Hi Long --
Manipulating Project Server's Managed Timesheet Periods feature without
fully understanding the effects, as well as working without a
well-thought-out backup and restore strategy, can lead to big
problems... which it sounds like you're learning the hard way. Having
administrative power without knowing how to use it can be dangerous.
It sounds like you're in quite a predicament, but I think that there's
still a way out of it, while minimizing re-entry of work hours by the
Team Members. This is key, since we rely on them to update tasks
accurately and in a timely manner, and we don't want them to lose
confidence in the system.
First, I assume that you will want to restore everyone else's projects
back to the current state in order to minimize re-work. You should be
able to do this by restoring the latest database backup; this should
bring everyone else's projects back up to date, and your project
schedule will be back to the point at which you had your Actual Work
and Actual Work Protected problem.
Once this is done, you have a couple of options... you can restore your
original troublesome project from a backup, or you can try to fix the
Actual Work / Actual Work Protected problem in current version of the
project schedule. There is a utility available from Microsoft that you
can use to restore a prior version of a single project schedule from a
backup, called the "Restore Single Project Tool" (you can visit
www.microsoft.com and search for it). However, it's not a simple
5-minute process, so I would first try to fix the latest version of the
schedule (it may be an easy fix).
You stated in your original post that the Actual Work and the Actual
Work Protected values were different in your project schedule... but
did you do further analysis to determine why they were different?
When your Project Server is configured to use Managed Timesheet
Periods, the Actual Work Protected values are those which have been
entered into Team Members' PWA timesheets... and thus they should be
accurate. The Actual Work Protected values are not editable by the
Project Manager in Project Pro when the Managed Timesheet Periods
function is enabled. However, the Actual Work values CAN be edited by
the PM in Project Pro, although they should match the Actual Work
Protected values. Because there are two separate sets of values, and
one set is protected and the other is not, it's possible that they can
become out of sync... and thus the alert messages that you've seen.
If you'd like suggestions on how to perform a detailed comparative
analysis of Actual Work and Actual Work Protected values, I can post
more info about that.
If you do some research and find that the Actual Work Protected values
are correct and the Actual Work values are not, then you can use a
built-in Project Pro function to re-sync them... Tools > Tracking >
Sync to Protected Actuals. This will update the Actual Work values in
Project Pro to match the Actual Work Protected values.
If, on the other hand, you do some research and find that all or some
of the Actual Work values are correct and the Actual Work Protected
values (entered by Team Members) are not correct, then you can do three
things:
1. Ask the Team Member(s) to correct the Actual Work hours in their PWA
timesheet(s) and resubmit (recommended)... if there are corrections
that need to be made during a closed timesheet period, then you will
need to temporarily open it for the correction.
2. Use the "Adjust Actuals" function in PWA to adjust the Team
Member(s) Actual Work hours for them
3. Turn off the Managed Timesheet Periods function, republish the
assignments and push the Actual Work hours from the project schedule
back out to the Team Member(s) PWA timesheet(s), then turn the Managed
Timesheet Periods function back on
If you choose option 3, keep in mind that you don't need to republish
all of the assignments in the project schedule, but rather you can
republish selected ones, keeping the others in tact.
Good luck!
Tony Zink
========================================
http://www.msprojectreporter.com
http://www.pmreporter.com
http://www.sharepointreporter.com
http://www.msofficereporter.com
http://www.dotnetreporter.com
========================================
, to undo it, someone plz help me :-??