Oracle Fusion HCM Value Sets Explained Clearly

What is a Value Set in Oracle Fusion HCM?

A value set is a fundamental configuration object in Oracle Fusion HCM that defines which values are permitted for a field and how users can select those values through a list of values (LOV). Value sets play a critical role in maintaining data quality by enforcing consistency across your system.

In practice, value sets prevent data entry errors by standardizing entries. For example, instead of allowing 10 different spellings of the same region, a well-designed value set ensures everyone selects from the same controlled list.

Where Value Sets Are Used

Value sets are integrated throughout Oracle Fusion HCM, including:

• Flexfields (Descriptive, Extensible, and Key Flexfields)
• Fast Formulas (for consistent inputs and outputs)
• HCM Extracts (for reporting and data consistency)

---

Why Value Sets Matter Beyond Dropdown Lists

Good value set design benefits more than just user experience:

Data Integrity

Only validated values can be saved to the system, preventing invalid or malformed entries.

Consistent Reporting & Analytics

Standardized values reduce data cleansing overhead and improve report accuracy. When data is consistent, analytical insights become more reliable.

Process Consistency

Downstream workflows, approval chains, and eligibility rules behave predictably because they work with known, controlled values.

Controlled Access Through Value Security

You can restrict which users see or select specific values based on their roles and responsibilities.

---

Where to Manage Value Sets

Value sets are administered centrally in the Setup and Maintenance work area using the Manage Value Sets task. This is your single point of control for:

• Creating new value sets
• Editing and maintaining existing value sets
• Configuring validation rules
• Managing the actual list of allowed values

---

---

Value Set Types in Oracle Fusion HCM

Oracle Fusion HCM supports five distinct value set types. Choosing the right type early in your design prevents rework and improves long-term maintainability.

1. Independent Value Set

An independent value set is a standalone list of allowed values with no dependencies on other fields. Use this type when the list is static and self-contained.

Examples:

• Employment Type (Full-Time, Part-Time, Contingent)
• Work Location Category (On-site, Remote, Hybrid)
• Expense Eligibility Flag (Yes, No) Configuration approach: Values are maintained directly in the Manage Values page.

---

2. Dependent Value Set

A dependent value set narrows the available options based on a selection made in a related independent value set (called the parent). This creates hierarchical relationships between fields.

Examples:

• Country (parent) → State/Province (child)
• Business Unit (parent) → Department Group (child) Why use dependent value sets:
• Prevents users from selecting irrelevant combinations
• Improves data quality by enforcing logical relationships
• Reduces selection errors and training burden

---

3. Table Value Set (Table-Validated)

A table value set reads allowed values directly from an application table or view. The list of values automatically reflects data maintained elsewhere in the system, ensuring a single source of truth.

When configuring a table value set, you specify:

• The source table or view
• The column containing the values
• Optional WHERE clause to filter which rows are included
• Optional ORDER BY to control sort order Use table value sets when:
• The list is large or frequently changing
• Values are already maintained in application tables
• You want to avoid duplicate data maintenance
• You need values to stay in sync with other system data

---

4. Format-Only Value Set

A format-only value set enforces data type and length validation without maintaining a predefined list of allowed values. This type enables structured input while allowing flexibility in what can be entered.

Examples:

• Internal reference IDs that must be numeric and exactly 8 digits
• Project codes that follow a specific naming pattern
• Employee badges that must follow a defined format Use format-only when:
• You need to enforce input structure
• You do NOT require a predefined list of options
• Users need flexibility to enter values, but within constraints

---

5. Subset Value Set

A subset value set reuses an existing independent value set but limits it to a defined subset of values. This allows enterprise-wide consistency while enabling context-specific filtering.

Examples:

• A global list of job families where workers in a specific category should only see relevant options
• A list of cost centers where each department sees only their assigned codes Benefits:
• Maintains consistency with the enterprise list
• Provides context-specific visibility without creating duplicate lists
• Improves governance by keeping related data in one place

---

How to Create a Value Set (Practical Steps)

Navigation

Setup and Maintenance → Manage Value Sets

Configuration Steps

1. Create a new value set and define:
   • Code/Name (follow organizational naming conventions)
   • Module (HCM, Payroll, etc.)
   • Validation Type (Independent, Dependent, Table, Subset, Format-only)
   • Data Type (must match the field’s data type)
2. Maintain values based on type:
   • Independent, Dependent, Subset: Use Manage Values to add, edit, and delete entries
   • Table Value Sets: Configure the table, column, and optional filtering/sorting logic
3. Configure additional options as needed:
   • Value set security (if required)
   • Sequencing rules
   • Default values

Video Tutorial

[https://www.youtube.com/watch?v=7RVR5lg6zf8]

Value Set Security: Controlling User Access

Value set security allows you to restrict which users can see or select specific values within a value set. This is implemented through Oracle Fusion’s data security framework tied to roles and responsibilities.

When Value Set Security is Important

• Sensitive locations that should not be visible to all employees
• Internal organization codes that should be restricted by department
• Restricted programs or benefits that only certain groups can access
• Regional data where users should only see information for their region

Security Configuration

• Can be enabled for Independent, Dependent, Subset, and Table value sets
• For table value sets, security requires values to be sourced from a single table or view
• Define data security policies that grant specific duty roles access to defined value sets or subsets

---

Decision Guide: Choosing the Right Value Set Type

Use this logic to select the appropriate type upfront and avoid rework:

Situation	Best Choice	Why
Small, stable list (Employment Type)	Independent	Simple to maintain, no dependencies
Values depend on another field (Country → State)	Dependent	Enforces logical hierarchy
Large list or already in tables (GL Accounts)	Table	Single source of truth, auto-updated
Input must follow a pattern	Format-Only	Validates structure without a list
Reuse global list with context-specific values	Subset	Consistency + local flexibility

---

Best Practices for Implementation and Long-Term Maintenance

1. Standardize Naming and Ownership

Create a consistent naming convention across your organization:

HCM_DFF_<ObjectName>_<AttributeName>_VS

Example: HCM_DFF_Person_EmploymentType_VS

Also define:

• Business Owner (HR Operations, Payroll, Total Rewards)
• Technical Owner (Configuration team responsible for maintenance)

2. Design for Reuse (Avoid “Mega Lists”)

Reusing value sets improves system-wide consistency. However, avoid combining unrelated concepts into one oversized list. Instead:

• Keep lists focused on a single business concept
• Use subset value sets to provide context-specific views
• Create separate lists for different use cases

3. Use Table Value Sets When Data Exists

If the values you need are already maintained elsewhere in the application:

• Use table value sets
• Eliminates duplicate data entry and maintenance
• Keeps LOVs synchronized with authoritative sources
• Reduces the risk of divergence over time

4. Plan for Value Set Security Early

If different user groups require different visibility:

• Design security requirements before building
• Avoid retrofitting security later (complex and error-prone)
• Prevent downstream workflow issues by getting visibility right upfront

---

Common Pitfalls to Avoid

1. Using Format-Only When You Need Controlled Values

Mistake: Using format-only value sets for fields that require standardized categories.

Problem: Reporting and analytics become difficult because data isn’t standardized.

Solution: Use Independent, Dependent, or Table validation instead when consistent values are required.

---

2. Overusing Dependent Value Sets Without a Strong Parent

Mistake: Creating dependent value sets on parents that are unclear or frequently change.

Problem: Users select the wrong parent, and the child values don’t display correctly.

Solution: Only use dependent sets when the parent is stable and well-understood (like Country as a parent for State/Province).

---

3. Not Planning for Security Constraints on Table Value Sets

Mistake: Designing complex table value sets that draw from multiple tables, then discovering that value set security doesn’t work with multi-table sources.

Problem: You must redesign later, which is costly and disruptive.

Solution: Validate that table value set security can be implemented before finalizing design for sensitive data.

---

Frequently Asked Questions (FAQ)

Are value sets only for flexfields?

No. While value sets are most commonly associated with Descriptive Flexfields (DFF), Extensible Flexfields (EFF), and Key Flexfields (KFF), they’re also used in:

• Fast Formulas
• HCM Extracts
• Purge rules
• Various configuration parameters

Where do I maintain the actual list of values?

The maintenance location depends on the value set type:

• Independent, Dependent, Subset: Use the Manage Values page in Setup and Maintenance
• Table Value Sets: Values are sourced from the configured table/view (no manual entry needed)

Can I restrict which users see which values?

Yes. Enable Value Set Security and define data security policies tied to duty roles. This controls which users can see or select specific values.

Can I reorder values in a value set?

Yes. Both the Manage Values page and table value set ORDER BY clauses allow you to control the sequence in which values appear in the LOV.

What happens if I delete a value that’s already in use?

When you deactivate or delete a value set entry, existing records retain the value, but users cannot select it for new entries. Best practice is to inactivate (rather than delete) values to preserve historical data integrity.

---

Key Terms Explained

Value Set: A configuration object that defines and validates permitted values for a field.

LOV (List of Values): The selectable dropdown list presented to users, populated based on the value set configuration.

Flexfield: An extensible framework (DFF, EFF, KFF) that uses value sets for validation and LOV generation.

Value Set Security: Role-based restriction controlling which values are visible to which users.

Dependent Value Set: A value set whose available options change based on the selection of a parent value set.

---

Summary

Value sets are one of the most powerful and essential configuration tools in Oracle Fusion HCM. Investing time early to design them correctly improves data quality, reporting accuracy, and user experience across your entire implementation.

The five value set types—Independent, Dependent, Table, Format-Only, and Subset—each serve specific purposes. Understanding when to use each one ensures your configuration is maintainable, scalable, and aligned with business requirements.

---

Resources

• Oracle Fusion HCM Documentation
• Manage Value Sets Task
• Fast Formula Contexts Guide
• SQL Query for Absence Plan Configuration

---

This article is based on practical Oracle Fusion HCM implementation experience. Value set design is fundamental to building robust, maintainable configurations.

Ready to master Value Sets? Start with the decision guide above, then explore configuration in your Setup and Maintenance work area.