Entering actuals creates strange splits in tasks

[Galbers]

I have Project Server set up so that team members enter task actuals using
the "Hours of work done per day or per week" method. The problem I am getting
is that when the project plan is updated with these actuals individual tasks
are split to reflect the specific day that the actual hours were entered
against (which is fine) but once a task is complete there is an additional
"split" at the end of the task with no remaining work to be done.

What this effectively does is to push out all the successor tasks by the
duration of this dummy split. As the task is complete and there is no obvious
reason for this additional split (resource overallocation etc) then it is
screwing up the whole plan. If I manually set the finish date to when the
task actually completed then the plan is back in line (i.e. there are no
other dependencies in there causing the problem). In fact, when I look at the
Adjust actuals view for the particular task the Finish date is correct, it is
only in the project plan itself that the finish date is incorrect.

Does anyone have any ideas as to what would be causing this peculiar
behaviour?

Thanks.

 

[Dale Howard [MVP]]

Galbers --

Are you using Fixed Duration tasks, by chance? This behavior is what
happens with a Fixed Duration task when the task is completed earlier than
its scheduled Finish date. To reset the task and remove the trailing split,
set the Task Type for the task to Fixed Units. Let us know...

 

[Galbers]

Hi Dale,

Thanks for the response but no, they are all Fixed Units tasks.