Can a Managed Time Period be Deleted?

[Antoon]

I saved some Managed Time Sheet periods in order to test this functionality.
In the Managed Timesheet periods section of the Tracking Settings in
Admin/customize PWA, the Delete button is always disabled.
Also the Start and End Date can not be changed.

Is there a way to get rid of these test periods?


Regards,
Antoon

 

[Dale Howard [MVP]]

Antoon --

Once actuals have been entered in a managed time period, you cannot delete
the managed time period. Are you still in a test environment with Project
Server? If so, why don't you delete every enterprise project from the
Project Server database, thus removing actuals from every managed time
period. After that, perhaps you can delete the unwanted managed time
periods. Let us know if this helps.

 

[Antoon]

Dale, thank you very much for your help.

I am still in a test environment, considering using this functionality in
the production environment.
Would it be a sound strategy to define a managed time period for every
month, initially Open, and to close those periods when the actuals are
complete (i.e. 40 hours/week per full time equivalent)?
This way we want to achieve an accurate financial reporting. After a
financial report is published, that period is closed. Exceptions will have to
notify the responsible for financial reporting.

Regards,
Antoon

 

[Dale Howard [MVP]]

Antoon --

I generally recommend that managed time periods match the project reporting
periods, either weekly or bi-weekly. Therefore, if team members are
expected to report actuals at the end of every week, I would set up weekly
managed time periods. I would also recommend that there be a "cut off" date
specified for each reporting period, for example, by Monday at noon after
the last reporting period. Once actuals have been submitted for the
reporting period, then the managed time period can be closed to prevent team
members from changing their progress in previous past time periods.

Whatever decision you make about this, I believe that your company's project
reporting needs should drive this decision. Just a thought. Perhaps the
others will have some ideas for you also. Hope this helps.

 

[Carole]

Hello,

I want to know if this is possible with Project Central and Project 2000 ?
If yes, how ?

Thanks

 

[Dale Howard [MVP]]

Carole --

No, this is not possible with either Project Central or Project Server 2002.
The use of managed time periods is only available in Project Server 2003.

 

[Carole]

Thanks . But, do you know a method to program this functionality with Project
Central ? Is it difficult ? I think with a excel sheet per haps ? Because i
think it is impossible to modify the timesheet in Project Central and locked
the filter for the resources ?
**********

 

[Dale Howard [MVP]]

Carole --

I know of no way to make this functionality appear in Project Central. The
best I can tell you is that you should make the following a training and
performance issue with your organization's team members:

1. Do not enter actuals in past time periods prior to the current reporting
period
2. Do not enter actuals in future time periods

Train people to follow the above guidelines and hold them responsible for
their behavior. That's the best I can tell you. Hope this helps.

 

[Carole]

Thanks a lot, but all you say i've done ... Even the project chief make
errors, it is awful ! Ok , per haps they can buy 2003 ...

 

[Dale Howard [MVP]]

Carole --

I didn't even want to mention it, but if your organization has the $$$, then
I would recommend you upgrade to Project Server 2003 to use the Managed Time
Periods feature and functionality. Hope this helps.