Introduction
Oracle Fusion Global Human Resources has one predefined approval flow. Using Oracle JDeveloper, you can edit a copy of this flow and create additional approval flows for transactions that have different approval requirements.
The following figure shows the predefined approval flow.
-
When the transaction is submitted, it is routed automatically to the Worklist of the submitter's first-level manager, who is the first approver.
-
If the submitter's first-level manager approves the transaction, it is routed automatically to the submitter's second-level manager, who is the second approver.
-
If the submitter's second-level manager approves the transaction, it is committed to the database tables.
Approval Management configuration options for Oracle Fusion Human Capital Management determine most of the actions that are available to the participants in the approval process. For example:
-
Either approver can reject the transaction. By default, the approval process stops when the transaction is rejected.
-
The second-level manager can push the transaction back to the first-level manager, who then has a second opportunity to review the transaction and either approve or reject it, as appropriate.
-
Insertion of approvers in the approval list is permitted.
-
Approvers can delegate their approval responsibilities to other approvers.
If you change the default settings of the Approval Management configuration options for a task, then different actions or action outcomes become available to this approval flow.
Notifications
The following table summarizes who is notified at each event during the predefined approval flow.
Transaction Event |
Transaction Submitter |
Approver: First Level Manager |
Approver: Second Level Manager |
Routed for Approval |
|
Yes |
Yes |
Rejected |
Yes |
|
|
Pushed Back |
|
Yes |
|
Committed |
Yes |
Yes |
Yes |
In addition, either approver can request more information from the other approver, the transaction submitter, or both. Such requests don't affect control of the approval process, but the person from whom information is requested receives a Worklist notification.
Approval Management Default Configuration Options
Approval Management has the following default configuration options for all applications in the Oracle Fusion Human Capital Management family.
Configuration Option |
Default Value |
Effect of Default Value |
Ad hoc insertion of approvers |
True |
Ad hoc insertion of approvers in the approval list is allowed. Users who add approvers may also modify or remove the approvers that they add. |
Allow delegate |
True |
Approvers can delegate their approval responsibilities to other users. One approver replaces another, but the approver list is otherwise unaltered. |
Allow Pushback |
True |
An approver can push the transaction back to the previous approver, who thereby has a second opportunity to review the transaction. |
Allow Reassign |
True |
Any approver can reassign the approval to a different approver. The approval list is recalculated based on the new approver. |
Allow Request Information |
True |
Approvers can request more information from another approver or the person who submitted the transaction. |
Allow Self-Approval |
False |
The person who submits the transaction can't approve it. |
Allow Withdraw |
True |
The requester or an administrator can withdraw a transaction while the approval process is incomplete. Approvers who have already approved are notified of the withdrawal. The transaction is removed from the worklists of approvers who haven't yet approved. |
On Error Notify |
Human Resources Application Administrator |
A Human Resources Application Administrator is notified automatically when an error occurs. |
Period Before Task Expires |
None |
Approval tasks don't expire. |
Period Before Task Escalates |
None |
Approval tasks aren't escalated to other approvers. |
Escalated Approvers |
None |
Approval tasks aren't escalated to other approvers. |
Repeated Approver Frequency |
Once per approval |
An approver receives one notification per transaction, even when the approver appears multiple times in the approver list. |
Re-evaluate Approver List |
True |
The approver list is regenerated after every response. |
Rejection Outcome |
Stop All |
When an approver rejects a transaction, the approval process stops and the transaction is canceled. |
Comments
concerning this piece of writing, while I am also zealous of getting
knowledge.
RSS feed for comments to this post