Approver Types

You can include any number of approvers of various types in your approval sequence by dragging and dropping them into the approval flow. This topic explains each of the approver types.

Management Hierarchy or Supervisory Hierarchy

You can include the following predefined types of managers in your approval sequence:

• Line manager

• Resource manager

• Project manager

• Regional manager

If your enterprise defines additional types of managers, then they appear automatically in the Approvers section of the Manage Approval Rules page. You can include them in the approval sequence.

Users

You can include one or more Oracle Fusion Applications users in the approval sequence.

Approval Groups

You create approval groups using the BPM Worklist. When defining your approval sequence, you can enter the names of one or more existing approval groups.

Position Hierarchy

If you include a position hierarchy in your approval sequence, then position holders are invited to approve the transaction. For positions with more than one position holder, the transaction is approved by the first position holder to approve.

Responsibility Holders

You can include holders of the following predefined responsibilities in your approval sequence:

• Human Resources Representative

• Benefits Representative

• Union Representative

• Payroll Representative

If your enterprise defines additional responsibility types, then they appear automatically in the Approvers section of the Manage Approval Rules page. You can include them in the approval sequence.

Human Resource (HR) Specialists assign responsibilities to workers using the Manage Areas of Responsibility task. A worker becomes an approver for a transaction if he or she has that responsibility for the transaction subject. For example, if you specify the Benefits Representative as an approver for a promotion, then the Benefits Representative of the worker who is being promoted is invited to approve the promotion.

The application routes approval notifications to representatives by first checking if the configured Representative Type has an active assignment on the current date. If no representative has an active assignment on the current date, the notification is routed to the representative who is active as of the effective start date of the transaction.

Note: If you use a responsibility holder, then ensure that responsibility holders are already defined in the application. For example, if you include a HR representative as an approver for an employee process, then all employees must have HR representatives assigned to them.

Application Roles

You can use any of the existing duty roles to include in your approval sequence. If your enterprise defines duty roles for security purposes, then you can enter the duty role to include them in the approval sequence. Users with job or data roles that inherit the duty role become transaction approvers.

Job Level

You can include a job level in your approval sequence.

Job level routings are based on the manager hierarchy defined in Oracle Fusion Human Capital Management. The approval list is generated based on the starting level specified in a rule and continues until an approver with a sufficient job level is found. The approval flow uses the job level defined in the Manage Jobs interface.