Jodi M --
There are several methods for locking down a project so that no more actuals
can be entered against it:
Method #1 -- Enable the use of managed time periods in Project Server. When
you use managed time periods, past time periods can be closed to prevent the
entry of actuals in the past. In addition, the use of managed time periods
will also prevent resources from entering time into the future, and will
restrict resources to only entering actuals in the current reporting period.
Before you implement this feature, please be aware that this creates a VERY
restrictive environment and applies to EVERY project in the Project Server
database. Frankly, I would not recommend this approach to solve your
problem, but I think you should be aware of it in case others have the same
need as you.
Method #2 -- Ask your Project Server administrator to create an additional
Project Server instance for your company called Archived Projects. He/she
would need to use the EditSite utility to create this new instance. When a
project is completed, your Project Server administrator would need to delete
the project from the production Project Server instance and then import it
into the Archived Projects instance, thus maintaining the historical record
for the project. If you need to keep closed Projects in your production
Project Server instance for a long period of time, then this solution won't
work very well for you.
Method #3 -- Make this a training and performance issue for both team
members and project managers. Teach them NOT to submit time for closed
projects, and then expect them to perform according to these standards.
This would be the simplest solution, I believe.
Just a few thoughts. Hope this helps.
