Remaining Costs calculate improperly

[Casey]

I have a project that where we received a short additional task order last
month. A separate file was developed with the WBS for the new work. When I
copy the tasks and paste them into my original plan, then rebaseline the NEW
tasks only, update the status date, set the % complete to 100% (the new work
actually completed on 3/30), this is what happens: most fields calculate
properly (BCWS, BCWP, ACWP, and EAC); however the “Remaining Cost†for almost
all tasks is equal to the BCWS/BCWP/ACWP (remember all work is completed).
For a few tasks, remaining costs are $0. Any ideas? I have tried a million
different combinations of steps. Using MS Project 2003 with SP1.

 

[Jim Aksel]

Rebaseline will set ACWP=BCWP=BCWS. Baseline the tasks when there is
0%Complete prior to setting it to 100% (I think that is what you did). You
will have remaining cost if there is remaining work or other remaining fixed
costs. You can manually set remaining work (or cost) to 0 and then hit F9 to
recalculate.

As an FYI, the latest on MS Project2003 is SP2 which can be downloaded here:
http://www.microsoft.com/downloads/...EF-AF64-444D-942D-1188843A8FA4&displaylang=en


--
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project

 

[Casey]

Thanks, Jim! I had not thought to manually set remaining costs to 0, but I
actually figured out what was hampering this about 5 minutes ago. The second
plan was set to always calculate manually. I had checked the master plan,
but neglected to check the new one. Once I reset that to automatically
calculate and followed the same steps it worked. I appreciate the link to
SP2, also!