EPM Central Project Server Tutorials
Home Deployment    MS Project PWA SharePoint Articles Administrators FAQs Consulting Guest Book Search Site Map
  Error Messages

Project Server 2003

PWA Login DropDown

Inactive vs. Delete

Actual Work Protected

  2003 SQL Queries

  Enterprise Fields
    Project Fields
    Resource Fields
    Sample Queries

Admin Tools

Re-associate Site

Project Archival

  VBA

 
 
Administration -> MS Project Server 2003 -> Actual Work Protected

Actual Work Protected vs. Actual Work columns in MS Project Plan:

Actual Work in MS Project Plan is the overall work done on the tasks but not necessarily submitted from PWA.

Actual Work Protected values are entered through the PWA timesheet and approved by PM.

Actual Work Protected is valid for only assignments in the project plan. When PM approves the timesheet updates from PWA, actual work values go into Protected Actual Work and Actual Work columns of MS Project plan.

A project manager can edit the Actual Work values but not the Actual Work Protected in Project Professional. System simply looks at each assignment in PWA, and prevents PMs from changing tasks in the project plan file in any way that causes a conflict in actual work values between the two sources.

Note: Editing actual work in MS Project Plan is not possible when your Project Server configured with Managed Time Periods option.

Discrepancy between Actual Work and Actual Work Protected values:

When working with timesheets for status updates, Actual work and Actual Work protected should always be the same. When this is not the case (e.g. if PM manually changed the Actual Work of an assignment in MS Project plan for which timesheet reporting was done), you get an out of sync message. Synchronizing will then copy the information from the timesheet (Protected) into the Actual Work field of the project plan again.

Note: Please make sure there are no actual hours entered for local resources in the project plan. If you have actual hours for local resources in the project plan, when you use the Protected to Sync feature, it overwrites the AWP values into AWP. This makes AW for local resources as 0 hrs. (Always AWP values for local resources are 0 hrs due to actual hours for local resources are not received from PWA, instead those hours entered directly into project plan.)

If actual hours were entered for local resources is valid, please do not use the Sync to Protected Actuals feature on project plan.


Steps to Syncronize AW & AWP:

Open project plan -> Tools menu -> Tracking -> Sync to Protected Actuals -> Save Project


Note:
Actuals cannot be protected if timesheet tracking done by percent complete OR timesheet tracking done by actual and remaining work OR if you're not receiving your actuals from PWA timesheet."

Actual Work Protected feature is not available in Project Server 2007

Examples:
  • AW and AWP values are not same after doing Sync to Protected Actuals
  • Detailed task values have same AW & AWP values but values does not match at summary task level

Copyright © 2012. EPM Central. All rights reserved.