iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Oracle HCM position hierarchy is a date-effective set of parent-position relationships. When manager synchronization is configured to use it, the incumbent in a parent position can become the line manager for an assignment in a child position. To implement it, enable the feature, establish and verify parent relationships, configure position synchronization, and plan how assignment changes will be applied. HDL can load the relationships, but it does not replace assignment synchronization.
What is Oracle HCM position hierarchy?
Oracle describes it succinctly: “Position hierarchy defines positions’ relationships.” In practice, each position can have a parent position, representing the next position up in the hierarchy. Once enabled, administrators can specify that parent when creating or editing positions. The relationships can also support synchronizing assignment line managers.
The HCM position hierarchy is not the same thing as a position tree. Both represent hierarchical structures, but they have different administration and uses.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Structure | Relationship model | Documented uses | Operational focus |
|---|---|---|---|
| HCM position hierarchy | Positions are related through effective-dated parent-position relationships. | Position relationships and, when configured, assignment manager synchronization. | Maintain parent positions and plan how affected assignments are synchronized. Oracle: HCM Position Hierarchy |
| Position tree | A separate HCM tree structure, which can have multiple versions and one top node. | Budgeting, organizational planning, and security. | Maintain the tree structure and its versions. Oracle: HCM Trees |
Choose the structure according to the task. A position tree is not a substitute for parent-position relationships when the goal is to use those relationships for manager synchronization.
How does position hierarchy determine the line manager?
When assignment manager synchronization is based on the HCM position hierarchy, Oracle describes the incumbent in the parent position as the line manager for a new assignment in the child position. The hierarchy therefore supplies a relationship between positions; the incumbent occupying the parent position supplies the person used as manager.
A parent position without an incumbent is an important exception. Depending on the workflow and configuration, direct reports may need to be reassigned manually. A parent-position change can also affect existing assignment data, so do not assume editing a relationship changes only future assignments. Oracle: How Line Managers Are Synchronized Using Position Hierarchy
How to set up a position hierarchy in Oracle HCM
Use this as a planning sequence rather than a universal migration recipe; tenant configuration and release can affect the available options and navigation.
Recommended Free Tools
- Decide the intended use. Confirm that the organization needs parent-position relationships and decide whether assignment manager synchronization from the hierarchy is in scope. Oracle documents an important constraint: the HCM position hierarchy configuration cannot be changed while line manager synchronization is based on that hierarchy. Assess that design decision before rollout.
- Enable the feature. In Setup and Maintenance, open Manage Enterprise HCM Information and enable HCM position hierarchy. Oracle documents this as the prerequisite for specifying parent positions on position pages. Verify the exact label and availability in your tenant’s release. Oracle: HCM Position Hierarchy
- Create or edit positions. In Workforce Structures, set the intended parent position on each applicable position. Check parent-child relationships before using them to drive assignment managers.
- Configure position synchronization. Set synchronization at the enterprise or legal-entity level, select the attributes to synchronize, and decide whether assignment overrides are allowed. A legal-employer setting takes precedence over an enterprise setting when both are configured. Depending on the setup, assignments may need Synchronize from Position set to
Y. Oracle: Set Up Position Synchronization - Plan assignment updates. Determine how and when to run Synchronize Person Assignments from Position so relevant changes to assignments are applied. For manager synchronization, Oracle recommends scheduling the process daily.
- If loading with HDL, validate the data and load sequence. Use the current release’s object template and verify effective dates, keys, and referenced positions before loading. All positions referenced by hierarchy rows must already exist in the target environment.
- Decide how flattening will run. Oracle says hierarchy changes made in the UI or loaded through HDL trigger flattening automatically. Its HDL documentation also describes a
SETinstruction to prevent automatic flattening during a hierarchy load. Follow current release documentation for the exact syntax and sequencing.
Position synchronization can cover attributes such as department, job, location, grade, manager, and working hours, depending on configuration. The attributes and inheritance behavior vary by operation; an HDL assignment load should not be assumed to synchronize every hierarchy-related value immediately. Oracle: Position Synchronization · Oracle: How Assignment Values Are Inherited from Position
How to load position hierarchy using HDL
Oracle’s examples use the PositionHierarchy object in a file named PositionHierarchy.dat. They show both source-key and user-key approaches. In either case, the referenced positions must exist in the target environment before the hierarchy rows are loaded. Oracle: Examples of Loading HCM Position Hierarchies
Choose and validate the key format
- Source keys: Oracle’s example includes source-system fields and parent and child position source IDs.
- User keys: The example identifies parent and child positions using business unit names and position codes.
- Effective dates: The examples include effective start and end dates and use
MERGErows. The sample historical start dates and end date4712-12-31illustrate date-effective records; they are not a universal date strategy for production.
Before building a production load, reconcile the keys and effective dates with your source data, confirm that each referenced position exists in the target, and check the current object template and HDL documentation for your Oracle release. Oracle: Examples of Loading HCM Position Hierarchies
Control flattening and plan the sequence
Hierarchy updates can trigger flattening automatically, including when the relationship is loaded with HDL. If the load requires flattening to be controlled, Oracle documents a SET instruction for preventing the automatic run. The exact instruction and load sequencing are release-sensitive, so use the current Oracle HDL documentation rather than copying an unverified sample.
What must happen after hierarchy changes?
Loading or editing parent-position relationships does not, by itself, guarantee that all affected assignment values have been updated. Oracle documents the Synchronize Person Assignments from Position process for applying relevant changes to assignments. It covers changes related to position synchronization, past- or future-dated hierarchy changes, and HDL-loaded position data. Schedule it regularly; Oracle recommends daily scheduling when managers are synchronized. Oracle: Synchronize Person Assignment from Position Process
The process has a Past Period to Be Considered in Days parameter, whose documented default is 30 days. That is a process default, not an instruction to use a 30-day lookback for every load: Oracle notes that the process can detect effective dates and last-updated dates. Choose the parameter based on the process behavior and the timing of the changes being applied.
Assignment effects can involve current, future, or past effective dates. Review the affected assignments and your synchronization configuration rather than assuming a hierarchy edit is limited to future records. Also account for the parent-without-incumbent case, where manual reassignment may be required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
