server >> help! Actual Work Billable/Timesheet mismatch...

by U2hhd24gRXZlcmluZ2hhbQ » Fri, 11 Apr 2008 00:03:03 GMT

Using the Reporting database, I have a query ... well, the joins are below...
So...We have bereavement time set up as a custom value for administrative
time. We are pulling all administrative time and pushing the info to our time
keeping system.

Here's the deal...
I pulled all the administrative time for the month of March, using
TimeByDay. One of our resources filled out their timecard for 40 hrs
bereavement, saved and submitted...self approved timesheet. I notice this on
my audit report, specifically because he claimed 9 hrs every day, when we
work 8 hr days. He indicated to me that he had corrected those entries, in
fact, changed that time off, from Bereavement to a Management category in his
timesheet for that week. He was basically questioning my report, because it
was showing the bereavement time, when in actuality, his timecard reflected
something totally different.

I have rebuilt the cube. Refreshed the data...I can't for the life of me
figure out why it still thinks he has bereavement time.

Can anyone help? my last few posts have gone unanswered. Maybe I'm treading
in uncharted territory. I need some answers...please help me if you know
what's up...

thanks in advance.

dbo.MSP_TimesheetActual as ta
inner join dbo.MSP_TimesheetResource_OlapView as tr
on tr.ResourceNameUID = ta.LastChangedResourceNameUID
inner join dbo.MSP_TimesheetLine_OlapView as tl
on tl.TimesheetLineUID = ta.TimesheetLineUID
inner join dbo.MSP_TimesheetProject_OlapView as tp
on tp.ProjectNameUID = tl.ProjectNameUID
inner join dbo.MSP_EpmResource_UserView as er
on er.ResourceUID = tr.ResourceUID
inner join dbo.MSP_Timesheet_OlapView as ts
on ts.TimesheetUID = tl.TimesheetUID
inner join dbo.MSP_TimesheetPeriod_OlapView as p
on p.PeriodUID = ts.PeriodUID
inner join dbo.MSP_TimesheetClass_OlapView as tc
on tc.ClassUID = tl.ClassUID
inner join dbo.MSP_TimesheetTask_OlapView as tt
on tt.TaskNameUID = tl.TaskNameUID


--
Technology, like art, is a soaring stretch of our imagination...Daniel Bell.
1919


Similar Threads

1. Actual Work vs. Actual Work Billable

Hello,

What is the difference between "Actual Work" and "Actual Work Billable" ?
In the timesheets, resources are not using Actual Work billable. They enter 
time only on Actual Work.
Timesheets have been validated, but the actuals are not imported in Project 
Pro.

I created two Data Analysis views:
- 1st based on MSP_Project_Timesheet cube, which displays the Actual Work.
- 2nd based on EPM Timesheet cube, which displays the Actual Work Billable 
(we don't have other choice)

1st pivot table (Actual Work) displays 0 values on months where there are 
some (expected) actuals
2nd pivot table (Actual Work Billable) displays the right values where there 
are some actuals.

Thanks for your help 


2. Actual work mismatch in Timesheet & Portfolio Analyzer

3. PS2007 - Actual work billable hours missing in 2 of 3 timesheet cu

Hi,

I need to create a data analysis view that provides actual work billable 
based on customized enterprise fields on task and on project level.
These fields are only available in the virtual cube MSP_Project_Timesheet. 
Unfortunately in this cube there are 0 hours, even without adding any 
dimensions to the view. Since I have read in "Implementing and Administering 
Microsoft Office Project Server 2007" that this cube is based on EPM 
Timesheet, I have also checked that one. There are also 0 hours for Actual 
work billable in there. EPM Timesheet in Analysis Server is referring to 
MSP_TimesheetActual_OlapView. In that view actual billable work is shown 
correctly. So I think something doesn work with building these 2 cubes. 
There are no errors when building the cube. Has anyone experienced something 
similar?
Moreover the hours are also shown in cube imesheet Unfortunately in that 
one I am missing the customized fields 
SP1 is applied, so is hotfix rollup SP1 since an issue with 
MSP_Project_Timesheet was mentioned. It didn help.

Any ideas are appreciated!

Regards
Barbara

4. Actual Work mismatch

5. Actual work mismatch in Resource Usage View

I apologise for this very long message. I request your patience.

I inherited a work plan that had been created by breaking a few MS-
Project rules. For example, resources and work  had been assigned at
the summary tasks level with the detailed sub-tasks being milestones.
The detailed sub-tasks drove the dates for the summary level. Tasks
were of type Fixed Duration and Fixed Units. The Summary tasks were
all Fixed Duration and the detailed tasks were a mix of Fixed Units,
Fixed Work and Fixed Units. We have a company policy that all tasks
shall only be Fixed Work.

To add to the confusion, the plan had not been baselined and people
already started to enter actuals through PWA at the summary tasks
level.

It has fallen upon me to "correct" the plan and bring it to company
standards.

What I did:

I deleted all the detailed sub-tasks (which were all milestones by the
way). This made all the original summary tasks (to which resources and
work had been assigned) as non-summary tasks. This was a desired
result. Unfortunately what this also did was to change the start dates
to the beginning of the project; and since these (originally) summary
tasks were Fixed Duration, this also changed the Finish dates to the
start date + duration.

This in itself is not much of a problem, I just changed the dates back
to what they were supposed to be. But there were already actuals in
some of these "summary" tasks, therefore when the dates got shifted
back and forth, the actuals for those days got blown away.

This again is not much of a problem since I could always "Adjust
Actuals" in PWA and re-enter everyone's actuals. But...  when I look
at the Resource Usage View of the plan (in the left part of the screen
where the resources are listed, I inserted the column "Actual Work"
and I see the total actuals for each resource) the total actual work
for each resource reflects the total actual work they entered,
however, the right part of the screen (where each day's work is shown)
when I look at the actual work, it does not total up to the total
actuals displayed in the left part.

Sorry about not being very clear, let me try to explain differently:

In the Resource Usage View, the right half, the Yellow part, I right-
clicked, unchecked "Work" and checked "Actual Work" so that I can see
the actuals for each day of the week.

In the left half, where the resources are listed, I added the column
"Actual Work".

Now the Actual work dislayed in the left part shoudl equal the sum of
all the actuals dislayed in the right half, right? It does not. The
left half displays the correct figure while the right half totals up
to either zero or some other value significantly less than the left
half.

I tried to see if the actuals got moved to some other period, but
could not find the actuals at all. I even tried to change the
timescale to the "Year" view and checked all years from 199x to 2045,
no actuals anywhere other than 2007 and they were not equal to the
values in the left half.

Any pointers on why this happens?

I could always delete the actuals for those resources and re-create
them from scratch, but then we are talking about 3 weeks' worth of
time entry for a 2000 line plan for about 25 resources.

By the way, after doing all this, I changed all the tasks to "Fixed
Work" and baselined the plan so that I could run the macros to
calculate the cost & schedule performances (again developed in-house).

6. Actual Work mismatch

7. Actual Overtime Work Billable

Hi..me again.

PS 2007, SQL Server 2005 Enterprise
I created Data Analysis for viewing total overtime for every resources, 
using EPM Timesheet or Timesheet Cube. and when i add total actual overtime 
work billable data show 0 hours. But if i check in MSP_Timesheet_Actuals in 
Published Database and MSP_TimeSheetActual in Reporting Database, the Actual 
Overtime Work Billable show in that both table...
can somenoe direct me how to solve this? 

thank you


 
 

8. Actual Work Billable blank in OLAP cube