Oracle HCM HDL Error: "The Combination Is Not Valid" – Complete Troubleshooting Guide
Introduction
While loading data using Oracle HCM Data Loader (HDL), Payroll Data Loader, Spreadsheet Loader, or performing worker transactions, consultants frequently encounter the following error:
Error:
An error occurred. To review details of the error run the HCM Data Loader Error Analysis Report diagnostic test.
Message details:
The combination is not valid.
This error can be frustrating because Oracle doesn't always identify the exact segment or flexfield combination causing the issue.
In this article, we'll discuss the most common root causes, troubleshooting steps, and proven solutions that Oracle HCM consultants can use to resolve this error quickly.
Understanding the Error
The error generally indicates that Oracle Fusion is trying to validate a combination of values against a configured flexfield structure and the combination fails validation.
Common areas where this occurs include:
Worker Loads
Assignment Loads
Payroll Loads
Cost Allocation Loads
HDL Data Conversions
Element Entries
Payroll Costing
The system validates combinations against configured setups before allowing data creation.
Actual Error Message
An error occurred.
To review details of the error run the HCM Data Loader Error Analysis Report diagnostic test.
Message details:
The combination is not valid.
Root Cause #1 – People Group Flexfield Enabled
One of the most common causes of this error is People Group configuration.
Many organizations enable People Group segments but forget to populate valid values during HDL loads.
When Oracle validates the People Group combination, it fails and generates the error.
How to Verify
Navigate to:
Setup and Maintenance
→ Manage Key Flexfields
Search for: PPG as Key Flexfield Code
Name - People Group Flexfield.Example Scenario
Your implementation contains People Group Segments:
| Segment | Value |
|---|---|
| Region | US |
| Employee Type | Full Time |
| Cost Center | IT |
If HDL attempts to load:
Region = USA
Employee Type = Permanent
Cost Center = 100
and the combination doesn't exist, Oracle returns:
The combination is not valid
Solution
Verify:
✔ People Group enabled
✔ Segment values exist
✔ Combination exists
✔ HDL contains valid segment values
Root Cause #2 – Expense Account Flexfield Enabled
Another frequent cause is Expense Account validation.
Organizations often enable accounting flexfields such as:
Cost Center
Department
Natural Account
Company
Business Unit
If one segment value is invalid, Oracle rejects the entire combination.
Example
Valid Account:
01.100.5000.000
Invalid Account:
01.999.5000.000
If segment 999 doesn't exist, Oracle returns:
The combination is not valid
Root Cause #3 – Cost Allocation Flexfield Validation
This issue commonly appears during:
Payroll Costing Loads
Cost Allocation HDL Loads
Element Eligibility Costing
Department Costing
Oracle validates:
Cost Allocation Key Flexfield
before processing.
Root Cause #4 – Cross Validation Rules
Sometimes all segment values exist but the combination itself is restricted.
Example:
Allowed:
Company = 01
Cost Center = 100
Blocked:
Company = 01
Cost Center = 900
due to Cross Validation Rules.
Oracle therefore throws:
The combination is not valid
Root Cause #5 – Suspense Account Missing
Payroll costing loads often fail because:
Default Account missing
Suspense Account missing
Offset Account missing
Oracle validates account combinations during payroll costing generation.
Troubleshooting Checklist
Before raising an SR, verify the following:
People Group
✔ Is People Group enabled?
✔ Are all People Group segments populated?
✔ Are values valid?
✔ Does the combination exist?
Expense Account
✔ Is Expense Account enabled?
✔ Are all account segments valid?
✔ Are segment values active?
✔ Are values end-dated?
Cost Allocation
✔ Cost Allocation Flexfield configured?
✔ Cost Account valid?
✔ Offset Account valid?
✔ Suspense Account configured?
Cross Validation Rules
✔ Any restrictions defined?
✔ Combination allowed?
HDL Mapping
✔ Source values mapped correctly?
✔ No blank mandatory segments?
✔ Segment lengths valid?
Recommended Resolution Process
Resolution Process Image
Real-Life Example
A customer was loading employee assignments through HDL.
Error received:
The combination is not valid
Investigation revealed:
People Group Flexfield enabled
New People Group Segment added
HDL file not populating the new segment
After updating the HDL mapping and loading the correct segment value, the worker load completed successfully.
Best Practices
Before Data Conversion
✔ Review all enabled flexfields
✔ Document segment values
✔ Validate source data
Before HDL Load
✔ Verify People Group values
✔ Verify Expense Account values
✔ Validate Cost Center combinations
During Testing
✔ Load small sample data
✔ Review HDL Error Analysis Report
✔ Validate costing combinations
Conclusion
The Oracle HDL error:
The combination is not valid
usually points to a failed flexfield validation.
In most Oracle HCM implementations, the issue is caused by:
People Group Flexfield enabled but invalid segment values.
Expense Account combinations not configured.
Cost Allocation Key Flexfield issues.
Cross Validation Rule restrictions.
Missing Suspense or Default Accounts.
Always start troubleshooting by checking:
✔ People Group Configuration
✔ Expense Account Setup
✔ Cost Allocation Flexfield
✔ Cross Validation Rules
These checks resolve the majority of cases without requiring an Oracle Service Request.
Frequently Asked Questions (FAQ)
Q1. What does "The combination is not valid" mean in Oracle HDL?
It means Oracle failed to validate a flexfield combination such as People Group, Expense Account, or Cost Allocation Account.
Q2. Where should I check first?
Start with:
People Group Flexfield
Expense Account Flexfield
These are the most common causes.
Q3. Can Cost Allocation setup cause this error?
Yes. Invalid costing combinations frequently trigger this error.
Q4. What report should I run?
Run:
HCM Data Loader Error Analysis Report
to get detailed diagnostic information.
Q5. Can Cross Validation Rules cause this error?
Yes. Even valid segment values can fail if Cross Validation Rules restrict the combination.
Related Articles
Feedback Section
Did this article help resolve your issue?
✔ Yes, People Group was the problem
✔ Yes, Expense Account caused the issue
✔ Yes, Cost Allocation setup was incorrect
✔ Need help with another variation of this error
Share your scenario in the comments and help other Oracle HCM consultants learn from real project experiences.
No comments:
Post a Comment