How You Configure Spend Authorization Request Approval Rules
You can configure approval rules for approval of spend authorization requests. Oracle Business Process Management Suite (BPM) provides the UI to administer and manage approval rules.
A BPM Worklist administrator can access approval rules in the BPM Worklist if he is assigned the role if he is assigned the role of Financial Application Administrator (FUN_FINANCIAL_APPLICATION_ADMINISTRATOR).
When you submit a spend authorization request for approval, Expenses invokes the approval process. The approval process prompts a set of approval rules created in the BPM Worklist to build the list of approvers. After an approver responds to an approval notification, BPM sends an approval notification to the next approver. BPM continues sending approval notifications to the approvers in the approval hierarchy until all approvals are complete.
To configure or modify spend authorization rules, complete these steps:
-
In the Setup and Maintenance work area, use the following to navigate to the BPM Worklist:
-
Offering: Financials
-
Functional Area: Expenses
-
Task: Manage Expense Approval Rules
-
-
In the BPM Worklist, select the Task Configuration tab.
-
From the Tasks to be configured pane, select FinExmWorkflowSpendAuthorization.
-
Select the Assignees tab.
-
Click the Switch to Vertical Layout link. An approval hierarchy displays.
-
On the Authorization rectangle, click the diamond icon and select Go to rule.
The spend authorization approval flow contains a predefined rule set with its associated approvers as described in the following table.
Rule Set |
Approver |
---|---|
SpendAuthorizationRuleSet
|
Supervisor
|
SpendAuthorizationRuleSet: Approval by Supervisor
The predefined rule set for approval of spend authorization that uses the supervisory hierarchy is called SpendAuthorizationRuleSet. The predefined rule is as follows:
Approval by the immediate supervisor of spend authorizations with a total over 0
You can change the predefined rules, delete, or add rules as needed. The following table lists the parameters for the SpendAuthorizationRuleSet.
Rule |
Field |
Predefined Value |
Description |
---|---|---|---|
SpendAuthorizationMan-agerApprovalRule |
Condition |
AuthorizedTotal is same or greater than 0 |
Attribute that stores the spend authorization request total in the reimbursement currency. |
List Builder |
Supervisory |
The rule uses the supervisory hierarchy to retrieve approvers. |
|
Response Type |
Required |
The approval notification requires a response. |
|
Number of levels |
1 |
Number of supervisory levels required for approval completion. |
|
Starting Participant |
HierarchyBuilder.getManager ("supervisory",Task.payload .ownerUserName,-1,"","") |
Person for whom the spend authorization is requested. |
|
Top Participant |
HierarchyBuilder.getPrincipa l("FINUSER30",-1,"","") |
Last approver in the approval chain. Approval doesn't go beyond this participant in a hierarchy. To use this rule as is, you must change the predefined last approver user name to the last approver in your organization. Note:
This must be changed to reflect the last approver in your organization. |
|
Auto Action Enabled |
False |
Automatic approval action is disabled. |
|
Auto Action |
Null |
No automatic approval action. |
|
Rule Name |
SpendAuthorizationManagerRule |
Name of rule. |