We've had a number of good questions come in. I thought it would be helpful to share these and the answers. Enjoy!
Question: Which is true?
Case 1: Does the assigned timesheet manager approve all tasks in the timesheet (for example, project tasks as well as administrative time tasks) OR
Case 2: Does the resource manager (i.e. the assigned timesheet approver) approve administrative time AND the project manager of the project the tasks originally came from approve the project tasks?
SUMMARYThe Resource manager approves all timesheet data. If the Admin timesheet categories require approval outside of timesheets, those are also approved by the timesheet manager.
LOOPING THE PM INTO THE APPROVAL CHAINThe current timesheet submitter/approver can change the value of the next person to approve the timesheet. Using this setting, the PM can be sent the timesheet to approve. As long as the PM doesn't have the category approval permission for that resource, the PM can send the timesheet back to the resource manager for final approval. One manages actual work while the other manages compliance with company policies.
Question: I'm using Project Professional and I need to answer the following questions:
In Project Professional, you can define a filter to show you this. The filter will prompt you for a date so you can use this to see finishing by any date.
The way we do this internally is to define a task level custom field. You would then assign a milestone value to each task.
Add a new task custom field to the Project.
By the way, all of these filters can be used together. So, by applying all three filters, I can see for a given milestone, within Milestone 1, which tasks will be completed by X date.
From Jim Corbin. The technical article Importing Project 2007 Tasks from Excel Using a Managed Code Add-In is now published on MSDN. There is an associated download that includes the complete C# and VB.NET code, using Visual Studio 2008 (Beta 2) with Visual Studio Tools for Office.
It appears part of the where clause is missing on the published Timesheet Audit report. The result is that the weekly totals are all the same for each resource.
To correct this, replace the SQL with the code below. The addition is in bold below.
SELECT MSP_EpmResource.ResourceName, MSP_TimesheetPeriod.PeriodName,
MSP_TimesheetPeriodStatus.Description AS PeriodStatus,
MSP_TimesheetStatus.Description AS TimesheetStatus,
AS TotalWork, MSP_TimesheetPeriod.StartDate, MSP_TimesheetPeriod.EndDate,
FROM MSP_EpmResource LEFT OUTER JOIN
MSP_TimesheetResource INNER JOIN
MSP_TimesheetActual ON MSP_TimesheetResource.ResourceNameUID =
MSP_EpmResource.ResourceUID = MSP_TimesheetResource.ResourceUID
LEFT OUTER JOIN
MSP_TimesheetPeriod INNER JOIN
MSP_Timesheet ON MSP_TimesheetPeriod.PeriodUID = MSP_Timesheet.PeriodUID INNER JOIN
MSP_TimesheetPeriodStatus ON MSP_TimesheetPeriod.PeriodStatusID =
MSP_TimesheetPeriodStatus.PeriodStatusID INNER JOIN
MSP_TimesheetStatus ON MSP_Timesheet.TimesheetStatusID =
MSP_TimesheetResource.ResourceNameUID = MSP_Timesheet.OwnerResourceNameUID
WHERE (MSP_EpmResource.ResourceTimesheetManagerUID = @TimeSheetManager)
AND (MSP_TimesheetActual.TimeByDay BETWEEN MSP_TimesheetPeriod.StartDate AND MSP_TimesheetPeriod.EndDate)
GROUP BY MSP_TimesheetPeriod.PeriodName, MSP_TimesheetPeriodStatus.Description,
HAVING (MSP_TimesheetPeriod.PeriodStatusID = 0) OR
(MSP_TimesheetPeriod.PeriodStatusID IS NULL)
For your information, this report includes time logged in any open time periods. The report was designed assuming you are closing timesheet periods on a regular basis. Closing prevents time from being applied to an incorrect period. If you are billing for your time, this is real important. Anyway, if you aren't closing periods, this report will continue to get grow wider as columns are added for each open period.
We apologize for any inconvenience.