Oracle Fusion HCM :: Apply Name Formats to Person Names, Keywords, and LDAP

✅ Overview

When you modify a person name format, the changes are not automatically applied to existing records.

✅ To reflect the updated format, you must run the job set:

Apply Name Formats to Person Names, Keywords, and LDAP

---

✅ Job Set Components

This is a parent job set that automatically executes the following child processes:

1. Apply Name Formats to Person Names

2. Update Search Person Keywords

3. Send Personal Data for Multiple Users to LDAP

✅ You only need to run the parent job set
❌ Do NOT run child processes separately

---

⚙️ How the Process Works

✅ Execution Flow

1. Step 1 (Sequential)

o Runs:

§ ✅ Apply Name Formats to Person Names

2. Step 2 (Parallel Execution)

o Runs:

§ ✅ Update Search Person Keywords

§ ✅ Send Personal Data for Multiple Users to LDAP

---

⚠️ Failure Behavior

· If Step 1 succeeds but any process in Step 2 fails:

o ✔ Successful processes are applied

o ❌ Failed child processes are marked as failed

o ❌ Parent job is also marked as failed

---

✅ Execution Restriction

While this job set is running:

· You cannot run or schedule individually:

o Apply Name Formats to Person Names

o Update Search Person Keywords

o Send Personal Data for Multiple Users to LDAP

---

▶️ How to Run the Job Set

✅ Navigation

Navigator > Tools > Scheduled Processes

✅ Steps

1. Click Schedule a Process

2. Select Job Set

3. Search for:

4. Apply Name Formats to Person Names, Keywords, and LDAP

5. Click OK

6. Enter parameters for each job (if prompted)

7. Submit the job

---

✅ Child Process: Apply Name Formats to Person Names

✅ Purpose

Applies updated formats to the following fields:

· Display Name

· Full Name

· List Name

· Order Name

---

⚙️ Parameters

Parameter	Description
Format Type	Specifies which name format to apply (Display, Full, List, Order)
Country	Applies format for a specific country

---

✅ When to Run This Job

Run the job manually in these scenarios:

· ✅ Name format definition is changed

· ✅ New language is installed

· ✅ After P2T (Production to Test)

· ✅ After data masking activities

---

✅ Best Practices

✔️ Do’s

· Always run the job:

o Immediately after format changes

o After language updates or environment refresh

· Run only when business-relevant changes occur

---

❌ Don’ts

· ❌ Do NOT schedule this job for regular execution

· ❌ Avoid unnecessary runs (causes redundant processing and system load)

---

⚡ Key Considerations

· Name changes impact:

o UI display

o Search behavior (keywords)

o LDAP synchronization

· The process ensures consistency across all layers:

o Database

o Search index

o External directories (LDAP)

---

✅ Summary

· Changing name formats alone does not update existing data

· Run the job set to propagate changes

· Execution includes:

o Name updates

o Keyword refresh

o LDAP synchronization

· Use it only when needed, not on a schedule