Oracle Fusion HCM :: Person Search Keywords

 ✅ Update Person Search Keywords – Process Guide

�� Overview

Person search keywords are derived from key attributes of:

· Person records

· Employment records

· Profile records

These keyword values are stored in the table:

· PER_KEYWORDS

�� This table is indexed to optimize search performance across the application.

---

�� How Keywords Are Updated

✅ Automatic Updates

· When a keyword-related attribute changes (e.g., phone number, language skill):

o An event is triggered

o System services automatically update PER_KEYWORDS

· When a new person is created:

o Keywords are populated automatically

---

⚠️ Why You Must Run the Process

Even though updates are automatic, the process must still be run periodically because:

1. Future-dated changes are NOT processed automatically

2. Ensures recovery from:

o Temporary failures

o Missed event triggers

3. Guarantees data consistency in PER_KEYWORDS

---

❌ When You Don’t Need to Run It

You don’t need to run the process if:

· Changes are made via standard Fusion UI (except):

o Work Structures

o CRM Resource Information

�� In such cases, updates happen automatically and immediately

---

▶️ Execution Scenarios

�� 1. For a Specific Batch ID

· Used when:

o HDL post-processing is disabled

· Action:

o Run HCM Data Loader Worker Post Processing

o Use UCM Content ID

---

�� 2. For a Specific Person

· Use the Name parameter

· When to use:

o Immediate correction for an individual

✅ Execution Time: ~30 seconds to 1 minute

---

�� 3. Delta Processing (Incremental Updates)

· Use parameter:

· After Batch Load = Y

· Updates:

o Changed workers

o Newly loaded workers

✅ Use when:

· Total changes 20,000 records

⏱️ Execution Time:

· ~20 minutes per 20,000 records

---

�� 4. Full Population (All Persons)

· Submit with all parameters = NULL

· Recreates keywords for entire system

✅ Use when:

· New language installed

· Changes > 20,000 records

⚠️ High system impact → run carefully

---

⏰ Scheduling Strategy

You can run manually or schedule periodically

�� Frequency Guidelines

Data Volume	Recommended Frequency
High volume	Daily / multiple times
Medium	Weekly
Low	Monthly

�� Always run during off-peak hours to avoid performance issues

---

✅ Best Practices

✔️ Do’s

· Schedule daily delta run:

· After Batch Load = Y

· Enable HDL post-processing for keyword updates

· For large loads (>20,000):

o Disable post-processing

o Run full refresh manually

· Coordinate with Manager Hierarchy:

o Run Refresh Manager Hierarchy daily with:

o Updated Within Last N Days = 1

�� Helps keep delta size manageable (<20,000)

---

❌ Don’ts

· ❌ Don’t run full refresh (NULL parameters) frequently
�� Impacts performance and indexing

· ❌ Don’t run full refresh unnecessarily
�� Only when:

o Large data changes (>20,000)

o Structural updates (e.g., language install)

· ❌ Don’t use unsupported Batch IDs:

· -100, -200

�� Can break keyword search behavior

---

⚡ Performance Considerations

· Full refresh rebuilds entire PER_KEYWORDS table

· Can:

o Impact system performance

o Affect search index stability

�� Always schedule during low system usage

---

✅ Summary

· Keywords are mostly updated automatically via events

· Manual process ensures:

o Future-dated data inclusion

o Recovery from missed updates

· Choose processing mode carefully:

o Delta (preferred) for daily use

o Full refresh only when necessary

· Follow strict scheduling and best practices to avoid performance issues