We have 450+ unique jobs that we need to accomodate in our approval hierachy and in order to avoid a maintenance nightmare with PO Approval Groups, are looking to build business rules to point to the AP signing limits table (used for iExpense) to derive our approvers by cost centre. This table provides all needed approvers as well as limits by cost centre. Has anyone else used this approach or have alternate suggestions or comments on this approach? Appreciate any input.
I would suggested that In a Dev envronment, enable the PO Requisition Approval transaction type
and test by creating a Approver Group with type as Dynamic, their you can provide a SQL looking at approvers from the iExpense tables.
This will build your list of approver list dynamically. There are examples all over the net on how to create a dynamic approver group.
You will also have to write a generic AME rule so that the PO Requisition Approval process gets triggered.
It does not take much time to test it out.