Inconsistant hours in Reporting DB and Timesheet cube/Timesheet vi

[Flemming Goldbach]

We have been user testing Project Server 2007 incl. timesheet functionality
for a while now, where we have created a report (using reporting services
against the _Reporting DB) to list out time usage.

A couple of times now we have experienced an inconsistancy between what is
queried from the _Reporting DB) and what is shown in timesheet views and in
the Timesheet cube.
(and it is not just related to the delay before updates are replicated to
the _Reporting DB)

I seems to be related to when a resource enters hours in their timesheet on
a given timesheet line (seen it both on Administrative and Project tasks)
Submits, Recalls and then delete the hours on that given line and resubmits.

Is this a known issue or are we doing something wrong?

 

[Flemming Goldbach]

Yes, we are running SP1 + Inf.Upd + SP2

Flemming:

This very well may be a known issue. Have you installed SP2?

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Flemming Goldbach]

We've found the cause of the problem, it was a mistake from our side, due to
the way that adjustments to timesheet data are stored in Project Server 2007
Reporting DB.

It seems that in order to maintain audit trail of timesheet data
adjustments, Project Server 2007 saves all adjustments to a certain
timesheet-actual record, ex. if a line reads 3 hours, and is adjusted to 2
hours, Project Server will save records: one with the 3 hours, one with -3
hours and one with 2 hours, and an adjustment index to tell which is the
lastest one.

Our SQL query returned all > 0 timesheet actual record, which meant that if
timesheet adjustment put a line to 0 hours, we would only get the original
un-adjusted hours, and not the minus adjustment or the end-result 0.

Tricky.