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)

• 🔗 Load Worker Data Using HCM Loader

• 🔗 Common Errors During Worker HDL Load

• 🔗 HDL Template for Dependent Enrollment

• 🔗 Change Primary Work Relationship Using HDL

---

📈 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.

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

HDL Template for Documents Of Record

 For this use DocumentsOfRecord.dat file.

You can see step by step video to load Documents Of Record using this Link

Please find the below sample template :

METADATA|DocumentsOfRecord|SourceSystemOwner|SourceSystemId|DocumentsOfRecordId|PersonNumber|DocumentTypeId|DocumentType|Country|DocumentCode|DocumentName|DocumentNumber|DateFrom|DateTo|IssuingAuthority|IssuedDate|IssuingCountry|IssuingLocation|Comments|Publish|PublishDate|Status|VerifiedBy|VerifiedDate

MERGE|DocumentsOfRecord|XXTEST|XXTEST_DOCREC01||XXTEST2||Passport||XXTEST_DOCREC01|Passport|XXTEST2123|||||US|||||||

METADATA|DocumentAttachment|SourceSystemOwner|SourceSystemId|PersonNumber|DocumentType|Country|DocumentCode|DataTypeCode|Title|URLorTextorFileName|File

MERGE|DocumentAttachment|XXTEST|XXTEST_DOCREC01|XXTEST2|Passport||XXTEST_DOCREC01|passport.png|passport.png|FILE|passport.png

Top 50 Fusion HCM Technical Questions - Part 2

 Top 50 Oracle Fusion HCM Technical Questions - Part 2

Top 50 Oracle Fusion HCM Technical Questions - Part 1 Click 

Q) Mandatory Records to Load Worker File for NEW Hire?

->  Worker , Person Name , Person Legislative Data, Assignment, Work Term.

Q) Sequence of WorkStructure Business Object While Load?

-> Work Structure Business Object loads in below sequence 

     1. Location

     2. Grade

     3. Job

     4. Orgnization

     5. Position

Q) If any Location is end dated and same location we are providing in Worker File then what will happen?

-> HDL will fail to load the data. It will give error as "You must enter a valid value for the LocationId field." 

Q) Can we delete Location using HDL?

-> We can not delete Location. You can end date the that Location and make inactive.

Q) What will happen in below Scenario?

        Scenario - If we have future date changes for any worker and we tried to load the current any changes for the same worker using HDL.

-> If we tried to load the current changes then it will purge the future changes because by default 

     PURGE_FUTURE_CHANGES value set as Y.

     If you want to keep future dated changes then set PURGE_FUTURE_CHANGES N so that it will         keep future dated changes after the data load.

Q) Which Role is required to process the file using HCM Data Loader?

->  You required the Human Capital Management Integration Specialist Role (ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB)

Q) How can you change the delimiter in HDL File at run time?

->  You can set delimiter in HDL File using SET FILE_DELIMITER command.

Q) "The party identified by the specified party ID does not exist" Error while loading Personal Payment Method using HDL?

-> Reason - > Party Id is not created for those Worker.

 Solution - Run Below scheduled process 

                1 - Maintain Party and Location Current Record information

                2 - Synchronize Person Records 

Q) How to create personal Payment Method incase joint account scenario?

-> Create two different personal payment method for each employee and both can be tagged to same account.

In this case primary account holder name will be displayed in UI for both methods. 

Q) Talent Profile data loaded successfully using HDL, But not able to see at front end.

->  Loaded Profile information is not able to see at front end because of two reasons

            1. Check Section Id/Section Name is correctly used

             2. Check Content Type Id/Content Type is used correctly.

Q) Load Non Workers with person type Pensioner using HDL?

-> You can use Person Type Code and System Person Type with Pensioner in WorTerm and assignment Metadata line. 

Q) Supervisor Load is failed what could be the reason and solution for the same?

-> Cause - Manager's hire date is earlier than assignments effective start date

      Solution -  Add Work Term and Assignment record which is later than Manger's hire date   along with supervisor record.

Q) Roles Required to execute the HDL Load (HCM Data loader)?

->  Human Capital Management Integration Specialist. 

          

Note - For any doubts or additional information, please reach out in the comment section.

 

Oracle Fusion HCM Extract Changes Only Mode – All Attributes vs Changed Attributes (Complete Guide)

Oracle Fusion HCM Extract Changes Only Mode (All Attributes vs Changed Attributes)

Oracle Fusion HCM Extract is one of the most used tools for extracting data from HCM Cloud.
When we run extracts daily/weekly, most of the time we don’t want the full output — we only want data that changed after the previous run.

If you want to see output for Changed and Marked Attribute with Previous Value - visit  Link 

For this requirement, Oracle provides Changes Only Mode in HCM Extracts.

In this blog you will learn:

• What is baseline in Changes Only mode

• How to enable Changes Only in Extract Definition

• Difference between:

  • All Attributes

  • Changed Attributes

• How to test changes using Person Management

---

🎥 Step-by-Step Video

If you want to see step by step video for this, visit: (Add Link Here)

---

✅ What is Changes Only Mode in HCM Extract?

Changes Only mode helps you extract:

• Only changed records since last run

• Only changed attributes

• Changed + marked attributes

• Previous values (old data) for auditing

---

📌 Available Changes Only Parameters

When you submit the extract, you will see these modes:

1. All Attributes

2. Changed Attributes

3. Changed and Marked Attributes

4. Changed and Marked Attributes with previous value

5. Changed, Marked Attributes under threading group

6. Changed, Marked Attributes, previous data under threading group

👉 In this blog we will cover the first 2 modes:

• All Attributes

• Changed Attributes

---

✅ Requirement (Business Scenario)

1. Create HCM Extract with Changes Only enabled

2. Change a worker record

3. Run extract again and fetch only the changed record

---

✅ Navigation to Create Extract

Go to:

My Client Groups → Data Exchange → Extract Definitions → Create (+)

---

Step 1: Create Extract Definition

Field	Value
Name	PersonData_Change
Start Date	Any date
Type	Full Profile
Changes Only	✅ Enable

---

Step 2: Create Data Group

Field	Value
Name	Person_Details
Tag Name	Person_Details
User Entity	PER_EXT_SEC_PERSON_UE
Threading Database Item	Extract Person ID
Threading Action Type	Object actions
Root Data Group	✅ Enable

---

⭐ What is Threading Database Item?

If you implement Changes Only Extract, it is mandatory to define a Threading Database Item.

It should be the unique identifier for the selected User Entity.

Example:

• Person User Entity → Person ID

• Assignment User Entity → Assignment ID

---

Step 3: Create Record

Field	Value
Sequence	10
Name	Person_Details
Tag Name	Person_Details
Type	Detail Record
Process Type	Fast Formula

---

Step 4: Create Attributes (Sample)

1️⃣ Person ID (Key Attribute)

Person_ID

Field	Value
Name	Person_ID
Tag Name	Person_ID
Data Type	Number
Type	Database Item Group
Database Item Group	Extract Person ID
Output Column	1
Key Attribute	✅ Enable

⭐ Why Key Attribute is Required?

In Changes Only mode, you must configure at least one Key Attribute to uniquely identify each output row.

---

2️⃣ Person Full Name

Field Value Name Person_FullName Data Type Text Database Item Group Person Full Name Output Column 2

---

3️⃣ Person Gender

Field Value Name Person_Gender Data Type Text Database Item Group Person Gender Output Column 3

---

4️⃣ Person Date of Birth

Field Value Name Person_DOB Data Type Date Database Item Group Person Date Of Birth Output Column 4

---

Step 5: Define Delivery Option

Field	Value
Delivery Option Name	Data
Output Type	Data
Output Name	Data
Delivery Type	None

---

Step 6: Compile & Validate Extract

Navigate to:

Extract Execution Tree → Compile formulas → Validate

Once validation is successful, submit the extract.

---

✅ Testing Changes Only Mode (Real Example)

Mode 1: All Attributes (Baseline)

Submit extract with parameter:

✅ All Attributes

Output

It will extract full data output at that point of time.

📌 This run becomes your baseline.

If you want to see step by step video for visit  Link

---

Make a Change in Person Record

Now go to:

My Client Groups → Person Management

• Open any worker

• Change Person Name

• Save

---

Mode 2: Changed Attributes

Now run extract again with:

✅ Changed Attributes

Output

• Extract will compare with the previous baseline run

• It will fetch only those records which changed after last run

So you will get only changed worker in output.

If you want to see step by step video for Changed and Marked Attribute - visit  Link 

---

⭐ Other Modes (Quick Explanation)

Changed and Marked Attributes

This mode fetches:

• Changed records

• Plus attributes marked as change

What is “Marked as Change”?

At attribute level, you can enable:

✅ Marked as Change

Meaning:
Even if that attribute didn’t change, it will still be included in output when the record changes.

If you want to see details for Changed and Marked Attribute with Previous Value - visit  Link 

---

Changed and Marked Attributes with Previous Value

This mode fetches:

• Changed records

• Changed + marked attributes

• Old values (previous values) for auditing

---

🔗 Internal Links 

• Oracle Fusion HCM Extract – Complete Guide

• Oracle HDL Load Worker Data

• Oracle HDL Common Errors and Fixes

• Oracle Fusion HCM Technical Interview Questions

• Oracle eText Template BIP Report

---

⭐ FAQs

Q1. What is Changes Only mode in HCM Extract?

Changes Only mode allows you to extract only those records that changed since the last extract run (baseline).

Q2. What is baseline in HCM Extract Changes Only?

Baseline is the previous successful extract output used for comparison in the next run.

Q3. Is threading database item mandatory for changes only extract?

Yes, threading database item is mandatory because it uniquely identifies records for change tracking.

Q4. What is the difference between All Attributes and Changed Attributes?

All Attributes returns full data output and is used as baseline, while Changed Attributes returns only changed records after baseline.

Q5. What is Marked as Change in HCM Extract?

Marked as Change forces an attribute to appear in output whenever a record changes, even if that attribute did not change.

---

⭐ Overview 

Oracle Fusion HCM Extract

 Sample Templates for eText BI Publisher Reports (Delimiter & Fixed Position)

Introduction to eText BI Publisher Reports

Oracle BI Publisher (BIP) provides eText report templates to generate text-based output files such as .txt, .dat, or interface files required for integrations with external systems.

Unlike PDF or Excel outputs, eText reports are mainly used when:

• Data must follow a specific layout

• Files are consumed by external payroll, banking, or legacy systems

• Strict formatting rules (delimiter or fixed length) are required

In this blog, we’ll cover:

• What eText BI Publisher reports are

• how to create eText report in BI Publisher

• Differences between Delimiter-Based and Fixed Position-Based eText

• BI Publisher eText report example

• how to create fixed position eText report

• common errors in BI Publisher eText report

---

Difference Between Delimiter & Fixed Position eText

Delimiter VS Fixed Position eText

You can see step by step video to develop eText BIP Report using this Link

---

🔹 Sample 1: Delimiter-Based eText Template

This template generates output with values separated by a delimiter (for example, |).

You can see step by step video to develop eText BIP Report using this Link

<TEMPLATE TYPE>	DELIMITER_BASED
<OUTPUT CHARACTER SET>	iso-8859-1
<CASE CONVERSION>	UPPER
<NEW RECORD CHARACTER>	Carriage Return

 

<LEVEL>	DATA_DS
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	TableHeader
20	Alpha	'Person Id'
1	Alpha	'|'
20	Alpha	'Title'
1	Alpha	'|'
20	Alpha	'First Name'
1	Alpha	'|'
20	Alpha	'Last Name'

 

<LEVEL>	G_1
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	CLRDAta
20	Alpha	PERSON_ID
1	Alpha	'|'
20	Alpha	TITLE
1	Alpha	'|'
20	Alpha	FIRST_NAME
1		'|'
20	Alpha	LAST_NAME
<END LEVEL>	G_1

 

<END LEVEL>

DATA_DS

 This format is useful when the target system expects delimiter-separated text files.