Applying Actuals Based on the Auto Compute Actuals Method
The following processing occurs behind the scenes when you run the Apply Actuals command.
- For all activities where the Planned Start Date field is less than the new data date, set the Actual Start field equal to the Planned Start field.
- Set Remaining Duration equal to the Early Finish field minus the new data date.
- Set the Actual Duration equal to the Planned Duration minus the Remaining Duration.
- Set Actual Units equal to the Unit Percent multiplied by the At Complete Units.
- For all activities where the Planned Finish Date field is less than the new data date, set the Actual Finish field equal to the Planned Finish field.
- All Remaining values are set to At Complete values minus Actuals.
- For all role assignments without a resource, processing will update progress on the role assignment.
- If Units and Cost are linked, then Remaining and Actual Cost will always be set to Units multiplied by Price per unit.
- If there are multiple price per units, then the assignment's Actual Cost will be calculated using time-varying resource rates.
Note: Apply Actuals will take resource lags and resource curves into consideration, just as the Auto Compute Actuals feature does. If there is a curve applied to a resource, the application will apply the actuals to the resource based on the distribution of the curve.
Example: A project's data date is June 1 and a user runs Apply Actuals with a new data date of June 20. An activity is planned for June 18 and is estimated to last 10 days until June 27. The activity's resource assignment has +5 days of lag (meaning it cannot start until June 23). When the user applies actuals on June 20, the activity's status is updated; however, because the assignment carries a resource lag beyond the new data date, it is not updated.
Last Published Thursday, October 3, 2024