Oracle HCM Post Conversion ESS Jobs After HDL

 

✅ Post Conversion Best Practices in Oracle HCM Cloud  – ESS Jobs After HDL

When you complete a data conversion or perform incremental updates using HDL (HCM Data Loader) in Oracle HCM Cloud, the work is not finished yet. HDL Post Conversion Processes.

A successful HDL load updates core tables, but several dependent tables and search indexes still need to be refreshed for:

• Correct reporting

• Accurate person search results

• Manager hierarchy visibility

• Role provisioning and LDAP synchronization

• Seniority date creation

This article covers the most important post conversion ESS processes, when to run them, and the best scheduling strategy.

---

📌 Why Post Conversion ESS Processes Are Required?

After bulk HDL loads, Oracle HCM Cloud may not automatically:

• Update manager hierarchy tables

• Rebuild person keyword search indexes

• Synchronize person data to consuming applications

• Push role/user requests to LDAP

• Generate default seniority date records

Running the right ESS processes at the right time avoids:

❌ Missing managers in hierarchy
❌ People not appearing in search
❌ Incorrect reporting
❌ Delayed user provisioning
❌ Seniority records not created

---

✅ Post Conversion ESS Processes (Complete List)

#	Program	Description
1	Synchronize Person Records	Publishes events to consuming applications (example: TCA model) for changes in person/assignment details.
2	Refresh Manager Hierarchy	Refreshes denormalized hierarchy table PER_MANAGER_HRCHY_DN for performance.
3	Update Person Search Keywords	Populates keywords into PER_KEYWORDS table for fast search.
4	Optimize Person Search Keywords Index	Optimizes/rebuilds the PER_KEYWORDS index.
5	Autoprovision Roles for All Users	Evaluates all users against role provisioning rules (heavy + LDAP intensive).
6	Send Pending LDAP Requests	Sends user and role requests to LDAP.
7	Send Personal Data for Multiple Users to LDAP	Syncs name/email/manager fields from HCM to LDAP after bulk updates.
8	Synchronize Person Assignments from Position	Required if using Position Management and PositionOverrideFlag = Y.
9	Calculate Seniority Dates	Generates default V3 seniority records based on configured rules.

---

⚡ Auto-Triggered Processes After Worker HDL Load

By default, Oracle triggers these after Worker.dat finishes:

✅ Refresh Manager Hierarchy
✅ Update Person Search Keywords

How to disable auto-trigger?

You can disable one or both using a SET instruction in Worker.dat.

This is helpful when:

• You are running multiple worker batches

• You want to run these processes only once at the end

---

📅 When to Run Post Conversion ESS Programs?

This is a debated topic, but below is a practical schedule that works for most conversions.

Program	One-time Conversion	Incremental Updates	Notes
Synchronize Person Records	✅ Yes	✅ Yes	Run after bulk loads, best after hours.
Refresh Manager Hierarchy	✅ Yes (Auto-trigger)	✅ Yes (Auto-trigger)	Run manually if auto-trigger disabled.
Update Person Search Keywords	✅ Yes (Auto-trigger)	✅ Yes (Auto-trigger)	Run manually if auto-trigger disabled.
Optimize Person Search Keywords Index	✅ Yes	✅ Yes	Best daily during low system usage.
Autoprovision Roles for All Users	❌ No	❌ No	Run only when provisioning rules change.
Send Pending LDAP Requests	✅ Yes	✅ Yes	Best daily schedule for future dated requests too.
Personal Data for Multiple Users to LDAP	✅ Yes	Depends	Required only after bulk name/email/manager updates.
Synchronize Person Assignments from Position	Depends	Depends	Required for full HR + position management.
Calculate Seniority Dates	✅ Yes	✅ Yes	Required after worker loads if using seniority.

---

🔍 Deep Dive: How to Run Each ESS Process

---

1) Synchronize Person Records

This job is resource intensive because it publishes events to SOA.

Recommended Run Time

✅ After hours
✅ After bulk HDL worker loads

Parameters

1. From Date

2. To Date

3. After Batch Load (Yes/No/Blank)

How to run (Daily)

• From Date = System Date

• To Date = System Date

• After Batch Load = No

How to run (Specific Period)

Example:

• From Date = 12-Aug-2019

• To Date = 18-Aug-2019

⚠️ Important Note

• Maximum date range should be 7 days

• First run can accept more than 7 days

• Subsequent runs with >7 days may end in Warning and publish no events

---

2) Refresh Manager Hierarchy

Oracle stores manager hierarchy in a denormalized table:

📌 PER_MANAGER_HRCHY_DN

HDL updates do not always refresh this automatically unless auto-trigger is enabled.

Parameter

• Updated Within the Last N Days

  • Use 1 day for daily schedule

  • Leave blank for initial full refresh

---

3) Update Person Search Keywords

This process populates the keyword table:

📌 PER_KEYWORDS

Parameters

1. Batch Id

2. Name

3. After Batch Load (Yes/No/Blank)

Best Ways to Run

✅ For a specific HDL batch

• Enter Batch Id only

• Leave other parameters blank

✅ For one person

• Enter Name only

• Leave others blank

✅ Delta/Incremental mode

• After Batch Load = Yes

• Works only when delta size < 20K

⚠️ For delta > 20K
Run with no parameters (All People)

---

4) Optimize Person Search Keywords Index

This improves performance of keyword search.

Recommended Scheduling

✅ Daily during maintenance window
✅ Run after “Update Person Search Keywords”

Parameters

1. Maximum Optimization Time (default 180 minutes)

2. Optimization Level

   • Full Optimization (default)

   • Rebuild Index

---

5) Autoprovision Roles for All Users

This job evaluates ALL users against auto role provisioning rules.

⚠️ It is heavy and can generate many LDAP requests.

Best Practice

❌ Do not schedule daily
✅ Run manually only when provisioning rules change

Parameter

• Process Generated Role Requests (Yes/No)

✅ Recommended: No (defer processing)

---

6) Send Pending LDAP Requests

This job sends pending user/role requests to LDAP.

Best Practice

✅ Run after bulk HDL worker loads
✅ Schedule daily for ongoing requests + future dated processing

Parameters

1. User Type (All/Party/Person)

2. Batch Size

   • Use A (auto calculate)

---

7) Send Personal Data for Multiple Users to LDAP

This job ensures LDAP personal data matches HCM:

• First Name

• Last Name

• Email

• Manager

When required?

✅ After bulk updates via HDL or Spreadsheet loaders
✅ Recommended once after conversion

---

8) Synchronize Person Assignments from Position

Required if:

• You are using Position Management

• You load assignments with PositionOverrideFlag = Y

• You want manager or attributes synchronized from position

Parameters

1. Past Period in Days (default 30)

2. Run at Enterprise Level (Yes/No)

3. Legal Employer

---

9) Calculate Seniority Dates

📌 Important:
You cannot create V3 seniority records using HDL.
HDL supports only updates.

So after loading Worker.dat, you must run:

✅ Calculate Seniority Dates

Parameters

1. Person Number (optional list)

2. Past Period in Days (default 1)

3. Include Terminated Work Relationships

4. Legal Employer

5. Union

6. Selected Seniority Date Rules

---

⚙️ Performance Tip: Chunk Size for Calculate Seniority Dates

The Past Period in Days controls how many workers are picked.

• Large period = more workers = slower run

• Small period = fewer workers = faster run

Improve performance using multi-threading

Oracle supports multi-threading via profile option:

📌 PER_EMP_SD_MAX_PROCESS_REC

Steps

1. Navigate to Manage Profile Options

2. Create profile option:

• Profile Option Code: PER_EMP_SD_MAX_PROCESS_REC

• Display Name: PER_EMP_SD_MAX_PROCESS_REC

• Application: Global Human Resources

• Module: Employment

• Start Date: 01/01/1951

3. Enable it and allow update at Site level

4. Navigate to Manage Administrator Profile Values

5. Set site value (example: 2000 / 10000)

This value becomes the chunk size and controls number of threads.

---

✅ Recommended Post Conversion Run Sequence (Best Practice)

For a one-time conversion, this sequence is practical:

1. Refresh Manager Hierarchy

2. Update Person Search Keywords

3. Optimize Person Search Keywords Index

4. Calculate Seniority Dates

5. Send Pending LDAP Requests

6. Send Personal Data for Multiple Users to LDAP

7. Synchronize Person Records

---

🔗 Internal Links

• HDL Worker Data Load Guide → (URL)

• HDL Seniority Date Adjustments → (URL)

• HDL Seniority Hours Template → (URL)

• HDL Absence Entry Template → (URL)

• eText Template Report in Oracle Fusion  → (URL)

• Third Party Load in Oracle Fusion → (URL)

---

❓ Frequently Asked Questions (FAQ)

Q1. Are Refresh Manager Hierarchy and Update Person Search Keywords mandatory?

Yes. These processes ensure manager visibility and person search performance after HDL loads.

Q2. Can I disable auto-triggered processes after Worker.dat?

Yes. Use SET instructions in Worker.dat to prevent automatic execution.

Q3. Should I schedule “Autoprovision Roles for All Users” daily?

No. Run it only when auto role provisioning rules change.

Q4. Why are people not visible in search after HDL?

Usually because PER_KEYWORDS is not updated or the index needs optimization.

Q5. Why are managers missing after HDL?

Because PER_MANAGER_HRCHY_DN is not refreshed. Run Refresh Manager Hierarchy.

Q6. Why are seniority dates missing after conversion?

Because V3 seniority records are not created by HDL. Run Calculate Seniority Dates.

Q7. Which job sends new user accounts to LDAP?

Send Pending LDAP Requests.

Q8. When should I run Synchronize Person Records?

After bulk person loads, preferably after hours, using correct date range.

---

💬 Feedback & Comments

Have you faced issues after HDL conversion like:

• missing managers

• people not appearing in search

• delayed user provisioning

• seniority dates not created

Drop your questions in the comment section 👇

Examples of Loading Seniority Hours using Oracle HCM HDL

 

✅ Oracle HCM HDL: Load Seniority Hours (Create / Update / Delete) – Worker.dat Examples

For hourly paid workers, many organizations calculate seniority in hours instead of days. To support accurate seniority calculations in Oracle Fusion HCM, you can load seniority hours using HCM Data Loader (HDL).

In this post, you’ll learn how to create, update, and delete Seniority Hours using HDL with both:

• Source Keys (SourceSystemOwner + SourceSystemId)

• User Keys (AssignmentNumber + FromDate)

---

⭐ What are Seniority Hours in Oracle HCM?

Seniority Hours represent the number of hours worked that contribute to a worker’s length of service calculation.

This is mainly used for:

• Hourly paid workers

• Union or bargaining unit employees

• Time & Labor based seniority

• Payroll-driven seniority hours

---

📌 Sources of Seniority Hours Data

You can obtain seniority hours from:

• Oracle Time and Labor (OTL)

• Oracle Global Payroll

• A third-party time system

• External payroll system

---

✅ Important Prerequisites (Must Read)

Before loading seniority hours:

1) Assignment must exist

The assignment must already exist in Oracle HCM.

2) Assignment must be active

The assignment must be active as of the FromDate of the seniority hours.

3) Worker must be hourly paid

The worker must be paid hourly for the entire period you are loading hours.

---

🔍 How to Verify Loaded Seniority Hours

After loading, you can verify data from:

Option 1: UI Page

✅ Manage Seniority Dates page (worker level)

Option 2: Database Query

For multiple workers:
✅ Query table: PER_SENIORITY_HOURS

---

🧾 HDL Object Used

Seniority Hours are loaded using the HDL component:

✅ SeniorityHour (Worker.dat)

---

📂 File Name

📌 File Name:
Worker.dat

---

🔥 Examples of Loading Seniority Hours (HDL)

---

1) Create Seniority Hours Using Source Keys

METADATA|SeniorityHour|AssignmentId(SourceSystemId)|ToDate|FromDate|Hours
|SourceSystemOwner|SourceSystemId
MERGE|SeniorityHour|1031101972|2001/01/01|2000/01/01|500|VISION|UT00214

📌 Notes:

• SourceSystemOwner + SourceSystemId uniquely identify the record

• This is best for integrations from external systems

---

2) Create Seniority Hours Using User Keys

The user keys for SeniorityHour are:

✅ AssignmentNumber + FromDate

METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
MERGE|SeniorityHour|E00214|2001/01/01|2000/01/01|500

---

✏️ Updating Seniority Hours

---

3) Update Seniority Hours Using Source Keys

METADATA|SeniorityHour|AssignmentId(SourceSystemId)|ToDate|FromDate|Hours
|SourceSystemOwner|SourceSystemId
MERGE|SeniorityHour|1031101972|2001/01/01|2000/01/01|600|VISION|UT00214

📌 The update happens because the same SourceSystemOwner + SourceSystemId exists.

---

4) Update Seniority Hours Using User Keys

METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
MERGE|SeniorityHour|E00214|2001/01/01|2000/01/01|600

📌 Oracle identifies the record using:

• AssignmentNumber

• FromDate

---

🗑️ Deleting Seniority Hours

---

5) Delete Seniority Hours Using Source Keys

METADATA|SeniorityHour|AssignmentId(SourceSystemId)|SourceSystemOwner|SourceSystemId
DELETE|SeniorityHour|1031101972|VISION|UT00214

---

6) Delete Seniority Hours Using User Keys

METADATA|SeniorityHour|AssignmentNumber|ToDate|FromDate|Hours
DELETE|SeniorityHour|E00214|2001/01/01|2000/01/01|500

---

✏️ Updating Seniority Hours

✅ Example 1: Load Seniority Hours for Multiple Periods (Same Assignment)

Use this when you want to load hours month-wise / week-wise.

METADATA|SeniorityHour|AssignmentNumber|FromDate|ToDate|Hours
MERGE|SeniorityHour|E00214|2024/01/01|2024/01/31|168
MERGE|SeniorityHour|E00214|2024/02/01|2024/02/29|160
MERGE|SeniorityHour|E00214|2024/03/01|2024/03/31|176

Oracle HCM HDL: Load Seniority Date Template

 

✅ Oracle HCM HDL: Load / Update Seniority Date Adjustments (V3) – Examples + Worker.dat Templates

Seniority Date in Oracle HCM is the date used to calculate a worker’s length of service with the enterprise. It is commonly used for:

• Service anniversary calculations

• Leave / accrual eligibility

• Benefits eligibility

• Compensation / seniority-based policies

In this post, you’ll learn how to update V3 Seniority Dates using HCM Data Loader (HDL) with multiple real Worker.dat examples.

---

⭐ What is a Seniority Date in Oracle HCM?

A Seniority Date is a rule-based service date that Oracle uses to calculate service length for a worker.

Oracle allows seniority dates to be configured at:

• Person level

• Assignment level

• Work relationship level

And can be based on:

• Job

• Department

• Enterprise

• Location

• Legal Employer

• Position

• Grade

• Bargaining Unit

• Union Membership

How to Import/Load Organization/Third Parties Data in Oracle Fusion Using Import Management (CSV Template + Steps)

 

How to Import Organization Data in Oracle Fusion Using Import Management

Oracle Fusion applications provide Import Management to create or update business objects like Organization (Party).
This method is widely used in CX Sales, Fusion Service, and Trading Community Architecture (TCA).

In this blog, you will learn:

✅ How Organization import works

✅Load Third Parties in Oracle Fusion.

✅ Required attributes and validations
✅ How to prepare the CSV template
✅ How to create and submit import activity
✅ How to review import results
✅ Best practices to avoid duplicate data

---

🔥 What is Organization Import in Oracle Fusion?

Organization records represent party type = Organization in TCA.

Using Import Management you can:

• Create new organizations

• Update existing organizations

• Load data from external systems using SourceSystem mapping

---

✅ High-Level Steps (Process Flow)

1. Map source attributes → Oracle target attributes

2. Create CSV file using template

3. Create Import Activity

4. Validate and submit

5. Review import results

---

Step 1: Before You Start (Prerequisites)

Before importing Organization records, verify:

✅ 1. Parent records exist

If you’re importing child objects (like addresses), ensure parent Organization exists first.

✅ 2. Source System is configured

Navigate to:
Setup and Maintenance → Manage Trading Community Source System

You must know:

• SourceSystem

• SourceSystemReferenceValue

✅ 3. Identify unique record key

To avoid duplicates, decide how you will identify records.

---

Step 2: Choose Unique Identifier (Most Important)

All Organization records must be unique in Oracle Fusion.

You can identify organizations using either:

---

Option A: PartyNumber (Public Unique Identifier)

Use this when:

• Organization already exists

• You want to update the record

PartyNumber is visible in UI.

---

Option B: SourceSystem + SourceSystemReferenceValue

Use this when:

• You are creating new organizations

• You are loading from external system

• You want consistent integration keys

---

Step 3: Required Attributes for Organization Import

To successfully create an organization record, your CSV must include at least:

✅ Mandatory for Creating Organization

• OrganizationName

• PartyUsageCode

• SourceSystem (conditional)

• SourceSystemReferenceValue (conditional)

---

⭐ Key Required Fields Explained

1) OrganizationName (Required)

The name of the Organization party.

Example:

ABC Technologies Pvt Ltd

---

2) PartyUsageCode (Required)

This defines how the party is used.

Examples (depends on your setup):

• CUSTOMER

• PROSPECT

• SUPPLIER (if enabled)

• PARTNER

📌 Must exist as active value in:
HZ_PARTY_USAGES_B

---

3) SourceSystem & SourceSystemReferenceValue (Conditional)

Required if you are not using PartyNumber.

---

Step 4: Download Organization CSV Template

To download the template:

Navigate to:
Navigator → Tools → Import Management → Import Objects

Steps:

1. Search for Organization

2. Click Download

3. Edit the file in Excel or Notepad++

---

⚠️ Important Excel Tip

Sometimes Excel changes formatting (especially for large numbers).

Best practice:
✅ Use Notepad++ or Google Sheets for final save.

---

Step 5: Sample Organization CSV (Create)

Example format (basic):

OrganizationName,PartyUsageCode,SourceSystem,SourceSystemReferenceValue,ThirdPartyFlag
ABC Technologies Pvt Ltd,CUSTOMER,LEGACY,ORG_1001,Y

---

Step 6: Create Import Activity

Navigate:
Navigator → Tools → Import Management → Import Queue

Steps:

1. Click Create Import Activity

2. Enter Import Options:

   • Name: Organization_Import_01

   • Object: Organization

3. Upload CSV file

4. Click Next

---

Step 7: Map Fields and Validate

In the Map Fields screen:

• Oracle auto-maps most fields

• Review mappings carefully

• Fix unmapped columns

Then click:

✅ Validate Data

This checks:

• missing required fields

• wrong formats

• invalid values

---

Step 8: Submit Import Activity

On Review & Submit page:

Click:

✅ Submit

---

Step 9: Review Import Results

Go to:

Navigator → Tools → Import Management → Import Queue → All Imports

Search your import name.

Status meanings:

• Completed = Success

• Completed with errors = Partial success

• Unsuccessful = Failed

Click the import to open:
Import Status page

---

⭐ Best Practices (Must Follow)

✅ Avoid Duplicate Organizations

Use one unique identifier consistently:

• PartyNumber OR

• SourceSystem + SourceSystemReferenceValue

Do not mix randomly.

---

✅ Load in Correct Order

1. Organization

2. Organization Address

3. Organization Contacts

4. Child objects

---

✅ Use consistent PartyUsageCode

If PartyUsageCode is wrong/inactive → import fails.

---

🔥 Common Errors & Fixes

❌ Error: PartyUsageCode invalid

✅ Fix:

• Validate the code exists in HZ_PARTY_USAGES_B

• Ensure it is active

---

❌ Error: Duplicate record found

✅ Fix:

• Use correct PartyNumber

• Or use correct SourceSystemReferenceValue

---

❌ Error: Source system not found

✅ Fix:

• Configure source system in Setup and Maintenance

---

🔗 Internal Links 

• Oracle HCM HDL Templates (Worker, Assignment, Supervisor)

• Changes Only HCM Extracts Complete Guide

• Oracle Fusion HCM Technical Interview Questions

• Sample HDL Template for Benefit Enrollments

• Oracle eText Teamplate BIP Report.

---

⭐ FAQs

Q1. What is Import Management in Oracle Fusion?

Import Management is a tool to create or update Oracle Fusion business objects using CSV files.

Q2. Which object is used to import Organization data?

You must select Organization object in Import Management.

Q3. What is the unique identifier for Organization import?

You can use:

• PartyNumber
  OR

• SourceSystem + SourceSystemReferenceValue

Q4. Is OrganizationName mandatory for import?

Yes, OrganizationName is mandatory when creating a new organization.

Q5. Where can I check import status in Oracle Fusion?

Go to:
Navigator → Tools → Import Management → Import Queue → All Imports

🔐 How to Lock and Unlock User Accounts Using HDL in Oracle Fusion HCM (Step-by-Step Guide)

 Step-by-Step Instructions for Administrators

Locking and unlocking user accounts is a common requirement for Oracle Fusion HCM administrators. Whether an employee has left the organization, access must be temporarily restricted, or security compliance requires action, Oracle HCM provides a simple way to lock/unlock accounts using HCM Data Loader (HDL).

In this blog, you’ll learn how to lock and unlock user accounts using HDL, along with the required HDL file format, steps to load it, and the process required to apply changes.

---

✅ Prerequisites

Before you begin, make sure you have:

• Access to perform HDL operations

• Valid Person Numbers for users you want to lock/unlock

• Access to run required ESS process (Send Pending LDAP Requests)

• Admin privileges to verify the user status

---

🔒 Locking a User Account Using HDL

To lock a user account in Oracle Fusion HCM, you need to set the Suspended flag = Y in the User HDL file.

---

Step 1: Prepare the HDL File (User.dat)

Use the following format:

METADATA|User|PersonNumber|Suspended
MERGE|User|<Enter Person Number>|Y

Example:

METADATA|User|PersonNumber|Suspended
MERGE|User|E12345|Y

---

Step 2: Save and Compress the File

1. Save the file as: User.dat

2. Compress it into a ZIP file:

   • Example ZIP name: LockUser.zip

---

Step 3: Upload the HDL File

Navigate to:

My Client Groups → Data Exchange → HCM Data Loader → Import and Load

Then:

1. Click Import File

2. Upload the ZIP file

3. Submit the load

---

Step 4: Run Required Process (Very Important)

After HDL loads successfully, you must run:

✅ Send Pending LDAP Requests

This process applies the account changes to the LDAP directory.

---

Step 5: Verify User is Locked

Go to:

Setup and Maintenance → Create Implementation User

Search using the person number / username and confirm the account is locked.

---

🔓 Unlocking a User Account Using HDL

To unlock a user account, set the Suspended flag = N.

---

Step 1: Prepare the HDL File (User.dat)

METADATA|User|PersonNumber|Suspended
MERGE|User|<Enter Person Number>|N

Example:

METADATA|User|PersonNumber|Suspended
MERGE|User|E12345|N

---

Step 2: Save and Compress the File

1. Save as User.dat

2. Zip it:

   • Example ZIP name: UnlockUser.zip

---

Step 3: Upload the HDL File

Navigate to:

My Client Groups → Data Exchange → HCM Data Loader → Import and Load

1. Click Import File

2. Upload ZIP file

3. Submit

---

Step 4: Run Required Process (Very Important)

After HDL loads successfully, you must run:

✅ Send Pending LDAP Requests

This process applies the account changes to the LDAP directory.

---

Step 5: Verify User is Unlocked

Go to:

Setup and Maintenance → Create Implementation User

Confirm the user is now active/unlocked.

---

⭐ Best Practices and Recommendations

• Always double-check the Person Number before locking/unlocking

• Keep an audit log of user account changes

• Notify users when their account is unlocked (unless security policy says otherwise)

• Regularly review locked accounts to avoid unnecessary access restrictions

• Run Send Pending LDAP Requests after every HDL user suspension change

---

⚠️ Common Issues and Troubleshooting

Issue 1: HDL loads successfully but user is still active

✅ Solution:
Run Send Pending LDAP Requests process.

---

Issue 2: Person number not found

✅ Solution:
Confirm the person exists and has a user account created.

---

Issue 3: Changes not reflecting immediately

✅ Solution:
LDAP sync may take time. Wait 5–10 minutes after process completion.

---

📌 FAQ

1. Can we lock a user account in Oracle Fusion HCM using HDL?

Yes. You can lock a user account using HDL by setting the field Suspended = Y in User.dat.

---

2. What HDL object is used to lock/unlock users?

The HDL object used is:

User

---

3. What does the Suspended flag mean in HDL?

• Y = user is locked/suspended

• N = user is active/unlocked

---

4. Do we need to run any process after loading HDL?

Yes. You must run:

✅ Send Pending LDAP Requests

---

5. Where can we verify if a user is locked/unlocked?

You can verify in:

Setup and Maintenance → Create Implementation User

---

6. Can we lock multiple users in one HDL file?

Yes. Add multiple MERGE lines:

METADATA|User|PersonNumber|Suspended
MERGE|User|E1001|Y
MERGE|User|E1002|Y
MERGE|User|E1003|Y

---

7. Is locking a user same as terminating an employee?

No. Locking only disables login access. Termination affects employment and HR records.

---

✅ Conclusion

Locking and unlocking user accounts using HDL is one of the fastest and cleanest methods available for Oracle Fusion HCM administrators. By updating the Suspended flag and running Send Pending LDAP Requests, you can manage user access securely and efficiently.