Oracle Fusion HCM :: Refresh Manager Hierarchy

✅ Manager Hierarchy Maintenance in HCM

✅  Overview

A person’s manager hierarchy could be derived dynamically from transactional tables, but doing so can negatively impact system performance.

To address this, Oracle HCM maintains a denormalized (precomputed) manager hierarchy, which:

· Improves performance

· Ensures quick access

· Keeps hierarchy data consistently updated

This hierarchy is derived from the source table:

· PER_ASSIGNMENT_SUPERVISORS_F

---

✅  Denormalized Hierarchy Tables

1. PER_MANAGER_HRCHY_DN / CF

· Core tables for:

o Line manager security

o Headcount calculations

o HCM application flows

· Used in:

o OTBI Assignment List dimensions

---

2. PER_MANAGER_HRCHY_REPORTEES_DN

· Used exclusively for:

o OTBI reporting

o Assignment manager dimension data

---

✅  Automatic vs Manual Refresh

✅ Automatic Refresh

The hierarchy is automatically updated when:

· Manager changes are made via:

o Application pages (e.g., New Hire, Change Manager)

o HDL loads

❌ Automatic Refresh Does NOT Occur When:

· Profile HRC_DISABLE_HCM_EVENTS_PROCESSING = Y

· HDL uses:

· SET DISABLE_POST_PROCESS_TASKS RefreshManagerHierarchy

· SOA/Integration issues prevent event triggering

✅  In these cases, manual execution is required

---

▶️ Running Refresh Manager Hierarchy Process

✅  Navigation

Navigator > Tools > Scheduled Processes

✅ Required Role: Human Resource Specialist

---

⚙️ Processing Modes

The behavior of the process depends on the parameter:

✅  Parameter: Updated Within the Last N Days

Parameter Value	Mode	Description
NULL / Blank	Normal – Full Run	Rebuilds PER_MANAGER_HRCHY_DN & CF for all active assignments
Positive (e.g., 5)	Normal – Incremental Run	Refreshes records updated/created in last N days
0	OTBI – Full Run	Rebuilds PER_MANAGER_HRCHY_REPORTEES_DN completely
Negative (e.g., -5)	OTBI – Incremental Run	Updates OTBI table for last N days

---

⏱️ Minimum Execution Intervals

Mode	Minimum Interval
Normal Full Run	18 hours
Normal Incremental Run	1 hour

✅  If run more frequently, the process will be skipped

---

⚡ Additional Parameters (Full Run Only)

Parameter	Values	Description
Ignore Inactive Assignments	Yes (Default) / No	Include/exclude inactive assignments
Ignore Historical Data	Yes / No (Default)	Exclude/include past dated records

---

�� OTBI Consideration

· Table PER_MANAGER_HRCHY_REPORTEES_DN:

o Does NOT auto-sync

o Must be refreshed manually

· Required only if:

o OTBI reports use manager hierarchy dimensions

---

✅  Recommended Scheduling Strategy

✅ Best Practice Approach

1. Normal Full Run

· Frequency: Weekly (weekend) or daily (if needed)

· Use case:

o Data mismatch

o Initial setup or correction

---

2. Normal Incremental Run

· Frequency: 1–3 times per day

· Example:

o Parameter = 1 → processes last 1 day changes

---

3. OTBI Runs

· Full or Incremental:

o Schedule daily

· Required only for OTBI reporting accuracy

---

✅  Suggested Refresh Strategy

· Daily: Incremental refresh

· Weekly/Monthly: Full refresh

· Ad-hoc: When hierarchy issues are detected

---

⚠️ Key Notes

· Incremental refresh improves performance for frequent updates

· Full refresh ensures complete synchronization

· Always check:

o Event processing

o HDL configurations

o Integration health

---

✅ Summary

· Manager hierarchy is stored in denormalized tables for performance

· Automatically updated in most cases

· Use Refresh Manager Hierarchy process when automatic sync fails or for OTBI data

· Choose between Full vs Incremental runs based on the situation

· Follow a balanced scheduling strategy for optimal results