Oracle Fusion HCM

Thursday, 19 January 2023

HDL Template to Disability of Worker

 HDL Template to Person Disability


Please find the below sample template :


File Name- PersonDisability.dat

METADATA|PersonDisability|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|LegislationCode|PersonId|PersonNumber|SelfDisclosedType|Category|QuotaFTE|Status

MERGE|PersonDisability|XXTEST|XXTEST_DIS21|2021/07/07|4712/12/31|US|100000609337422|XXTEST21|ORA_PER_YES_US|NA|1|A


 

Wednesday, 18 January 2023

HDL Template to Change Hire Date of Worker


✅ HDL Template to Change Hire Date of Worker in Oracle Fusion HCM (Worker.dat)

Changing an employee’s Hire Date (Start Date) is a common requirement in Oracle Fusion HCM, especially when correcting wrong employee joining dates loaded from legacy systems or during data migration.

In this blog, you will learn how to change Hire Date of a worker using HDL (HCM Data Loader) with Worker.dat file.


๐Ÿ”ฅ What is Hire Date in Oracle Fusion HCM?

In Oracle Fusion HCM, the hire date is stored at the Work Relationship level.
That’s why to change Hire Date using HDL, you must update the WorkRelationship component inside Worker.dat.


๐Ÿ“Œ HDL File Used

✅ Worker.dat


⚠️ Important Note Before Updating Hire Date

Before you change hire date, ensure:

  • Worker already exists in Fusion HCM

  • You know correct identifiers like PersonId or PersonNumber

  • Hire date change may impact:

    • Payroll

    • Absence

    • Seniority

    • Benefits eligibility

    • Assignment start dates

So always validate in lower environment first.


✅ HDL Template to Change Hire Date of Worker (Worker.dat)

Use below template exactly:

SET PURGE_FUTURE_CHANGES N


METADATA|WorkRelationship|SourceSystemOwner|SourceSystemId|

PersonId(SourceSystemId)|LegalEmployerName|NewStartDate

MERGE|WorkRelationship|XXTEST|XXTEST_HIREDATE1|100009|India Legal Entity|

2002/02/10



๐Ÿงพ Explanation of Fields (Worker.dat)

ColumnMeaning
SourceSystemOwnerYour source system name (ex: XXTEST)
SourceSystemIdUnique record identifier for this HDL row
PersonId(SourceSystemId)PersonId of the worker (can be PersonNumber too in other templates)
LegalEmployerNameMust match worker’s legal employer
NewStartDateThe corrected hire date you want to set

⭐ Why We Use SET PURGE_FUTURE_CHANGES N

This line controls whether future-dated changes should be purged.

✅ Recommended:

SET PURGE_FUTURE_CHANGES N

Because:

  • It keeps future-dated transactions safe

  • Prevents accidental loss of future assignment updates


๐Ÿงญ Step-by-Step: How to Load HDL to Change Hire Date

Step 1: Prepare Worker.dat file

  • Copy the template

  • Replace with your employee values

Step 2: Create ZIP

Zip the file as:

Worker.zip └── Worker.dat

Step 3: Upload in HCM Data Loader

Navigation:

My Client Groups → Data Exchange → HCM Data Loader

  1. Click Import and Load

  2. Upload the ZIP file

  3. Submit the process

Step 4: Validate Results

After load:

  • Check Import and Load Status

  • Review logs if errors occur


✅ How to Verify Hire Date is Updated

Go to:

Person Management → Search Worker → Employment → Work Relationship

Check:

  • Start Date / Hire Date updated correctly


❗ Common Errors and Fixes

1) Legal Employer Name Invalid

Error: LegalEmployerName not found
✅ Fix: Use exact legal employer name from Fusion setup.


2) PersonId Incorrect

Error: PersonId(SourceSystemId) not found
✅ Fix:

  • Use correct PersonId

  • Or use PersonNumber based mapping (if your environment supports)


3) Future Changes Conflict

Error: Cannot update because of future-dated changes
✅ Fix:

  • Review future-dated transactions

  • Keep SET PURGE_FUTURE_CHANGES N


๐Ÿ”— Internal Links 


HDL Template for Salary of Worker


How to Load Worker Salary in Oracle Fusion HCM Using HDL (Salary.dat)

Learn how to create or update worker salary in Oracle Fusion HCM using HDL Salary.dat. Step-by-step guide with sample template, required fields, salary basis, action codes, approval flag, and common error fixes.

Oracle Fusion HCM allows you to load or update worker salary using HCM Data Loader (HDL).
This is useful when you need to migrate salary data during:

  • New implementation (initial data load)

  • Bulk salary updates

  • Salary corrections

  • Salary changes during hiring

In this blog, you will learn:

✅ Salary HDL file name and structure
✅ Required attributes
✅ Salary basis and approval flag
✅ Sample Salary.dat template
✅ Common errors and troubleshooting

You can see step by step video to load Salary data using this Click Here


๐Ÿ“Œ HDL File Used

To load salary data, use:

✅ Salary.dat


✅ Prerequisites (Very Important)

Before loading salary using HDL, make sure:

1) Worker & Assignment already exist

Salary is always tied to an assignment.

So these must exist first:

  • Worker record

  • AssignmentNumber


2) Salary Basis must exist

SalaryBasisName should already be configured.

Example:

  • US1 Annual Salary

  • Monthly Salary

  • Hourly Rate

Navigation:
My Client Groups → Salary → Salary Basis


3) Worker must have valid payroll / employment info

Salary often fails if assignment is missing:

  • legislation code

  • grade

  • payroll details (in some setups)


✅ Salary.dat Template (Sample)

Use the below sample:

METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved

MERGE|Salary|ORACLE_ASG12|1991/01/01||10000|US1 Annual Salary|HIRE|Y



✅ Field Explanation (Salary HDL)

1) AssignmentNumber

This is the unique assignment number of the worker.

Example:

ORACLE_ASG12

2) DateFrom / DateTo

  • DateFrom = salary effective start date

  • DateTo = keep blank unless you want to end-date salary

Example:

1991/01/01

3) SalaryAmount

Salary amount to load.

Example:

10000

4) SalaryBasisName

This must match exactly with configured Salary Basis.

Example:

US1 Annual Salary

5) ActionCode

Defines why salary is being loaded.

Common values:

  • HIRE

  • SALARY_CHANGE

  • PROMOTION

  • TRANSFER

Example:

HIRE

6) SalaryApproved

Salary approval flag.

Values:

  • Y = approved

  • N = not approved

Example:

Y

✅ Step-by-Step: Load Salary Using HDL

Step 1: Create Salary.dat file

Create a .dat file and add metadata + merge line.


Step 2: Create .zip file

Create a zip file:

Example:

Salary.zip

Inside zip:

Salary.dat

Step 3: Upload in HDL

Navigate to:

My Client Groups → Data Exchange → HCM Data Loader

Steps:

  1. Import and Load Data

  2. Upload Salary.zip

  3. Submit


Step 4: Monitor HDL Status

Check:

  • Import Status

  • Load Status

  • Completed Successfully / Error


Step 5: Validate Salary in UI

Navigate to:

My Client Groups → Person Management → Search Worker → Salary

Confirm:

  • Salary Amount

  • Salary Basis

  • Effective date


⭐ Example: Load Salary for Multiple Workers

METADATA|Salary|AssignmentNumber|DateFrom|DateTo|SalaryAmount|SalaryBasisName|ActionCode|SalaryApproved MERGE|Salary|ORACLE_ASG12|1991/01/01||10000|US1 Annual Salary|HIRE|Y MERGE|Salary|ORACLE_ASG13|1991/01/01||12000|US1 Annual Salary|HIRE|Y MERGE|Salary|ORACLE_ASG14|1991/01/01||15000|US1 Annual Salary|HIRE|Y

๐Ÿ”ฅ Common HDL Errors & Fixes

❌ 1) Salary basis not found

Error:
SalaryBasisName is invalid

✅ Fix:

  • Verify Salary Basis exists

  • Match exact name (case-sensitive)


❌ 2) Assignment number not found

Error:
AssignmentNumber doesn’t exist

✅ Fix:

  • Confirm assignment is created successfully

  • Load worker/assignment first


❌ 3) Salary overlaps existing salary

Error:
Overlapping salary records

✅ Fix:

  • End-date previous salary using DateTo

  • Or use correct DateFrom


❌ 4) Salary not approved

Error:
Salary not visible in UI

✅ Fix:

  • Set SalaryApproved = Y

  • Ensure approvals not required in workflow


๐Ÿ”— Internal Links 



⭐ FAQs 

Q1. Which file is used to load salary using HDL?

Salary is loaded using Salary.dat in Oracle Fusion HCM.

Q2. What is required before loading salary using HDL?

Worker and Assignment must exist, and Salary Basis must be configured.

Q3. Can we update salary using MERGE?

Yes, MERGE can create or update salary records depending on the effective date.

Q4. What is SalaryApproved in Salary.dat?

SalaryApproved is a flag that indicates whether the salary record is approved (Y) or not approved (N).

Q5. What is the most common reason salary HDL fails?

The most common reasons are invalid SalaryBasisName and incorrect AssignmentNumber.

HDL Template for Worker Extra Information of Worker (EIT)

HDL Template for Worker Extra Information of Worker (EIT).

For this use Worker.dat

Please find the below sample template :

Sample file for Worker EIT.

METADATA|WorkerExtraInfo|PersonNumber|EffectiveStartDate|EffectiveEndDate|InformationType|PeiInformationCategory|CategoryCode|FLEX:PER_PERSON_EIT_EFF|EFF_CATEGORY_CODE|_CASTE(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_COMMUNITY(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_EX_SERVICE_PERSON(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_HEIGHT(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_PAN_APPLIED(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_PAN_REFERENCE_NUMBER(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_RESIDENTIAL_STATUS(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_RESIDENTIAL_STATUS_Display(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)|_WEIGHT(PER_PERSON_EIT_EFF=HRX_IN_MISCELLANEOUS)


MERGE|WorkerExtraInfo|PS5|2010/11/02||HRX_IN_MISCELLANEOUS|HRX_IN_MISCELLANEOUS|PER_EIT|HRX_IN_MISCELLANEOUS|PER_EIT|Test123|Backward|||||||

Wednesday, 28 December 2022

HDL Template for Global Temporary Transfer of Worker

For this use Worker.dat


Please find the below sample template :

METADATA|WorkRelationship|PersonNumber|LegalEmployerName|DateStart|ActualTerminationDate|PrimaryFlag|WorkerNumber|WorkerType|RehireRecommendationFlag|OnMilitaryServiceFlag|ActionCode|ReasonCode|DateOfDeath

MERGE|WorkRelationship|XXTEST9|US1 Legal Entity|2018/01/01||Y|XXTEST9|E|Y|N|GLB_TEMP_ASG||

MERGE|WorkRelationship|XXTEST9|UK Legal Entity|2019/01/01||N|XXTEST9|E|Y|N|GLB_TEMP_ASG||



METADATA|WorkTerms|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|PrimaryWorkTermsFlag|SystemPersonType|ReasonCode

MERGE|WorkTerms|GLB_TEMP_ASG|XXTEST9|US1 Legal Entity|2018/01/01|E|XXTEST_WRKTERM9|2019/01/01|4712/12/31|Y|1|ET|Employee|SUSPEND_PROCESS|US1 Business Unit|Y|EMP|

MERGE|WorkTerms|GLB_TEMP_ASG|XXTEST9|UK Legal Entity|2019/01/01|E|XXTEST_WRKTERM9-2|2019/01/01|4712/12/31|Y|1|ET|Employee|ACTIVE_PROCESS|UK Business Unit|Y|EMP|


METADATA|Assignment|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|WorkTermsNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|GradeCode|JobCode|LocationCode|DepartmentName|ManagerFlag|LabourUnionMemberFlag|ReasonCode

MERGE|Assignment|GLB_TEMP_ASG|XXTEST9|US1 Legal Entity|2018/01/01|E|XXTEST_ASSIGN9|XXTEST_WRKTERM9|2019/01/01|4712/12/31|Y|1|E|Employee|SUSPEND_PROCESS|US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC12|XXTEST Department1|Y|N|

MERGE|Assignment|GLB_TEMP_ASG|XXTEST9|UK Legal Entity|2019/01/01|E|XXTEST_ASSIGN9-2|XXTEST_WRKTERM9-2|2019/01/01|4712/12/31|Y|1|E|Employee|ACTIVE_PROCESS|UK Business Unit|XXTEST_GRADE1|ADM|XXTEST_LOC12|XXTEST Department1|Y|N|

 

Tuesday, 27 December 2022

SQL Query to Fetch Global Transfer records in Fusion HCM

SQL Query to Fetch Global Transfer records in Fusion HCM 



select

papf.person_number, ppnf.full_name,

to_char(ppos.date_start,'mm/dd/yyyy') Hire_date

,(select hou.name from hr_organization_units hou where organization_id = ppos.LEGAL_ENTITY_ID)  Current_LE

from per_All_assignments_m paam

,per_all_people_F papf

,per_person_names_f ppnf

,PER_PERIODS_OF_SERVICE ppos

where paam.person_id = papf.person_id

and papf.person_id = ppnf.person_id

and ppos.period_of_service_id = paam.period_of_service_id

and ppnf.name_type = 'GLOBAL'

and sysdate between papf.effective_start_date and papf.effective_end_date

and sysdate between ppnf.effective_start_date and ppnf.effective_end_date

and  sysdate  between paam.effective_start_date and paam.effective_end_date

and paam.person_id = papf.person_id

and paam.assignment_status_type = 'ACTIVE' 

and paam.assignment_type = 'E'

and paam.action_code = 'GLB_TRANSFER'


Note :- Do let me know in case of any issue in query.


Monday, 26 December 2022

SQL Query to Fetch Inactive Employees in Fusion HCM

SQL Query to Fetch Inactive Employees in Fusion HCM 



select 

paam.*

from

 per_all_assignments_m paam ,

per_all_people_f  papf 

where 1=1

and papf.person_id = paam.person_id

and paam.ASSIGNMENT_STATUS_TYPE <> 'INACTIVE'

and paam.effective_latest_change = 'Y'

and paam.primary_flag = 'Y'

and paam.assignment_type= 'E'

and trunc(sysdate) between papf.effective_start_date and papf.effective_end_date

and exists ( select '1' from per_all_assignments_m paam1 where paam1 .assignment_id = paam.assignment_id

             and trunc(sysdate) between paam1 .effective_start_date and paam1 .effective_end_date

and t1.ASSIGNMENT_STATUS_TYPE <> 'INACTIVE'

)

Monday, 28 February 2022

How to Change Non-Primary Work Relationship to Primary Using Worker.dat (Oracle Fusion HDL)

  


How to Change Non-Primary Work Relationship to Primary Using Worker.dat (Oracle Fusion HDL)

Introduction

In Oracle Fusion HCM, an employee can have only one Primary Work Relationship at any given time.

During data corrections or integrations, you may encounter a requirement to change an existing non-primary work relationship to primary.

Oracle Fusion allows this update using HCM Data Loader (HDL) by passing specific attributes in the Worker.dat file.

This blog explains:

  • When this scenario occurs

  • Required HDL attributes

  • Sample Worker.dat template

  • What happens after upload

Saturday, 4 September 2021

HDL Template for Job Requisition

HDL Template for Job Requisition 


For this use JobRequisition.dat file.

You can see step by step video to load Job Requisition data using this Link


Please find the below sample template :

METADATA|JobRequisition|RequisitionNumber|RecruitingType|JobCode|JobFamilyCode|JobFunction|NumberOfOpenings|UnlimitedOpeningsFlag|RequisitionTitle|HiringManagerId|RecruiterId|PrimaryLocationId|PrimaryWorkLocationId|OrganizationId|DepartmentName|LegalEmployerName|WorkerType|RegularOrTemporary|FullTimeOrPartTime|EducationLevel|CurrentPhaseCode|CurrentStateCode|ExternalApplyFlowCode|PositionCode|BaseLanguageCode|BusinessUnitShortCode|CandidateSelectionProcessCode

MERGE|JobRequisition|XXTEST100|ORA_EXECUTIVES|XXTEST_PM|HUMAN RESOURCES|GSE_TEACH|2|N|XXTEST100|100000610420334|100000610420436|300000186934005|300000221843104|300000047826629|XXTEST Department1|US1 Legal Entity|E|Regular|FULL_TIME|13|REQUISITION_OPEN|REQUISITION_POSTED|ORC_FACULTY|XXTEST_POS1|US|US1 Business Unit|ORC_FACULTY


METADATA|PostingDetails|StartDate|ExternalOrInternal|RequisitionNumber

MERGE|PostingDetails|2021/08/23 00:00:00|ORA_INTERNAL|XXTEST100

MERGE|PostingDetails|2021/08/23 00:00:00|ORA_EXTERNAL|XXTEST100


Friday, 20 August 2021

Oracle Fusion HCM HDL Candidate.dat File – Load Candidate, Address, Phone, Name & Profile (Sample Template)

 

๐Ÿงพ Oracle Fusion HCM – Load Candidate Data using HDL (Candidate.dat)

If you want to load candidate details into Oracle Fusion Recruiting, you can use HCM Data Loader (HDL) with the file Candidate.dat.

This blog covers:

✅ Candidate basic data
✅ Candidate address
✅ Candidate phone
✅ Candidate name
✅ Candidate profile (Degree / Certifications etc.)
✅ Sample Candidate.dat file format


๐Ÿ“Œ Prerequisites

Before loading Candidate HDL:

  • You must have access to HCM Data Loader

  • CandidateNumber must be unique

  • Use valid codes for:

    • Country (US, IN, etc.)

    • LegislationCode

    • AddressType

    • PhoneType


๐ŸŽฅ Step-by-Step Video Reference

You can see step by step video to load Candidate data using this Link:
๐Ÿ‘‰  Link


๐Ÿ“‚ Candidate.dat File – Full Sample Template

1️⃣ Candidate (Basic Candidate Record)

๐Ÿ“Œ HDL Metadata

METADATA|Candidate|CandidateNumber|CandPrefLanguageCode|StartDate|ConfirmedFlag|CountryOfBirth|DateOfBirth|RegionOfBirth|Source|SourceMedium|TownOfBirth|VisibleToCandidateFlag

✅ Sample Data

MERGE|Candidate|CT123|US|2019/03/20|Y||1980/08/05||direct Source|||Y


2️⃣ CandidateAddress

๐Ÿ“Œ HDL Metadata

METADATA|CandidateAddress|CandidateNumber|EffectiveStartDate|AddressLine1|AddressType|AddressLine2|Country|PostalCode|Region2|Region1|TownOrCity|EffectiveEndDate

✅ Sample Data

MERGE|CandidateAddress|CT123|2019/03/20|1257 Test1|HOME|Test|US|12576|NC|Wayne|Pikeville|

3️⃣ CandidatePhone

๐Ÿ“Œ HDL Metadata

METADATA|CandidatePhone|CandidateNumber|DateFrom|PhoneType|PhoneNumber|CountryCodeNumber|AreaCode|DateTo|Extension|LegislationCode|SpeedDialNumber|Validity|GUID

✅ Sample Data

MERGE|CandidatePhone|CT123|2019/03/20|H1|9605804|1|262|4712/12/31||US|||


4️⃣ CandidateName

๐Ÿ“Œ HDL Metadata

METADATA|CandidateName|EffectiveStartDate|EffectiveEndDate|CandidateNumber|NameType|LegislationCode|FirstName|LastName

✅ Sample Data
MERGE|CandidateName|2019/03/20||CT123|GLOBAL|US|Amar|Test

5️⃣ CandidateProfile (Degree / Profile Items)

CandidateProfile is used for things like:

  • Degree

  • Certifications

  • Skills

  • Previous employment

  • Education details

๐Ÿ“Œ HDL Metadata

METADATA|CandidateProfile|CandidateNumber|ContentType|ContentItem|SectionContext|DateFrom|ItemDate7|ItemNumber9|ItemText2401|CountryGeographyCode|CountryCountryCode|ProfileItemId


✅ Sample Data

MERGE|CandidateProfile|CT123|DEGREE|BA - Bachelor of Arts|PERSON_DEGREE|2019/03/20|2019/03/20|||US|US|122

✅ Best Practices (Important)

✔ Always Follow this Order in Candidate.dat

Recommended sequence:

  1. Candidate

  2. CandidateName

  3. CandidateAddress

  4. CandidatePhone

  5. CandidateProfile


✔ Date Format

Use:

  • YYYY/MM/DD
    Example:

  • 2019/03/20


✔ Effective End Date

Use:

  • 4712/12/31


❌ Common Errors & Fixes

1) Candidate already exists

Error: Duplicate candidate number
✅ Fix: Use unique CandidateNumber


2) Invalid country / legislation code

Error: Invalid CountryCode or LegislationCode
✅ Fix: Use valid values like:

  • Country: US, IN

  • LegislationCode: US, IN


3) AddressType invalid

Error: AddressType HOME not valid
✅ Fix: Use correct address type based on setup:

  • HOME

  • MAILING

  • WORK


4) ProfileItemId issue

Error: Profile item not created
✅ Fix: Ensure ProfileItemId exists OR remove ProfileItemId for new inserts.


๐Ÿ”— Internal Links 

Add these links at the bottom or inside the blog:


⭐ FAQ 

Q1. Which file is used to load candidate data in HDL?

Candidate.dat is used to load candidate records in Oracle Fusion Recruiting.

Q2. Can we load Candidate Address using HDL?

Yes, using CandidateAddress in Candidate.dat.

Q3. How to load candidate education or degree in Oracle HDL?

Use CandidateProfile with ContentType like DEGREE,Education etc.

Q4. What is the best Effective End Date in HDL?

Most implementations use 4712/12/31.

Monday, 2 August 2021

HDL Template for Content Item

 For this use ContentItem.dat file.

You can see step by step video to load Content Item data for talent profile using this Link


Find Content Item Value set Name using below Query - 

SELECT 

a.content_value_set_id as ContentItemValueSetId, 

a.content_value_set_code, 

b.value_set_name as ContentItemValueSetName, 

value_set_description

FROM FUSION.hrt_content_tp_valuesets_b a, FUSION.hrt_content_tp_valuesets_tl b

WHERE a.content_value_set_id = b.content_value_set_id

and b.language = 'US' ;


Please find the below sample template :

METADATA|ContentItem|SourceSystemOwner|SourceSystemId|ContextName|ContentItemCode|Name|ItemDescription|DateFrom|DateTo|ContentItemValueSetName

MERGE|ContentItem|XXTEST|XXTEST_BTECH|DEGREE||BTECH|BTECH|1951/01/01||Degrees


Monday, 26 July 2021

HDL Template for Talent Profile in Oracle Fusion HCM (TalentProfile.dat + Examples + Common Errors)

HDL Template for Talent Profile in Oracle Fusion HCM

Load Talent Profile Data Using HCM Loader (HDL)

TalentProfile.dat Step-by-Step Guide + Examples

Oracle Fusion HCM provides the Talent Profile feature to manage employee skills, languages, certifications, competencies, and other professional attributes. To load or migrate talent profile data in bulk, Oracle supports HCM Data Loader (HDL) using the TalentProfile.dat file.

In this blog, we will walk through:

  • Talent Profile HDL overview

  • Required HDL objects

  • Sample HDL template

  • Common mistakes and best practices

๐Ÿ“น You can also watch the step-by-step video to load Talent Profile data using HDL from the provided link.


๐Ÿ“Œ What Is Talent Profile in Oracle Fusion HCM?

Talent Profile allows organizations to capture and manage:

  • Skills

  • Languages

  • Certifications

  • Education

  • Licenses

  • Competencies

This data is widely used in Talent Management, Recruiting, Learning, and Succession Planning modules.


๐Ÿ“‚ HDL File Used for Talent Profile

To load Talent Profile data, use the following HDL file:

TalentProfile.dat

This file primarily uses two business objects:

  • TalentProfile

  • ProfileItem


๐Ÿ”น TalentProfile HDL Object

The TalentProfile object defines the main profile linked to a person.

๐Ÿ”ธ Sample Metadata & MERGE

METADATA|TalentProfile|SourceSystemOwner|SourceSystemId|Description|
Summary|ProfileTypeCode|ProfileCode|ProfileStatusCode|ProfileUsageCode
|PersonId MERGE|TalentProfile|XXTEST|XXTEST_TALENT2|||PERSON|PERSON_TALENT|A|P
|100000609812368

๐Ÿ”‘ Key Fields Explained

  • ProfileTypeCode → PERSON

  • ProfileCode → PERSON_TALENT

  • ProfileStatusCode → A (Active)

  • ProfileUsageCode → P (Person)

  • PersonId → Person ID from Fusion


๐Ÿ”น ProfileItem HDL Object

The ProfileItem object stores the actual talent details such as languages, skills, certifications, etc.

๐Ÿ”ธ Sample Metadata & MERGE (Language Example)

METADATA|ProfileItem|SourceSystemOwner|SourceSystemId|
ProfileId(SourceSystemId)|ContentType|ContentItem|SectionName|
CountryCountryCode|DateFrom|DateTo|RatingModelCode1|RatingModelCode2
|RatingModelCode3|RatingLevelCode1|RatingLevelCode2|RatingLevelCode3 MERGE|ProfileItem|XXTEST|XXTEST_TALENTPROF2|XXTEST_TALENT2|LANGUAGE
|Hindi|PERSON_LANGUAGE||2021/07/26||LANGUAGE|LANGUAGE|LANGUAGE|
HIGH|HIGH|HIGH

๐Ÿ”‘ Key Fields Explained

  • ProfileId(SourceSystemId) → SourceSystemId from TalentProfile

  • ContentType → LANGUAGE

  • ContentItem → Hindi

  • SectionName → PERSON_LANGUAGE

  • RatingModelCode → LANGUAGE

  • RatingLevelCode → HIGH


๐Ÿงฉ Supported Content Types in ProfileItem

Some commonly used ContentType values:

  • LANGUAGE

  • SKILL

  • CERTIFICATION

  • EDUCATION

  • LICENSE

Each content type may have different required attributes depending on configuration.


⚠ Common Errors & Troubleshooting

Talent Profile Load Common Issues



✅ Best Practices

✔ Load TalentProfile first, then ProfileItem
✔ Use consistent SourceSystemOwner
✔ Validate lookups for ContentType and RatingModel
✔ Test loads in lower environments
✔ Use MERGE instead of CREATE for updates


❓ Frequently Asked Questions (FAQ)

Q1. Which HDL file is used for Talent Profile?

Use TalentProfile.dat to load Talent Profile and Profile Items.

Q2. Can we load multiple skills or languages?

Yes. Use multiple ProfileItem records linked to the same TalentProfile.

Q3. Can Talent Profile be updated using HDL?

Yes. Use MERGE with the same SourceSystemId.

Q4. Is PersonId mandatory?

Yes. Talent Profile must be linked to a valid person.


๐Ÿ”— Related Articles (Internal Linking)


๐Ÿ“ˆ Conclusion/ Highlights 

HDL provides a reliable and scalable way to load Talent Profile data in Oracle Fusion HCM. By correctly using TalentProfile and ProfileItem objects, you can efficiently migrate or maintain talent information such as skills and languages.

TalentProfile.dat HDL template Oracle Fusion HCM

If you found this helpful, bookmark this page and explore other HDL templates available on this blog.




Sunday, 11 July 2021

HDL Template for Legislative Data Group

  For this use LegislativeDataGroup.dat file.

You can see step by step video to load Legislative Data Group using this Link

Please find the below sample template :


METADATA|LegislativeDataGroup|Name|DefaultCurrencyCode|LegislationCode|StructureInstanceName|SourceSystemOwner|SourceSystemId

MERGE|LegislativeDataGroup|US_LDG|USD|US|US Cost Flex Instance|XXTEST|XXTEST_LDG01


Featured post

Oracle Fusion HCM: US Tax Withholding Information Using HCM Data Loader (HDL)

  Overview of US Tax Withholding Information in Oracle Fusion HCM In Oracle Fusion HCM, Tax Withholding calculation cards store informatio...