Reference Data Set in Fusion HCM

Introduction

Reference Data Set in Oracle Fusion HCM is a critical concept that every functional consultant must understand while working on enterprise-level implementations. In large organizations operating across multiple countries or business units, maintaining centralized yet flexible configuration is essential—and this is exactly where reference data sets come into play.

In Oracle Fusion HCM (26A), reference data sets allow you to control the sharing of configuration data such as jobs, locations, grades, and positions across different business units. From my real implementation experience, improper use of reference data sets often leads to duplicate configurations, reporting inconsistencies, and security issues.

In this blog, we’ll go deep into how reference data sets work, how to configure them, and how they impact real-world implementations.

What is Reference Data Set in Oracle Fusion?

A Reference Data Set is a logical grouping that determines which business units can access specific setup data.

In simple terms:

• It controls data sharing across business units

• It ensures data segregation where needed

• It reduces duplicate configurations

Key Concept

There are two types of data access:

Example

• Job: “Software Engineer”

• If assigned to Common Set → Available to all BUs

• If assigned to India BU Set → Available only to India BU

Key Features of Reference Data Sets

1. Data Sharing Control

You can decide whether configuration is:

• Global (Common Set)

• Local (BU-specific)

2. Reduces Redundancy

Avoid creating duplicate setups like:

• Same job in multiple BUs

• Same location replicated multiple times

3. Improves Data Governance

Helps maintain:

• Standardization

• Consistency across enterprise

4. Supports Multi-Country Implementations

Very useful when:

• Policies differ by country

• Legal requirements vary

5. Integrated Across Modules

Reference Data Sets are used in:

• HCM (Jobs, Locations, Grades)

• SCM (Items, Categories)

• Financials (Payment Terms)

Real-World Business Use Cases

Use Case 1 – Global Organization with Shared Jobs

A multinational company wants:

• Same job structure across all countries

Solution:

• Assign Jobs to Common Set

Result:

• Centralized job management

• No duplication

Use Case 2 – Country-Specific Locations

Company operates in:

• India

• USA

• UK

Each country has different locations.

Solution:

• Create separate sets:

  • India Set

  • US Set

  • UK Set

Result:

• Locations visible only within respective country BU

Use Case 3 – Different Grades by Legal Entity

A company uses:

• Different grading structures per region

Solution:

• Assign grades to BU-specific sets

Result:

• Flexible compensation structures

Configuration Overview

Before using reference data sets, ensure:

Required Setups

• Enterprise Structure configured

• Business Units created

• Legal Entities defined

• Reference Data Sharing configured

Key Components

Step-by-Step Configuration in Oracle Fusion

Step 1 – Navigate to Manage Reference Data Sets

Navigation:

Navigator → Setup and Maintenance →
Search Task: Manage Reference Data Sets

Step 2 – Create a New Reference Data Set

Click Create

Enter:

Click Save

Step 3 – Assign Set to Business Unit

Navigation:

Navigator → Setup and Maintenance →
Task: Manage Business Unit Set Assignment

Step 4 – Map Set to BU

Example:

Click Save and Close

Step 5 – Assign Set in Setup Objects

Example: Creating Job

Navigation:

My Client Groups → Workforce Structures → Jobs

While creating job:

Testing the Setup

Scenario: Validate Job Visibility

Test Case

• Login as HR user for India BU

• Navigate to:
  My Client Groups → Jobs

Expected Result

• Should see:

  • Jobs assigned to INDIA_SET

  • Jobs assigned to COMMON set

• Should NOT see:

  • Jobs assigned to US_SET

Validation Checks

• Correct set assigned?

• Correct BU mapping?

• Data visible as expected?

Common Implementation Challenges

1. Wrong Set Assignment

Issue:

• Job not visible in BU

Cause:

• Assigned to wrong set

2. Overuse of Common Set

Issue:

• Too much data sharing

Impact:

• Loss of control

• Compliance issues

3. Data Duplication

Issue:

• Same job created in multiple sets

Solution:

• Use Common Set strategically

4. Reporting Issues

OTBI reports may show:

• Missing or extra data

Cause:

• Incorrect set mapping

Best Practices from Real Projects

1. Design Set Strategy Early

Before implementation:

• Identify global vs local data

2. Use Common Set Carefully

Use it only for:

• Truly global data

3. Naming Conventions

Use clear names like:

• INDIA_SET

• US_SET

• GLOBAL_SET

4. Avoid Frequent Changes

Changing sets after go-live:

• Impacts transactions

• Causes inconsistencies

5. Document Mapping

Maintain a mapping sheet:

Summary

Reference Data Set in Oracle Fusion HCM is one of the most powerful yet often misunderstood concepts. It directly impacts:

• Data visibility

• Configuration strategy

• Multi-country implementations

From my consulting experience, projects that properly design reference data sets early avoid major rework during later phases.

If you are working on HCM implementations, mastering this concept will significantly improve your design capability and troubleshooting skills.

For deeper understanding, refer to Oracle’s official documentation:
https://docs.oracle.com/en/cloud/saas/index.html

FAQs

1. What is the difference between Common Set and Business Unit Set?

Common Set is shared across all BUs, while BU Set is restricted to specific business units.

2. Can we change the set after creating a job?

Technically possible but not recommended after transactions are created, as it may impact data consistency.

3. Is Reference Data Set used only in HCM?

No, it is used across multiple modules like SCM and Financials.