Managed Time Period - Fixing

[bushie_40]

I have managed time periods turned on but when we set it up, we only
had a single time period from Jan 1, 2005 to Dec 31,
2005. People have been submitting timesheets and tasks updates for the
last 2 months or so. Now that we are more used
to the system we would like to go with managed time periods biweekly to
match project reporting and payroll periods.

The problem is that now that we have time submitted against the yearly
managed time period, we can't delete it in order to replace it with the
biweekly periods.

Might this involve saving all the projects to MPP, deleting them from
the server, deleting the timeperiod, creating the proper time periods
and then republishing everything?

Thanks!

Paul

 

[Jonathan Sofer - MCP]

Doing your suggestion of saving all plans off as mpp files, deleting and
re-importing would work except that all your resources will see messages on
their home page that they have not entered their timesheets for all past
periods. There is a hotfix out there that might fix this problem but I
would suggest attempting this whole process, including the hotfix on a
development/sandbox environment to make sure it works with no issues.

You will first have to load the projects with non-managed time periods so
that you can push the actuals out to the PWA timesheets. After you have
re-imported all your plans back and published the actuals out, you can then
switch to Managed Time-Periods and define them bi-weekly.

Again, I would not suggest just going for this solution until you have
thoroughly tested it on a separate environment.

Here is the hotfix I mentioned:
http://support.microsoft.com/default.aspx?scid=kb;en-us;897706#5.