Showing posts with label Oracle Cloud Workforce Scheduling. Show all posts
Showing posts with label Oracle Cloud Workforce Scheduling. Show all posts

Wednesday, 18 March 2026

End-to-End Guide to Enterprise Shifts, Work Pattern Types and Work Pattern Template Rules in Oracle HCM

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

DayShift
Monday08:00 AM to 05:00 PM - 60 mins unpaid break
Tuesday08:00 AM to 05:00 PM - 60 mins unpaid break
Wednesday08:00 AM to 05:00 PM - 60 mins unpaid break
Thursday08:00 AM to 05:00 PM - 60 mins unpaid break
Friday08:00 AM to 05:00 PM - 60 mins unpaid break
SaturdayOff
SundayOff




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

DayShift
Monday01:00 PM to 10:00 PM - 60 mins unpaid break
Tuesday01:00 PM to 10:00 PM - 60 mins unpaid break
Wednesday01:00 PM to 10:00 PM - 60 mins unpaid break
Thursday01:00 PM to 10:00 PM - 60 mins unpaid break
Friday01:00 PM to 10:00 PM - 60 mins unpaid break
SaturdayOff
SundayOff




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

  1. Detects HCM changes, such as new hires, transfers, legal employer changes, and assignment updates.
  2. Evaluates template rules by checking legal employer eligibility and excluding manually assigned work patterns.
  3. 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

  1. Create shift → 08:00 AM to 05:00 PM
  2. Create pattern type → Start-End based
  3. Create template → Weekly recurring schedule
  4. Define rule → Legal Employer based
  5. 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.

Sunday, 15 March 2026

Use Case: Managing Different Public Holiday Schedules for Different Segments of the Workforce

Use Case: Managing Different Public Holiday Schedules for Different Segments of the Workforce

Organizations with diverse operational models often require different public holiday schedules for different segments of the workforce. For example, corporate office employees may observe the full set of public holidays, while manufacturing facilities may operate on reduced holiday schedules to maintain production continuity.

Oracle Fusion Cloud HCM 25D Organization Calendar Events enables organizations to manage holidays and organizational events centrally through configurable calendars. However, when implementing this feature for different worker populations, it is important to understand the current design constraints of the feature.

This use case illustrates how an organization can configure separate public holiday calendars for US manufacturing and US non-manufacturing employees. :contentReference[oaicite:0]{index=0}


Business Requirement

A company operates multiple work locations across the United States with two major workforce populations:

1. Non-Manufacturing Employees

  • Corporate offices
  • Administrative staff
  • Sales and support teams

2. Manufacturing Employees

  • Factory workers
  • Production teams
  • Plant operations staff

The organization follows a standard US public holiday calendar for most employees. However, manufacturing plants operate on a modified holiday schedule due to production requirements.

Non-Manufacturing Employees

Corporate employees observe the full US public holiday schedule:

  • New Year’s Day (1/1/2026)
  • MLK Day (1/19/2026)
  • Presidents’ Day (2/26/2026)
  • Memorial Day (5/25/2026)
  • Juneteenth (6/19/2026)
  • Independence Day (7/4/2026)
  • Labor Day (9/7/2026)
  • Veterans Day (11/11/2026)
  • Thanksgiving Day (11/26/2026)
  • Christmas Day (12/25/2026)
  • Winter Break 1 (12/26/2026)
  • Winter Break 2 (12/27/2026)
  • Winter Break 3 (12/28/2026)
  • Winter Break 4 (12/29/2026)
  • Winter Break 5 (12/30/2026)
  • Winter Break 6 (12/31/2026)

Manufacturing Employees

Manufacturing plants observe only a subset of these holidays:

  • New Year’s Day (1/1/2026)
  • MLK Day (1/19/2026)
  • Presidents’ Day (2/26/2026)
  • Memorial Day (5/25/2026)
  • Juneteenth (6/19/2026)
  • Independence Day (7/4/2026)
  • Labor Day (9/7/2026)
  • Veterans Day (11/11/2026)
  • Thanksgiving Day (11/26/2026)
  • Christmas Day (12/25/2026)

Winter Break holidays (12/26/2026 – 12/31/2026) are not observed because the plant continues production during those periods.

The organization therefore requires:

  • A US Corporate Holiday Calendar for non-manufacturing employees
  • A US Manufacturing Holiday Calendar for plant employees

Configuration Approach

To implement this requirement using Organization Calendar Events, the organization configures:

  1. Define Organization Calendar Events
  2. Create Separate Organization Calendars
  3. Create Calendar Rules
  4. Assign Calendars to Workers

Step 1: Define Organization Calendar Events

First, administrators define the public holiday events that will be used across calendars.

Examples include:

  • New Year’s Day
  • MLK Day

Navigation:

Setup and Maintenance → Calendar Events

Create all 16 calendar events as defined earlier.





Important Note:

If you do not see the Redwood page for Calendar Events, enable the following profile option:

ORA_ANC_VBCS_ORG_CAL_EVENT_ENABLED = Y

Navigation:

Setup and Maintenance → Manage Administrator Profile Values

Step 2: Create Separate Holiday Calendars

US Non-Manufacturing Holiday Calendar

This calendar contains the full set of US public holidays observed by corporate employees.

It is assigned to workers in corporate offices and administrative roles through the work location.



US Manufacturing Holiday Calendar

This calendar contains only the holidays applicable to plant operations.

It excludes holidays during which manufacturing plants remain operational.

For example, events such as Winter Break 1 to 6 are omitted.





Step 3: Create Calendar Rules

Calendars are assigned to workers using Calendar Rules.

Worker Population Assigned Calendar
US Corporate Employees US Non-Manufacturing Holiday Calendar
Manufacturing Plant Employees US Manufacturing Holiday Calendar

One or more calendar rules can be created using person and assignment attributes.

Once assigned, workers inherit the events defined in their respective calendar.















Step 4: Assign Calendars to Workers

To ensure that the correct workers are assigned to the appropriate calendars, Oracle Fusion uses the Evaluate Group Membership scheduled process.

This process evaluates the rules associated with each calendar and updates the membership of the underlying HCM Groups.

Because worker eligibility may change due to updates in calendar attributes, the process must run regularly.

It is recommended to schedule the process to run as frequently as worker data changes within the organization.

Scheduling the Evaluate Group Membership Process

Navigation:

Tools → Scheduled Processes

Steps:

  1. Click Schedule New Process
  2. Search for Evaluate Group Membership
  3. Schedule it to run periodically

Running a Targeted Refresh for Calendar Rules

If administrators need to refresh membership for a specific calendar rule:

  • Enter the specific rule name
  • Or search using:
%ANC_CALENDAR_RULES

This lists all calendar rules associated with Organization Calendar Events.





Important Note About Calendar HCM Groups

The HCM Groups used by Organization Calendar Events are maintained internally by the application.

Because of this:

  • These groups cannot be viewed or edited directly from the Define HCM Groups page
  • Membership is controlled automatically by the Evaluate Group Membership process

You can query the membership using SQL:

select 
per.person_number,
ppn.last_name,
ppn.first_name,
grp.group_name,
mem.effective_start_date,
mem.effective_end_date
from hwm_grp_members_f mem,
hwm_grps_vl grp,
per_all_people_f per,
per_person_names_f ppn
where grp.grp_id = mem.grp_id
and per.person_id = mem.member_id
and per.person_id = ppn.person_id
and ppn.name_type = 'GLOBAL'
and trunc(sysdate) between mem.effective_start_date and mem.effective_end_date
and trunc(sysdate) between ppn.effective_start_date and ppn.effective_end_date
and trunc(sysdate) between per.effective_start_date and per.effective_end_date

Testing the Solution

Corporate employees follow the full US public holiday calendar including winter break holidays.




Manufacturing employees follow the plant-specific holiday calendar without winter break holidays.





Business Benefits

  • Maintain Production Continuity
    Manufacturing plants can operate during certain holidays without impacting corporate scheduling.
  • Provide Accurate Workforce Scheduling
    The scheduling engine automatically respects the correct holiday calendar for each worker.
  • Reduce Administrative Effort
    Holiday schedules are managed centrally instead of being manually applied by managers.

Summary

The Organization Calendar Events feature in Oracle Fusion Cloud HCM 25D provides a centralized way to manage holidays and organizational events across different workforce populations.

In this case:

  • Corporate employees follow a US Non-Manufacturing Holiday Calendar
  • Manufacturing employees follow a US Manufacturing Holiday Calendar

Although the feature enables flexible calendar definitions, organizations must design implementations carefully due to the current limitation that calendars can only be defined using Geography or Organization hierarchies.

With proper configuration, the feature provides a scalable solution for managing holiday schedules across diverse operational environments.