One thing I've learned during Oracle HCM data conversions is that sometimes the simplest-looking loads end up teaching you the most.
Recently, I performed my very first department load using HDL. I expected it to be straightforward: create the department, provide the required attributes, include the Set Code, and load the file. BUT, this did not go the way I was planning it to be.
Attempt #1: The Missing Object
My HDL file contained the department details, including information such as:
Department Name
Department Number
Set Code
Effective Start Date
Everything looked correct, so I submitted the load.
The process failed.
After reviewing the error messages, I discovered that creating a department requires more than just the Organization business object. Oracle also expected an associated **OrgUnitClassification **record.
At that point, I realized that although I was creating the organization itself, Oracle still needed to know how that organization should be classified.
Attempt #2: Adding OrgUnitClassification
To address the issue, I updated the HDL file and added an OrgUnitClassification section in the same file.
My HDL now contained both:
METADATA|Organization|...
MERGE|Organization|...
METADATA|OrgUnitClassification|...
MERGE|OrgUnitClassification|...
With both business objects present, I was confident the load would succeed.
Unfortunately, it failed again.
The Real Problem
This second failure took a little more investigation.However,I eventually discovered that the classification information defined in the Organization section did not match the values being supplied in the OrgUnitClassification section.
Although both records existed, Oracle validates that they are aligned.
For example, if the Organization record references a department classification, the OrgUnitClassification record must contain the corresponding classification values.
The mismatch between the two sections caused the load to fail.
This was an important lesson because the issue was not missing data anymore. The issue was that the related business objects were not consistent with one another.
What Finally Worked
After correcting the classification values and ensuring they matched across both sections of the HDL file, I reran the load.
This time it completed successfully.
The departments were created correctly, complete with their assigned Set Code and Department classification.
Key Lessons Learned
My first successful department load required three things:
1. Create the Organization
The Organization record contains the core department information, including attributes such as:
Name
Department Number
Set Code
Effective Dates
2. Include OrgUnitClassification
A department is not fully defined until Oracle knows how it should be classified.
Adding the OrgUnitClassification record was required for the load to proceed.
3. Ensure Values Match
The Organization and OrgUnitClassification records must be consistent.
If the classification code or classification name referenced by the Organization does not match what is provided in OrgUnitClassification, Oracle will reject the load.
Final Thoughts
What I initially thought would be a simple department load turned into a valuable Oracle HCM learning experience.
My first load failed because I was missing the OrgUnitClassification business object. My second load failed because the classification values did not match between the Organization and OrgUnitClassification records. Once both objects were present and aligned correctly, the load completed successfully.
The biggest takeaway for me was that HDL loads are not just about loading data. They're about understanding the relationships between business objects and ensuring those relationships are configured correctly.
Sometimes the data itself is perfectly fine. The challenge is knowing which supporting objects Oracle expects and how they fit together.
And for me, that's exactly what made this first department load such a useful learning experience.
Top comments (0)