WaterGypsy
MIS
Hi Folks
I've had a little problem when using "Update Project" to reschedule a task I believed to be 100% complete.
A task had 10 hours spread over 4 days using a rate of $25/hr and MSP has planned:
Monday
This totals 10hrs but only $249.99. Then if I enter the 10 hours as Actual work on Monday (which is normally done by a macro reading data from an excel file, but we get the same effect entering the data manually) we get the situation where the Actual Work is the same as the Work but the Actual Cost exceeds the Cost by $0.01 - the overall task is shown as 100% complete but the individual assignment shows as 99% complete.
This then causes our rescheduling process a problem because if I ask MSP to reschedule outstanding work MSP throws a bit of a wobbly and adds around 30 hours of work and actual work to the task in the process bringing Cost and Actual Cost back in line.
We are going to get around this by filtering the project so we don't attempt to reschedule when Remaining Work is zero but if anyone can shed some light on why MSP acts like this it would be appreciated.
Thanks
Kevin
I've had a little problem when using "Update Project" to reschedule a task I believed to be 100% complete.
A task had 10 hours spread over 4 days using a rate of $25/hr and MSP has planned:
Monday
2.8hr
$70
Tuesday2.8hr
$70
Wednesday2.8hr
$70
Thursday1.6hr
$39.99
This totals 10hrs but only $249.99. Then if I enter the 10 hours as Actual work on Monday (which is normally done by a macro reading data from an excel file, but we get the same effect entering the data manually) we get the situation where the Actual Work is the same as the Work but the Actual Cost exceeds the Cost by $0.01 - the overall task is shown as 100% complete but the individual assignment shows as 99% complete.
This then causes our rescheduling process a problem because if I ask MSP to reschedule outstanding work MSP throws a bit of a wobbly and adds around 30 hours of work and actual work to the task in the process bringing Cost and Actual Cost back in line.
We are going to get around this by filtering the project so we don't attempt to reschedule when Remaining Work is zero but if anyone can shed some light on why MSP acts like this it would be appreciated.
Thanks
Kevin