Scribd
Upload
111 views13 pages

Workflows Presentation

This document discusses Oracle HCM Workflows and Approvals in Fusion HCM. It defines workflows as automated processes that route tasks to users in a defined sequence. It provides examples of common tasks like absence approvals, promotions approvals, and terminations approvals. It discusses how tasks appear in users' worklists and how they are notified. It also covers how approvers, including multiple management levels, are set up and maintained for tasks. Considerations for task rule configuration like ensuring transactions match rules and using legislation codes are also mentioned.

Uploaded by

puduru lakshmikanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
111 views13 pages

Workflows Presentation

This document discusses Oracle HCM Workflows and Approvals in Fusion HCM. It defines workflows as automated processes that route tasks to users in a defined sequence. It provides examples of common tasks like absence approvals, promotions approvals, and terminations approvals. It discusses how tasks appear in users' worklists and how they are notified. It also covers how approvers, including multiple management levels, are set up and maintained for tasks. Considerations for task rule configuration like ensuring transactions match rules and using legislation codes are also mentioned.

Uploaded by

puduru lakshmikanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Oracle HCM Workflows and

Approvals

FUSION HCM TECHNICAL


Agenda
• Tasks
• Task definition
• Approvers
• Setup & Maintenance
• Business Process flows
• Considerations
• Practice
Workflows

Workflow is a process in which tasks are routed automatically among users for
their consideration or action. The tasks routed in defined sequence to achieve
a defined result.

A workflow human task is any workflow component that requires attention or


action from users. For example, a promotion request for a worker may require
approval from two levels of the manager hierarchy above the task submitter.

Workflow tasks for a user appear in the worklist: Notification and Approvals region
on the user’s welcome Dashboard, The user also receives email notification.
Tasks
• The following tasks have custom rules: • ResignationApproval (ESS)
• AbsencesApprovalsTask (ESS/MSS) • TerminationsApproval (MSS)
• ApprovalResponsibility (HR – Security)
• ChangeLocationApproval (MSS) • TransfersApproval (MSS)
• ChangeManagerApproval (MSS) • VariableAllocationTask (MSS)
• ChangeSalaryApprovalTask (MSS)
• ChangeWorkHoursApproval (MSS)
• ManageDirectsApprovalTask (MSS)
• PersonalInformation (ESS)
• PromotionsApproval (MSS)
Task definition
• A task is made of a set of rules:
• Each rule has a condition, and approvers
• If a rule condition is true, the approvers are
required
• If none of the rules meets the transaction, a
History Tree Table error occurs on the screen
Sample Flow
Approvers
• Line Managers. How many levels? If 2 or more, they approve
sequentially.

• Some countries use AOR Representatives


• Human Resources Representative
• Absence Representative
• Compensation Representative
• Some other use Approval Groups (application roles)

• It is very uncommon, but it is possible to use a specific User


Approvers
Setup and Maintenance

• There 2 tasks in Setup and Maintenance


• Manage Approval Transactions for Human Capital
Management
• Design is more friendly and visual
• Difficult to edit when a task has many rules
• Manage Task Configurations for Human Capital
Management
• Design is more technical
• Easier to edit when a task has many rules
Considerations
• Make sure each transaction matches one rule
• If using AORs, make sure each worker is under an AOR
representative
• Most rules need Legislation Code to be part of the condition
• Rule naming should include something short describing the
scenario
• Usually 2 letter country code + what differentiates from the other rules
• Keep all rules of a country together
• Management hierarchy approver is based on the requester
• In Most of the Task rules we use below conditions to create a rule
• LDG Code –Country
• Grades

•
• AbsencesApprovalsTask • PersonalInformation D05 C09
• ApprovalResponsibility • PromotionsApproval
D06 C10
• ChangeLocationApproval E01 C11
• ResignationApproval E02 C12
• ChangeManagerApproval • TransfersApproval E03 C12
• ChangeSalaryApprovalTask X01 CX1
• TerminationsApproval X02 CX1
• ChangeWorkHoursApproval • VariableAllocationTask X03 CX1
• ManageDirectsApprovalTask
Fusion Technical
Q&A

You might also like