Second level approval going to wrong resource

[BudOlly]

Hello,

We are implementing a two-stage approval route; each resource submits their
timesheet to their timesheet manager, and the timesheet manager then approves
and sets our Project Manager as the next approver. So, ALL the timesheets
funnel down to the Project Manager.

I have noticed the following odd behavior:

Resource 'A' submits to TM 'B'. 'B' has a TM 'C', who is different than
the PM 'D'. However, 'B' needs to send the approved timesheet from 'A' onto
the PM, 'D'. Since 'B' has 'C' as their TM, when 'B' approves 'A', and
selects 'D' as the next approver, the timesheet will go to 'C' instead.

The only explanation I can come up with for this behavior is that it has
something to do with me having the "Approve Timesheets" persmission under the
"Organization" category set to 'Allow' for both the timesheet manager 'C' and
the PM 'D'.

Does this make sense what I am doing? The main problem, I think, is that I
do not fully understand how to use the category-based permissions, and I do
not understand the difference between allowing 'Accept timesheets' as a
global permission vs. allowing 'Approve Timesheets' as a category permission.

Any help or clarity is greatly appreciated!

 

[Gary Chefetz]

BodOlly:

See if this FAQ helps you work this out:

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/ChainOfTimesheetApprovers.aspx