Task Control - Actual Start and Actual Finish Wrong data

FilipeCuango 

Thanks for the screen shot, it gave me what I needed to analyze your scenario. One interesting observation, not related to your questions but curious nonetheless, is that the projector was assigned at 50% yet you entered 240 minutes of work. That should result in a Peak value of 109% but your screen shot shows 100%. When I emulated your task the projector shows a 109% Peak value. I don't know why yours is different.

With respect to your question, the reason you get the schedule alert is because you have set the task as fixed duration. If the task type is fixed work or fixed units, you will not get the message. However, by entering the actual work value in the timescale data you are fixing (confining) the 5 minutes of actual work to that day (Monday). The total work for that resource is 11 minutes on Monday. To resolve the mismatch for Monday, Project adjusts the original 11 minutes on Monday to the actual 5 minutes on Monday but Project needs to do something with the remaining 6 minutes so it alerts you that the 6 minutes will need to move to the next day, thus the conflict with the fixed duration of the task.

You can avoid this problem by entering the 5 minutes into the Actual Work field on the left side of the screen. That still leaves 6 minutes of remaining work for that resource but you have not "committed" the 5 minutes of actual work to Monday only so the fixed duration can still be valid and no alert will be issued.

So what to do with the 6 minutes remaining work for that resource? If the resource is all done, set remaining work to zero and Project will adjust the work value to be the actual work value of 5 minutes. If the resource is not done, then you need to decide if the resource will perform the remaining 6 minutes of work on Monday or will it indeed flow into the next day.

Something to wrap your head around.

John