Example of Multilevel Approval Rule Using Supervisory List Builder

Suppose you want to approve the budget version for baseline based on the budget cost. The higher the budget cost, the greater number of levels of approval needed for the budget.

• If the budget cost is $5000 or less, approval is required only from the project manager.
• If the budget cost is between $5000 and $20000, it needs approval from both the project manager and the project manager's superior.
• If the budget cost exceeds $20000, approval must be obtained from the project manager, the project manager's superior, and the superior's manager.

Budget Cost Greater Than	Budget Cost Same or Less Than	Levels of Approvals Required
0	5000	1
5000	20000	2
20000	No upper limit	3

In this scenario, edit the predefined rule set to route the budget version to a hierarchy using the Supervisory list builder based on the budget cost.

• First level approval rule to route approval to the project manager for budget cost that’s same or less than $5000.
• Second level approval rule to route approval to the project manager and the project manager's superior for budget cost that’s between $5000 and $20000.
• Third level approval rule to route approval to the project manager, the project manager's superior, and that superior's manager for budget cost that’s greater than $20000.

You must also find out the highest position in the job hierarchy so that you can implement this approval for any number of levels till the highest position in your hierarchy. In this example, we’ll consider the highest position in the hierarchy to be CEO.

Pre-requisite: Define jobs in Oracle Fusion Cloud HCM.

Follow these steps:

1. In the Setup and Maintenance work area, go to the Manage Task Configurations for Project Financial Management task.

   The BPM Worklist tool is displayed.

2. In the Tasks to be configured pane, search for the ApprovePlanVersion task, and click the ApprovePlanVersion link.
3. Click the Edit Task icon in the Tasks to be configured pane to open the task in edit mode.
4. Click the Assignees tab.

   The participants who must approve project budgets or forecasts are displayed. Click on each of these participants to review the workflow rules that apply to their approval choices.

5. Click the Approver participant in the workflow, click the Go to Rule (the diamond shaped) icon within the Approver box, and then click the Go to Rule option that appears.

   The list of rules associated with the Approver participant are displayed. Ensure that the BudgetForecastAMXRuleSet rule is selected in the drop-down list.

6. Change the IF condition of the predefined rules from 1 is 1 to 1 is 2 to disable the predefined workflow from sending project budget or forecast approvals to the project manager for approval.
7. Add the first level rule, as follows:
   1. In the Rules pane, click the Advanced Add or Modify Options (the + icon) drop-down list and select General Rule.
   2. Click the Properties link, enter FirstLevel in the Name field, add the description, verify that the Active checkbox is selected, and click OK.
   3. In the IF part of the rule, click the Advanced Add or Modify Options drop-down list and select simple test, and add the IF conditions as follows:

      Value to Enter in the Left Text Box	Value to Select in the Number Comparison Drop-down List	Value to Enter in the Right Text Box	Why to Add the IF Condition
      ApprovePlanVersionPayloadType.planClassCode Note that you can also select this value by clicking the Left Value search icon and selecting ApprovePlanVersionPayloadType.planClassCode in the Condition Browser dialog box.	is	"BUDGET" This value is case-sensitive. Include the quotation marks. Don't copy and paste this value. To meet similar requirements for forecasts, enter "FORECAST".	To specify that the rule is applicable only for budget versions.
      ApprovePlanVersionPayloadType.approvePlanPayload.summaryAmounts.pcBurdenedCost	isn't	null	To check if the burdened cost amounts are available.
      new BigDecimal(ApprovePlanVersionPayloadType.approvePlanPayload.summaryAmounts.pcBurdenedCost)	same or less than	5000.00	To check if the burdened cost is within the threshold limit.

   4. In the THEN part of the rule, click the Advanced Add or Modify Options drop-down list and select the Supervisory list builder by clicking Add Approver > Supervisory. Then, enter the values as follows:
      • Response Type: Required
      • Number of levels: 1
      • Starting Participant: HierarchyBuilder.getPrincipal(ApprovePlanVersionPayloadType.approvePlanPayload.approverName,-1,"","")
      • Top Participant: HierarchyBuilder.getPrincipal("john.doe",-1,"","")
        Note: john.doe is the username of the CEO.
      • Auto Action Enabled: False
      • Auto Action: null
      • Rule Name: “FirstLevel”
        Note: The rule name is auto-populated, it's the name that you entered in Step 7.
      • Dimension Id: null
        Note: The dimension ID is auto-populated as null.
8. Repeat Step 7 and make the following changes for the second and third levels of approval:
   • Enter the rule names as SecondLevel and ThirdLevel.
   • Enter the value in the IF condition as follows:
     • Second level: new BigDecimal(ApprovePlanVersionPayloadType.approvePlanPayload.summaryAmounts.pcBurdenedCost) between 5000.00 and 20000.00
     • Third level: new BigDecimal(ApprovePlanVersionPayloadType.approvePlanPayload.summaryAmounts.pcBurdenedCost) more than 20000.00
   • Enter the value in the THEN condition as follows:
     • 2 for second level and 3 for third level in the Number of levels field.
9. Click Validate on the top right corner to validate the newly defined rules.
10. Click the Save icon in the Tasks to be configured pane to save the rules.
11. Click the Commit task icon in the Tasks to be configured pane to complete the rule configuration.
12. Click OK to close the confirmation message window.