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.

How to Configure Context-Sensitive Descriptive Flexfields (DFF) for Absence Types in Oracle Fusion HCM

Introduction

Organizations frequently need to capture different information depending on the absence type selected by an employee.

Absence Type	Additional Information Required
Paid Time Off	Paid Time Off Attribute
Sick Leave	Sick Leave Attribute

Instead of customizing the application, Oracle Fusion Absence Management provides this capability through Context-Sensitive Descriptive Flexfields (DFF). This configuration allows the system to automatically display relevant fields depending on the selected absence type.

Solution Overview

This solution uses the Absence Recording Descriptive Flexfield (DFF) available in Oracle Fusion Absence Management.

1. Access the Absence Recording DFF
2. Configure the Context
3. Create contexts and context sensitive segments
4. Deploy the flexfield

(1) Access the Absence Recording DFF

Navigate to:

Setup and Maintenance → Manage Descriptive Flexfields

Search for Absence Recording DFF and click the Edit icon.

Step 2 – Configure the Context

Parameter	Value
Default Type	Parameter
Default Value	Absence Type
Derivation Value	Absence Type
Display Type	Hidden

This ensures the context is automatically derived from the absence type.

Step 3 – Define Context and Context Sensitive Segments

Create Contexts for Each Absence Type

Next, click the Manage Contexts button to view existing contexts or create new ones.

On the Manage Contexts page, click the “+” (Add) icon to create a new context.

When creating a context:

• You can enter any value for the Display Name

• The Context Code must be the absence_type_id

The system uses this value to determine which set of fields should be displayed for the selected absence type.

Retrieve the Absence Type ID

To obtain the absence_type_id, run the following SQL query:

SELECT *
FROM ANC_ABSENCE_TYPES_F_TL
WHERE language = 'US'
AND name IN ('Paid Time Off','Sick Leave');

This query retrieves the IDs for the required absence types. Use the corresponding absence_type_id as the Context Code when creating the context.

Once the context is created, you can define context-specific segments that should appear when that absence type is selected.

Paid Time Off

• Paid Time Off Attribute

Let's define another context and related segments

Sick Leave

• Sick Leave Attribute

Step 4 – Deploy the Flexfield

Save the configuration and click Deploy Flexfield. Ensure deployment status shows successful compilation.

Testing the Configuration

Navigate to:

My Client Groups → Absence → Absences and Entitlements

Create a new absence request and verify the fields appear dynamically based on absence type.

Best Practices

• Use Global Segments only for fields applicable to all absence types
• Ensure context code matches absence_type_id
• Keep Context Segment hidden
• Always deploy flexfields after configuration

Conclusion

Using Context-Sensitive Descriptive Flexfields in Oracle Fusion Absence Management, organizations can dynamically capture absence-specific information without customization. This improves data accuracy, user experience, and system flexibility.