Oracle HCM Position Hierarchy: How Parent Positions, Setup, and HDL Work

Oracle HCM position hierarchy is a set of parent-child relationships between positions. Enable the feature, assign each position its intended parent, and—if you want those relationships to drive assignment managers—configure position synchronization and run the synchronization process. For bulk relationship loads, Oracle HDL uses the PositionHierarchy object in PositionHierarchy.dat; the referenced positions must already exist.

A position hierarchy is not the same thing as a position tree. They are separate Oracle HCM structures with different purposes, so choose the one that matches the task before you configure or load data.

#	Preview	Product	Price
1		Oracle Fusion HCM Consultant Cheat Sheet: Core HR, Payroll, Recruiting, Talent Management, Security,...	$15.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

What is Oracle HCM position hierarchy?

Oracle describes it simply: “Position hierarchy defines positions’ relationships.” In practice, each position can have a parent position—the next position up in this relationship structure. Once HCM position hierarchy is enabled, administrators can specify a parent while creating or editing a position. Oracle documents this structure as one basis for synchronizing assignment line managers. Oracle’s HCM Position Hierarchy documentation explains the feature; consult the documentation for your tenant’s release for current options and navigation.

HCM position hierarchy versus position tree

These structures are not interchangeable just because both represent hierarchy. Use parent-position relationships when the requirement is to connect positions and potentially synchronize assignment managers. Use a position tree when the requirement calls for a tree structure, such as a planning or security use case.

#1 Best Overall

Oracle Fusion HCM Consultant Cheat Sheet: Core HR, Payroll, Recruiting, Talent Management, Security, Integrations, Reporting, Fast Formula, HDL, REST ... (Oracle Fusion cloud visual guide)

$15.99

Buy on Amazon

How do I set up a position hierarchy in Oracle HCM?

First decide whether the organization needs parent-position relationships and whether assignment manager synchronization should use them. Manager synchronization is a consequential configuration choice: Oracle says the HCM position hierarchy configuration cannot be changed while line manager synchronization is based on that hierarchy. Oracle describes correction options for past-dated configuration, but this should not be treated as a routine way to reverse a design decision. Review the current release documentation before rollout.

1. Enable the feature. In Setup and Maintenance, open Manage Enterprise HCM Information and enable HCM position hierarchy. Oracle identifies this as the prerequisite for specifying parent positions on position pages. Verify the task and available settings in your tenant’s release: HCM Position Hierarchy.
2. Set the parent positions. In Workforce Structures, create or edit positions and assign the intended parent position. Check the relationships before using them to drive managers; a mistaken parent can affect more than the visual structure.
3. Configure position synchronization if needed. At the enterprise or legal-entity level, select which position attributes should synchronize and determine whether assignment overrides are allowed. A legal-employer configuration takes precedence over an enterprise configuration when both apply. See Oracle’s Set Up Position Synchronization guidance.
4. Decide which assignments participate. Depending on the setup, assignments may need Synchronize from Position set to Y. Confirm the relevant assignment population and attributes rather than assuming every assignment is automatically governed by the hierarchy.
5. Plan assignment synchronization. Run Synchronize Person Assignments from Position when required to apply position changes to affected assignments. Oracle recommends scheduling the process regularly and recommends daily scheduling when synchronizing managers. See Synchronize Person Assignment from Position Process.

This is a practical sequence, not a claim that every implementation or migration follows an identical plan. Navigation labels, options, and behavior can vary by Oracle release and tenant configuration.

How does position hierarchy determine the line manager?

When assignment manager synchronization is based on HCM position hierarchy, the incumbent in the parent position supplies the line manager for a new assignment. The relationship is position-to-position: the parent position is not itself a person, and the manager value depends on who occupies that parent position. Oracle outlines this behavior in How Line Managers Are Synchronized Using Position Hierarchy.

If a parent position has no incumbent, a line manager may not be available from that relationship. Depending on the workflow and configuration, users may need to assign direct reports manually. Confirm the behavior for the specific assignment flow and tenant settings.

Changing a parent relationship or position can affect current, future, or past-dated assignment data; do not assume a hierarchy edit changes only future assignments. The Synchronize Person Assignments from Position process handles relevant position-related assignment updates, including changes involving hierarchy effective dates and HDL-loaded position data. Its effective-date and last-updated-date logic matters when selecting its parameters. Oracle documents a default of 30 days for Past Period to Be Considered in Days; that is a process default, not a universal lookback recommendation or a rule that every backdated load needs a matching number of days. Follow the process documentation for the data and dates you are processing.

How do I load position hierarchy using HDL?

Oracle’s HDL examples use the PositionHierarchy object in PositionHierarchy.dat. The examples show both source-key and user-key formats, effective dates, and MERGE rows. Critically, every referenced position must already exist in the target environment before its hierarchy relationship is loaded. See Oracle’s Examples of Loading HCM Position Hierarchies and validate the object template and attributes against the documentation for your release.

Choose source keys or user keys

• Source-key example: The sample identifies the PositionHierarchy object, source-system fields, effective start and end dates, and parent and child position source IDs.
• User-key example: The sample identifies the parent and child using business-unit names and position codes.

Use the key type that matches the identifiers maintained in your source data and target environment. Do not copy the sample’s historical effective starts or its end date of 4712-12-31 as universal production dates: they illustrate date-effective records, not a recommended date strategy. Validate effective dates, source keys, and current HDL attributes with your implementation data and Oracle’s release-specific guidance.

Plan hierarchy flattening during the load

Oracle says hierarchy changes made in the UI or loaded through HDL can trigger flattening automatically. Its HDL documentation also describes a SET instruction to prevent automatic flattening during a hierarchy load. Treat this as a load-control decision: determine whether flattening should run automatically or be deliberately controlled, and follow Oracle’s current documentation for the exact syntax and sequencing. Do not infer a production load sequence from a sample file alone.

What else must happen after a hierarchy change?

Loading or editing parent relationships does not by itself guarantee that affected assignments immediately show the intended manager or other synchronized position values. Position synchronization can cover attributes such as department, job, location, grade, manager, working hours, and others, depending on setup. Which values inherit—and when—depends on configuration and the operation used. Oracle’s inheritance guidance distinguishes responsive employment flows, HDL/HSDL, REST, and the Synchronize Person Assignment from Position process; an HDL assignment load should not be assumed to synchronize every hierarchy-related value immediately.

• Confirm whether position synchronization is configured at enterprise or legal-employer level and account for legal-employer precedence.
• Confirm the assignments’ Synchronize from Position setting where applicable and the configured attribute list and override behavior.
• Run or schedule Synchronize Person Assignments from Position to apply relevant position changes. For manager synchronization, Oracle recommends a daily schedule.
• Check effective dates and process parameters against the affected data; the process considers effective and last-updated dates.

Oracle’s relevant guidance includes Position Synchronization, How Assignment Values Are Inherited from Position, and Synchronize Person Assignment from Position Process. The links lead to Oracle’s documentation site; use the documentation selector or your tenant’s release-specific library to verify the current page and settings.

Quick Recap

Bestseller No. 1

Oracle Fusion HCM Consultant Cheat Sheet: Core HR, Payroll, Recruiting, Talent Management, Security, Integrations, Reporting, Fast Formula, HDL, REST ... (Oracle Fusion cloud visual guide)

$15.99

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.