Decimal rounding issue when actual work greater than planned.

[Binoy]

Hi,

I have an issue with Microsoft Project rounding up/down (?) values for
work/actual work.

e.g.
Add a task with a duration of 20 days (Task type as fixed duration)
Create an assignment with resource 'A' for this task. (Rate defined as 1$/hr)
Enter Work as 100hrs. Units calculated as 61%
Enter Actual Work as 100.46 and click on Ok.
Notice that Work and Actual Work are changed to 100.47hrs (?). Units remains
61% and duration is 20 days.

I would like to know why the work/actual work was changed to 100.47 (from
100.46). What are the calculations that Project internally does to arrive at
this value?

Thanks
Binoy

 

[Jan De Messemaeker]

Hi,

100.46 hr= 6027,6 minutes (the only unit Project calculates with) rounded to
6028
6028 min = 100,46666 hrs rounded to 100,47

If you want that precision enter all work and actual work in minutes.
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[Binoy]

Thanks to all for the help.

The reason why this rounding off creates an issue is because we have an
integration with Microsoft Project.
The scenario is as follows,
We bring in the planned and actual values ... e.g. 50122.46
Duration is 30 days (Fixed duration)
In our integration code, we first set the planned work. Next, we set the
actual work. At this point, for the assignment, it shows planned as 51022.45
and actual as 50122.46.
If I then send this project file to our integration system, it causes an
issue with our validation code (which validates that the planned is not less
than actuals).

To overcome this, I have now added a condition immediately after setting the
actual work. i.e. if actual >= planned then set value of actual work into
planned work field. This has fixed the issue.

Comments/suggestions are welcome.

Thanks,
Binoy