Now that I'm paying closer attention, I think I have found the problem: those Actual Cost activities that are "misbehaving" haven't been started yet. It seems that when one tries to assign Actual Costs to activities that haven't been started, P6 will make an assumption that you want those values to become part of the Planned Costs.
In this case, the situation is that project staff have been charging actual costs to a Work Element that hasn't yet begun. It seems now that I have a warning sign for such errors, now that I know how to recognize it: if the Actual Cost activities are showing Planned Cost and Remaining Cost, then, it's likely because the Actual Cost activities haven't been marked as started, which could be because the work itself hasn't started, and thus you have some invalid charges to be managed.
Member for
16 years 3 months
Member for16 years3 months
Submitted by Zoltan Palffy on Mon, 2022-08-01 21:33
make sure that for the resource that calculate costs from units is set to NO.
also for the resource make sure that auto compute actuals is NOT checked
also at the project level under the calculations tab make sure that Recalculate actual units and costs when duration % complete changes is NOT checked also make sure that Update units when costs change on resource assignments is NOT checked.
Member for
16 years 3 months
Member for16 years3 months
Submitted by Zoltan Palffy on Mon, 2022-08-01 21:28
make sure that for the resource that calculate costs from units is set to NO.
also for the resource make sure that auto compute actuals is NOT checked
also at the project level under the calculations tab make sure that Recalculate actual units and costs when duration % complete changes is NOT checked also make sure that Update units when costs change on resource assignments is NOT checked.
Member for
16 years 3 monthsthat is correct you can not
that is correct you can not have actual costs if the activity does not have an actual start date
Member for
9 years 7 monthsNow that I'm paying closer
Now that I'm paying closer attention, I think I have found the problem: those Actual Cost activities that are "misbehaving" haven't been started yet. It seems that when one tries to assign Actual Costs to activities that haven't been started, P6 will make an assumption that you want those values to become part of the Planned Costs.
In this case, the situation is that project staff have been charging actual costs to a Work Element that hasn't yet begun. It seems now that I have a warning sign for such errors, now that I know how to recognize it: if the Actual Cost activities are showing Planned Cost and Remaining Cost, then, it's likely because the Actual Cost activities haven't been marked as started, which could be because the work itself hasn't started, and thus you have some invalid charges to be managed.
Member for
16 years 3 monthsmake sure that for the
make sure that for the resource that calculate costs from units is set to NO.
also for the resource make sure that auto compute actuals is NOT checked
also at the project level under the calculations tab make sure that Recalculate actual units and costs when duration % complete changes is NOT checked also make sure that Update units when costs change on resource assignments is NOT checked.
Member for
16 years 3 monthsmake sure that for the
make sure that for the resource that calculate costs from units is set to NO.
also for the resource make sure that auto compute actuals is NOT checked
also at the project level under the calculations tab make sure that Recalculate actual units and costs when duration % complete changes is NOT checked also make sure that Update units when costs change on resource assignments is NOT checked.