Req Approval - User Action Task Question

What version are you? 80x or 90x?

Please read thru processflow administraion guides to understand how users/task are set up. An approver can have
one or many levels of approval. You will have to define who are the level approvers (it could be a janitor or CEO). If your requesting location only have one level of approver then you will define the same approver from level 1 to level 5.

Thank you Sam for your response! We are 9.0.0.6 apps and 9.0.0.7 env. I have the levels set up correctly according to the manual, but was trying to avoid having an approver respond twice to one requisition. If a requisition is $900, the flow would send it to Level 1 and Level 2. What if Level 1 and Level 2 are the same person? Is there a way to keep the approver from having to approve twice?

Are you still confuse? In 90x you have to use RM(ldap) to get the approver levels based on RQH-REQUESTER. Create two variables called rqlevel and rqparent. Rqlevel could be the requester, manager or Director and rqparent could be the somebody above level1. In ldap every requester has both USRRQLEVEL and USERRQPARENT and you have to save this every time a loop is made in LDAP. The value of USERRQLEVEL and USERRQPARENT could be anything from "Requester", "Manager" or "CEO".

So before going to who's inbasket you will test the threshold like:

If Amount <= 500 && rqlevel = 'Manager' || Amount <= 1000 and rqlevel = "Director" ||...etc then go to the
in-basket otherwise loop thru ldap this time using the saved USERRQPARENT.

In your case, it will bypass the "Manager" and loops again and get the "Director". Since "Director" is level 2, the
amount is approved because it is less than 1000.

We are also a Hospital company and like you we have different levels of approver. We even test for budgets and or source of budgets and fiscal years.

Forgot to include WFMETRICs. Before looping to the next level, you have to get the next level of approver from WFMETRICs (WF-RM-ID).

Sam, again, I thank you for your help. I am attempting to implement what you have explained here into our current design. I will repost to let you know how it goes!