Guy
If you’re using managed timesheet periods, Project is going to ask to sync to actuals. When users update their tasks through PWA timesheet, their time is entered into the protected work fields, which is new to Project ’03. These actuals can only be entered by the resource or users with the permission to adjust actuals
If you want to use managed timesheet periods and you want to adjust those thousands of actuals, you will need to create managed periods that go back in time. I would not recommend doing this, not only will it take you a lot of time, but we’ve discovered some bugginess with this process
I would advise you to start the project from the most recent time period and archive the completed portion locally. Like everyone else, I’m sure your firm is committed to using managed time sheet periods, so unless you want to battle to change corporate policy, you should, regrettably, move on without the past information
Hope this helps!
---------------------
Sean Pale
EPM Solutions Grou
Bennett Adelso
www.bennettadelson.co
----- Guy Melanson wrote: ----
We are ready to fully deploy Microsoft Project Server 2003 in our enterprise. We are enforcing managed periods and only allowing a 2 week window for users to enter their time before closing the window. Project plans were created in Project 2000, with no enterprise resource pool. Some project plans were already started so I created local resources for tasks already completed and assigned the uncompleted tasks to the enterprise resources. The problem is that when published, all actuals from these local resources are deleted and returned to 0. I need to maintain this history. Please help, were talking about thousand lines of tasks, there must be another way to adjust actuals beside going in PWA and entering it manually???
Guy Melanso
SPIELO
