PWA 2003 - fix managed time period

[Adrienne]

We wanted to close the last time period so that we could proceed with
archiving the plans in PWA, but unfortunately the past date was 9/1 - 9/16
versus 9/1 - 9/15. People have already submitted their hours so we don't
want to mess with it, but its got the time periods thereafter out of sync
with 9/17 - 10/2 next instead of 9/16 - 9/30 and so on. What is the best way
to fix this? Thanks.

 

[Sander]

1. Find the first period where no hours are already booked.
2. Delete all periods after this one.
3. update the period from step one to make it 1 day shorter
4. create new periods from here on with correct dates.

should not be to difficult i hope.

Sander

 

[Adrienne]

Thank you very much for your response, it is greatly appreciated.

To further clarify: Once hours are entered against a managed time period,
it seems to be locked in PWA. Would it be possible to change the time period
in a certain SQL table, without corrupting any data?

 

[Sander]

You asked for the best way and I still think my previous answer is that.
Sure it would be possible to change data in an sql table so that the periods
are straightened out, but your next requirement 'without corrupting data'
will never be guaranteed. so to be short: I would not go there.. the risk is
not worth the benefits.

can you live with this?

Sander

 

[Adrienne]

The project is in pretty dire need of fixing this, so it looks like they want
to change the SQL table. If all the .mpp files that have been uploaded to
PWA are backed up, could the table be changed and then the plans could be
re-uploaded?
Also, which SQL table holds the time period values? Currently, I don't have
admin access to even a test server to check. :-(

Thanks again,

Adrienne

 

[Chak]

Hi Adrienne,

Time phase data stores in view tables. I hope you already know how
view tables will get the data. Basically the data in view tables will
be populated from publish process. Once PWA task updates are approved
by PM, project will go through save/publishing process. During this
time view processor will pump the data into view tables.

Answer to your question, approved timesheet data will store in
MSP_VIEW_PROJ_ASSN_TP_BY_DAY table.

Please do not update the table directly; it may cause the data
corruption.

How many projects having this issue? If it is one project, you may do
the following. I know, the below process is more manual, but it will
be safer.

1) Temporarily set the setting as non managed time period in PWA and
choose the option PMs can update the hours from PWA and project plan

2) Open MS Project Plan having this issue

3) On Resource usage view, set the time scale to view by day

4) Move the actual hours accordingly (copy/paste in required days);
also make sure work aligned properly

5) Republish the plan by choosing overwrite actuals entered by
resources (This action will set the timesheet entries and also refresh
PWA entries)

6) Set back the PWA settings to managed time periods


Thanks
Chak
http://www.epmcentral.com

 

[Adrienne]

Hi Chak,

Thanks for your post! I have a follow-up question:

1. When you say "4) Move the actual hours accordingly (copy/paste in
required days); also make sure work aligned properly", do you mean the
following:
a. Right-click on the row and select Actual Work
b. Manually enter the actual hours into the required days (example 9/1
through 9/15)

Best regards,

Adrienne

 

[Chak]

Hi Adrienne,

Yes, I am assuming that you guys already accpeted time updated and
saved into project plan. If so, show actual work by right click; you
can manually enter those actual work values in to the required days
(OR) cut the values and paste into the required days.

If you guys are not accepted the time and still those entries are
appearing under pending updates, it is easy to fix.

Also one this exercise done, correct future time period ranges from
PWA admin menu.

Thanks
Chak
http://www.epmcentral.com