none
Effects of Rejecting Timesheet in Single Entry with Line Approval Required RRS feed

  • Question

  • We are running Project Server 2010 withthe April CU.  We have enabled Single Entry Mode as well as "Require line approval before timesheet approval".  What this means is that the Project Managers get to see and approve the time on their schedules before the Resource Managers get to approve the timesheets.

    My question is, if the the Resource Manager chooses to Reject a timesheet then the Timesheet goes back to the Team Member to change and resubmit.  Is that the only option?  So, if the Project Manager has already accepted the hours then any change to the Timesheet by the Team Member (to make the Resource Manager happy) would impact the project actual hours (and make the Project Manager unhappy).  And, what if the Project Manager has already "Closed Tasks to Updates" so that the Team Member can't send updates.

    What is the best way to keep everyone happy?  Should the Project Managers be required to keep the tasks "open for updates" until the Resource Managers have had their say on whether to accept or reject the timesheet?

    Thanks,

    Jim Mac.


    • Edited by Mac. Jim Thursday, July 14, 2011 8:31 PM Fixed Typographical error
    Thursday, July 14, 2011 8:01 PM

Answers

  • I think your PMs might be a little quick on the closing to updates trigger. Either that or the Resource managers are being too slow to review timesheets. either way I think the solution here is operational policy rather than system settings.

     

    Sorry. :-)


    --- Brian Kennemer Web: http://www.deltabahn.com Blog: http://www.projectified.com
    Thursday, July 14, 2011 10:37 PM
    Moderator
  • Hi Jim,

    good questions :) but I do agree with Brian, A system should not manage, it should maintain the data required. Out of the box what currently happens is that the Status Manager needs to approve the tasksk before the timesheet manager can. The timesheet manager could reject the timesheet for several reasons, but if he rejects it because of a project, he should notify the PM. You may say, " I want at least a notification as a PM if the Timesheet Managers rejects that timesheet". I argue that this would be annouing for all PM's ( should the resource work on several projects, or admin tasks that have been rejected) to receive a notification. That's why I also believe that the right process is required to be implemented. Simple rules like" Timesheet manager lets PM know if it is on one of his tasks". That will allow the PM to open the task for update again, etc.

    Anyway, my 2 cent :) You do have of course another option, that would be to develop your own workflow. Project Server certainly allows you to get the 100% solution if this is required. If you like to do so, check out the Project Server SDK, wich I am sure will be most helpful.

    Hope this helps


    Marc Soester [MVP] http://marcsoester.blogspot.com
    Sunday, July 17, 2011 5:55 AM
    Moderator

All replies

  • I think your PMs might be a little quick on the closing to updates trigger. Either that or the Resource managers are being too slow to review timesheets. either way I think the solution here is operational policy rather than system settings.

     

    Sorry. :-)


    --- Brian Kennemer Web: http://www.deltabahn.com Blog: http://www.projectified.com
    Thursday, July 14, 2011 10:37 PM
    Moderator
  • Hi Jim,

    good questions :) but I do agree with Brian, A system should not manage, it should maintain the data required. Out of the box what currently happens is that the Status Manager needs to approve the tasksk before the timesheet manager can. The timesheet manager could reject the timesheet for several reasons, but if he rejects it because of a project, he should notify the PM. You may say, " I want at least a notification as a PM if the Timesheet Managers rejects that timesheet". I argue that this would be annouing for all PM's ( should the resource work on several projects, or admin tasks that have been rejected) to receive a notification. That's why I also believe that the right process is required to be implemented. Simple rules like" Timesheet manager lets PM know if it is on one of his tasks". That will allow the PM to open the task for update again, etc.

    Anyway, my 2 cent :) You do have of course another option, that would be to develop your own workflow. Project Server certainly allows you to get the 100% solution if this is required. If you like to do so, check out the Project Server SDK, wich I am sure will be most helpful.

    Hope this helps


    Marc Soester [MVP] http://marcsoester.blogspot.com
    Sunday, July 17, 2011 5:55 AM
    Moderator