Actual Work Updates cause Data Corruption - MSP 2003

[Graham]

I'm using MSP 2003 and have tested this scenario using managed and
non-managed time periods and reach the same conclusions. We have
installed hot fix 830820 to solve the issue of notifications of
overdue timesheets due to administrative projects.

When a resource modifies time on a task by deleting previously
accepted actuals. The deletion isn't updated in the project schedule,
while the time is deleted in the timesheet!!!!

This causes timesheet entries to be different from the project
schedule and will lead to serious differences between project
schedules and timesheets.

Our conclusion is that resources cannot delete time using the delete
button, but must instead enter zeros. If zeros are used then the
project schedule is updated correctly.

Is this a known issue that a patch is available for? I suspect that a
stored procedure doesn't recognize nulls as zeros somewhere.

Any insight would be appreciated.

Thanks,
Graham

 

[ITG_Mike]

Graham

We have seen the same behavior as you report. Deleting a (previously updated) entry on ones task list does not update the time reported in project. The resource must enter zeros and then update those zero entries

Perhaps someone knows of a fix for this, but I do not

On a related note, it is problems like these that have caused my company to do all of oour financial reporting (How many hours were spent on project X in 1Q04) based on the data in the task list (web) database, not in the project database. The data in the project DB is prone to inaccuracies (like the one you identified)

Mike