End-to-End Guide to Enterprise Shifts, Work Pattern Types and Work Pattern Template Rules in Oracle HCM
Excerpt:
This article demonstrates how to configure Enterprise Shifts, Work Pattern Types, Work Pattern Templates, and Template Rules in Oracle HCM Cloud. Using a practical example, we assign a work pattern at the Legal Employer level while excluding workers with manual exceptions, and explain how the Process Events job evaluates and applies these rules.
Oracle HCM Cloud Workforce Scheduling provides a structured way to standardize employee schedules across large populations. Instead of assigning schedules manually, organizations can define reusable components and automate assignment using rules.
This blog walks through an end-to-end configuration using:
- Enterprise Shifts
- Work Pattern Types
- Work Pattern Templates
- Work Pattern Template Rules at the Legal Employer level
- Process Events job
Business Requirement
All employees under a specific Legal Employer should receive a standard work pattern:
- 08:00 AM to 05:00 PM - 60 mins unpaid break
However, employees with manual scheduling exceptions must be excluded. For example, employees manually assigned to 01:00 PM to 10:00 PM - 60 mins unpaid break should not be overwritten by the rule-based assignment.
Step 1: Create Enterprise Shifts
Enterprise Shifts act as reusable building blocks for scheduling.
Navigation
My Client Groups > Workforce Scheduling > Shifts
Click the Add button.
| Configuration Field | 1st Shift | 2nd Shift |
|---|---|---|
| Shift Name | 08:00 AM to 05:00 PM - 60 mins unpaid break | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Duration | 8 | 8 |
| Work Minutes | 0 | 0 |
| Start Time | 08:00 AM | 01:00 PM |
| End Time | 05:00 PM | 10:00 PM |
| Unpaid Break Duration | 60 Minutes | 60 Minutes |
Key Insight
- 9-hour span
- 8 paid hours after break deduction
Step 2: Create Work Pattern Types
Work Pattern Types define how shifts are structured.
Navigation
Setup and Maintenance > Workforce Scheduling > Work Pattern Types
| Configuration Field | Values for the 1st Work Pattern | Values for the 2nd Work Pattern |
|---|---|---|
| Shift Period Type | Start and end times | Start and end times |
| Name | 08:00 AM to 05:00 PM - 60 mins unpaid break | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Country | United States | United States |
| Status | Active | Active |
| Break Name | 60 mins unpaid break | 60 mins unpaid break |
| Break Duration | 60 Minutes | 60 Minutes |
| Break Type | Any time during shift | Any time during shift |
| Nature of Break | Unpaid | Unpaid |
Because this setup uses exact start and end times, a start/end-based work pattern type is the right choice.
Step 3: Create Work Pattern Templates
Templates define recurring schedules that can be assigned to groups.
Navigation
My Client Groups > Workforce Scheduling > Work Pattern Templates
a) Template Name: 08:00 AM to 05:00 PM - 60 mins unpaid break
Work Pattern Type: Fixed Start-End Pattern
Cycle Length: 1 Week
| Day | Shift |
|---|---|
| Monday | 08:00 AM to 05:00 PM - 60 mins unpaid break |
| Tuesday | 08:00 AM to 05:00 PM - 60 mins unpaid break |
| Wednesday | 08:00 AM to 05:00 PM - 60 mins unpaid break |
| Thursday | 08:00 AM to 05:00 PM - 60 mins unpaid break |
| Friday | 08:00 AM to 05:00 PM - 60 mins unpaid break |
| Saturday | Off |
| Sunday | Off |
b) Template Name: 01:00 PM to 10:00 PM - 60 mins unpaid break
Work Pattern Type: Fixed Start-End Pattern
Cycle Length: 1 Week
| Day | Shift |
|---|---|
| Monday | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Tuesday | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Wednesday | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Thursday | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Friday | 01:00 PM to 10:00 PM - 60 mins unpaid break |
| Saturday | Off |
| Sunday | Off |
Step 4: Define Work Pattern Template Rule
This is where automation happens.
We will create the work pattern template rule for 08:00 AM to 05:00 PM - 60 mins unpaid break.
Navigation
My Client Groups > Workforce Scheduling > Work Pattern Templates > Assign
Example Rule Logic
Include Criteria
- Legal Employer = ABC Corporation
- Oracle Work Pattern Source <> 'Manually Assigned'
This rule ensures that all eligible workers under the legal employer receive the standard day pattern, while workers already maintained manually are excluded from automated reassignment.
Step 5: Run Process Events
This is the critical activation step.
Navigation
Tools > Scheduled Processes
Process Name: Process Events
Parameters
- Effective Date: 3/18/2026
- Events to Process: Workforce Scheduling
The log files provide details about how many employees were processed and how the rule evaluation was applied.
How Process Events Works
Think of Process Events as the engine that applies your Workforce Scheduling rules.
What it does
- Detects HCM changes, such as new hires, transfers, legal employer changes, and assignment updates.
- Evaluates template rules by checking legal employer eligibility and excluding manually assigned work patterns.
- Generates scheduling assignments by assigning the template to eligible workers and skipping excluded workers.
Currently, Oracle supports multiple Workforce Scheduling events, and Process Events is the process that reacts to those changes and applies the configured logic.
End-to-End Flow Summary
- Create shift → 08:00 AM to 05:00 PM
- Create pattern type → Start-End based
- Create template → Weekly recurring schedule
- Define rule → Legal Employer based
- Run Process Events → Apply logic
Testing the Solution
Scenario 1: New Hire
- Legal Employer = ABC
- No manual exception
- Run Process Events
- Expected: work pattern assigned
After Position Change and running Process Events -
Scenario 2: Position Change and Missing Work Pattern
- Legal Employer = ABC
- Manual Exception = No
- Run Process Events
- Expected: work pattern assigned
Before Position Change -
After Position Change and running Process Events -
Scenario 3: Position Change and Manually Assigned
- Legal Employer = ABC
- Manual Exception = Yes
- Run Process Events
- Expected: No work pattern change
Before Position Change -
After Position Change and running Process Events -
Scenario 4: Job Change and Existing Work Pattern
- Legal Employer = ABC
- Manual Exception = Yes
- Run Process Events
- Expected: No work pattern change
Before the position change -
After Position Change and running Process Events -
Troubleshooting
Issue: Template not applied
- Verify rule criteria.
- Check worker attributes.
- Run Process Events.
Issue: New hires not assigned pattern
- Ensure Process Events is scheduled regularly, such as daily or hourly.
Final Thoughts
A well-designed Workforce Scheduling setup in Oracle HCM Cloud should use Enterprise Shifts as reusable units, Templates for scalability, Rules for automation, and Process Events for execution.
In this example, applying scheduling at the Legal Employer level with controlled exclusions ensures both standardization across the workforce and flexibility for exceptions.
Author Note
This blog reflects a practical implementation pattern for Workforce Scheduling in Oracle HCM Cloud. Always validate configurations in your own environment and align rule design with your organization's data governance strategy.
.png)
No comments:
Post a Comment