Fusion HCM: Best Practices for Refresh Manager Hierarchy Process (Doc ID 2937521.1)

Last updated on JULY 14, 2024

Applies to:

Goal

In many situations, a person's manager hierarchy must be readily available. For example, a person's line manager may be required during an approval process, and business intelligence reports often retrieve data based on a manager hierarchy.

A person's manager hierarchy could be derived from active data tables, but the impact of that approach on performance is unpredictable. Therefore, the complete manager hierarchy for each person is extracted from data tables and stored in separate manager hierarchy tables:

• PER_MANAGER_HRCHY_DN / CF - normal tables used for evaluating line manager security, headcounts, for some of the UI flows in HCM area and assignment list dimensions for OTBI
  
• PER_MANAGER_HRCHY_REPORTEES_DN - is specific to OTBI reporting only for assignment manager dimensions data
  

These table are known as the denormalized manager hierarchy.

Whenever a change is made to a person's manager hierarchy through the application pages, the change is reflected automatically in the denormalized manager hierarchy tables. You use the Refresh Manager Hierarchy process to populate the denormalized manager hierarchy tables when person records are migrated from other applications.

This document provides details on how this process works and describes the best practices you should follow when scheduling it in order to avoid system performance issues.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.