Approvals Management

SSHR actions use Oracle Approvals Management (AME), a rules-based expert system, to route actions via supervisory hierarchy (default), or routing list. Your implementation team can define business rules that generate a routing list automatically, ensuring that SSHR routes your action to the appropriate parties for approval. Your setup can designate approvers who record decisions by external authorities, such as unions or workers councils.

Pressing the Submit button on the Review page sends your action to an approval process that chooses the appropriate approvers automatically. Approvers receive a notification in their Worklist with a link to open the action, and (with update privileges) they can edit, change the effective date, or attach supporting documents. Approvers can return the action for correction to any previous approver on the chain. If you are the final approver, pressing Submit applies the action to the database.

The Review page also provides options to add approvers and select additional notification recipients.

Notifications

Workflow users receive notifications in their Worklist. Standard formats include:

• Approval Required

• Saved for Later

• Return for Correction

• FYI

• Queries from other approvers

When an approver or HR representative retrieves a notification requiring approval, the Notification Details page appears, providing notes and warnings related to the action. Notification Details provide the following options:

• Approve

• Reject

• Reassign

• Request Information

• View Action

• Update Action

• Return for Correction

Most options include an opportunity to provide comments or ask questions.

Updating an Action

Unless your implementation team has decided to have all actions take effect on approval, the Effective Date page appears when an approver opens an action. Any approver in the chain of recipients with update privileges can change the effective date here. Approvers may see messages or warnings about intervening or future-dated actions that the database has encountered. See Managing Conflicting Actions

Return for Correction

Any approver can return an action for correction to any previous approver on the chain. In order to make a change, recipients must have a workflow role that grants update privileges.

Transaction Data Changes in FYI Notifications

The FYI notifications display changes to the transactions that are either approved or rejected. The FYI notifications page displays a region with Proposed column to view transaction data changes and a Supporting Documents region to view any attachments added to the transaction. If any attachments are added to a transaction's Review page, then these attachments appear as a link on the FYI Notification page. For example, after a manager approves a leave of absence transaction, the recipient who receives the FYI notification can view the absence details that have been approved. The recipient need not navigate to the relevant self-service pages in the application to understand the changes that have been approved.