This content has been marked as final. Show 5 replies
Amit, are you running r12.0? I've been told that AME isn't stable for this particular release and is therefore not recommended.
We use approval groups for our signing authority. They key off the job code of the employee, so if you have a generic HR structure this is a pretty easy option. I think it is easier to maintain than AME.
Thanks for the reply. We are on 11i.
We have to use AME as approver list has many dynamic approvers which needs to be added through approver groups. If we want to make the limits dynamic in AME rules , what is the best solution?
Hi Amit,1 person found this helpful
Whenever we want to extend AME to be more flexible for the "Business User (The person who does not have Approvals Management Business Analyst responsibility)" Its always recommended to take a Lookup Route. You can define a User Lookup storing the Upper limit and Lower limit with description for each case.
Use this lookup to extract this on to the REQUISITION_TOTAL attribute using a customization. This would be my take, I will leave it on the forum for a better solution.
Thanks a lot for your reply.
Yes you are right, we can use lookups to maintain the approval limits. However there are probably two ways in which we can proceed.
1st Approach :
We make one AME rule and put all the approver groups in the same rule. Then based on the requisition amount and the approval limit of approver , approver groups will be populated and approval list will be generated. There will be empty approver groups. Calculation of requisition total and approver approval limit will be handled by the Pl/SQL code.
2nd Approach :
We make custom AME attributes to store the approval limit for each approver and make different rules and compare requisition total with these custom attributes and accordingly approval list will be generated.
I think 2nd approach is better from debugging perspective. What is your take on the approaches? Thanks !
- You can create an AME attribute RequisitionTotal .
- Then create a condition if RequisitionTotal > 0 and less than 100.
- You can then create a rule where this condition is applied.