The Manager Hierarchy: How It's Maintained
In many situations, a person's manager hierarchy must be readily available. For example, a person's line manager may be required during line manager security check, and business intelligence reports often retrieve data based on a manager hierarchy.
How the Manager Hierarchy Is Maintained
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 a separate manager hierarchy table. This table is known as the denormalized manager hierarchy. The denormalized manager hierarchy ensures that a person's manager hierarchy is both easily accessible and up to date.
These denormalized tables are populated during processing based on the source data in the PER_ASSIGNMENT_SUPERVISORS_F table.
- PER_MANAGER_HRCHY_DN / CF – This table is required for evaluating line manager security, head counts, and some of the flows in HCM are based on this table. It’s also used for the assignment list dimensions for OTBI.
- PER_MANAGER_HRCHY_REPORTEES_DN is specific to OTBI reporting only and for assignment manager dimensions data.
When You Run the Refresh Manager Hierarchy Process
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 table. You use the Refresh Manager Hierarchy process to populate the denormalized manager hierarchy table when person records are migrated from other applications.
How You Run the Refresh Manager Hierarchy Process
You run the Refresh Manager Hierarchy process in the Scheduled Processes work area. To run the process, you must have the Human Resource Specialist job role. The process has no default schedule. You can run the process occasionally to perform a complete refresh of the denormalized manager hierarchy. Alternatively, you can specify a schedule to run the process at regular intervals. Refresh Manager Hierarchy processes all types of manager hierarchies.
You can run the process using these processing modes based on the parameter Updated Within the Last N Days value.
| Updated Within the Last N Days | Mode | Details |
|---|---|---|
| No parameter value (Blank/NULL) | Normal - Full Run | Populates the denormalized tables PER_MANAGER_HRCHY_DN and PER_MANAGER_HRCHY_CF from the source of PER_ASSIGNMENT_SUPERVISORS_F by executing deletes and inserts of denormalized data for ALL the assignment supervisor rows |
| +ve parameter value | Normal – Incremental Run | Populates the denormalized tables PER_MANAGER_HRCHY_DN and PER_MANAGER_HRCHY_CF from the source of PER_ASSIGNMENT_SUPERVISORS_F by executing deletes and inserts of denormalized data for assignment supervisor rows updated or created in last N days (for example. if 5 is provided as parameter value then data updated or created in last 5 days will be processed) |
| 0 parameter value | OTBI – Full Run | Populates the denormalized table PER_MANAGER_HRCHY_REPORTEES_DN from the source of PER_ASSIGNMENT_SUPERVISORS_F by executing deletes and inserts of denormalized data for ALL the assignment supervisor rows during processing and refers to data of other denormalized tables PER_MANAGER_HRCHY_DN and PER_MANAGER_HRCHY_CF |
| -ve parameter value | OTBI – Incremental Run | Populates the denormalized table PER_MANAGER_HRCHY_REPORTEES_DN from the source of PER_ASSIGNMENT_SUPERVISORS_F by executing deletes and inserts of denormalized data for assignment supervisor rows updated or created in last N days (for example, if -5 is provided as parameter value then data updated or created in last 5 days will be processed) |
To improve performance, few additional parameters are introduced that are considered when running process with NULL or 0 parameter value, that is, Normal – Full Run or OTBI – Full Run
| Parameter | Values | Details |
|---|---|---|
| Ignore Inactive Assignments During Full Refresh | Yes or No (Default No) | If set to Yes, instead of processing all assignment supervisor data, will process only active assignments supervisor data and ignores inactive assignments |
| Ignore Historical Data During a Full Refresh | Yes or No (Default No) | If set to Yes, instead of processing all assignment supervisor data, will process only current or future assignments supervisor data and ignore historical (date effective) data of assignment supervisor |
Normal denormalized tables (PER_MANAGER_HRCHY_DN and PER_MANAGER_HRCHY_CF) are automatically synchronized when assignment supervisor data is created or updated from the application pages (New Hire, Change Manager, and so on) or HDL. Automatic synchronization of denormalized data won't happen if Events process is disabled, that is if, HRC: Disable HcmEvents Processing (HRC_DISABLE_HCM_EVENTS_PROCESSING) profile is set to Y, or when assignment supervisor data being uploaded through HDL and in .dat file post process task of RefreshManagerHierarchy is disabled using the setting SET DISABLE_POST_PROCESS_TASKS RefreshManagerHierarchy, or due to SOA composite instances not getting triggered or infrastructure issues.
Guidelines for Running the Process
These are the guidelines to run the process.
- Normal Full Mode (parameter value of blank/NULL) can be run ad-hoc if denormalized data isn’t in synchronization with source assignment supervisor data, or can be scheduled to run once every week (during weekend) or daily once if more frequent full refresh is needed.
- Normal Incremental Mode (positive value) can be scheduled to run daily or multiple times in day if needed, with parameter value, for example 1, all assignment supervisor data created or updated in last 1 day will be considered for processing.
- OTBI Full Mode (parameter value of 0) and OTBI Incremental Mode (parameter value of -ve. For example, -1 needed only if OTBI reports are based on assignment manager dimensions data. De-normalized table PER_MANAGER_HRCHY_REPORTEES_DN doesn’t get synchronized automatically when assignment supervisor data gets created or updated from the application pages or HDL. Process can be scheduled to run in OTBI Full or Incremental mode once daily for populating data.
- In addition to performing full refreshes of the manager hierarchy, you can perform incremental refreshes. With this approach, you refresh the hierarchy based on manager changes occurring in the previous N days. Schedule a full refresh every month or quarter and an incremental refresh every day or week, for example.
- You can select to run for a period of days since the last updated date, and you can exclude inactive assignment and any historical data by selecting the Ignore Inactive Assignments and Ignore Historical Data options when the process is run on Full mode.