Oracle HCM Position Hierarchy Explained: A Beginner's Guide to Structure, Setup, and HDL

Introduction

I recently came across the concept of Position Hierarchies in Oracle HCM and, at first, I wasn't entirely sure why they were needed. After all, Oracle HCM already has managers and reporting relationships. If employees can report to managers, why do we need another hierarchy?

As I dug deeper, I realized that Position Hierarchies solve a different business problem. They focus on the organizational structure itself rather than the individuals occupying roles. In this article, I'll explain what Position Hierarchies are, why organizations use them, what setup is required, and how they can be loaded using HDL.

Instead of saying: Employee A reports to Employee B, Position Hierarchy says: Position A reports to Position B.

This allows organizations to maintain a stable structure even when employees leave or move between positions.

What Is a Position?

A Position represents a specific role or slot within an organization. A worker may be assigned to a position, but the position itself exists independently of any individual employee.

For example: Even if the Finance Manager leaves the company, the position remains available for a future employee.

What Is a Position Hierarchy?

A Position Hierarchy defines the parent-child relationships between positions.

The hierarchy is built using positions rather than workers. Workers simply occupy those positions.

Why Do Organizations Use Position Hierarchies?

Position Hierarchies provide several advantages:

• Workforce Planning - Organizations can easily visualize their organizational structure and future growth plans.
• Vacancy Management - The reporting structure remains intact even when positions become vacant.
• Approval Routing - Approvals can be routed through the position structure rather than relying solely on manager relationships.
• Security - Certain security and data access models can leverage hierarchy information.
• Headcount Management - Organizations can track authorized positions separately from actual employees.

Position Hierarchy vs Manager Hierarchy

• Manager Hierarchy - The hierarchy changes when people move or leave.
• Position Hierarchy - The hierarchy remains unchanged even when different employees occupy these positions.

Prerequisites

Before building a Position Hierarchy, several foundational configurations should already exist.

1. Enterprise Structure Setup

The organization should already have the following configured within Oracle HCM:

• Legal Employers
• Business Units
• Departments
• Locations

2. Enable Position Management

Position Management should be enabled.

Navigation: Setup and Maintenance → Manage Enterprise HCM Information

Enable: Use Position Management

This allows positions to become a central part of workforce management.

3. Create Positions

Positions must exist before they can participate in a hierarchy.

Configuration Steps

Step 1: Create Positions

Navigation: My Client Groups → Workforce Structures → Positions

Create all required positions first.

Step 2: Define Parent Positions

When creating or updating a position, define its parent position.

Step 3: Build the Position Hierarchy

Oracle uses these parent-child relationships to construct the hierarchy.

Step 4: Run Hierarchy Processes

After large data loads or hierarchy updates, run the appropriate hierarchy-related processes so that reporting and approvals recognize the latest structure.

HDL Loads Required

In real implementations, organizations often create hundreds or thousands of positions. Because of this, HDL is commonly used.

• HDL Load 1: Positions - Create the positions.
• HDL Load 2: Parent Position Relationships - Include the parent position information.

A replacement worker can later occupy the position without requiring any changes to the organizational structure if a position was to become vacant.

This is one of the biggest advantages of Position Hierarchies.

Common Implementation Mistakes

Parent Positions Not Loaded First

A child position cannot reference a parent position that does not exist. Always create parent positions first.

Circular Hierarchies

Avoid configurations such as:

Position A → Position B
Position B → Position A

These relationships are invalid.

Assuming Vacancies Break the Hierarchy

A vacant position does not impact the hierarchy. The position remains part of the organizational structure.

Forgetting Hierarchy Processes

After significant hierarchy updates through HDL, hierarchy processes may need to be run to refresh reporting structures and approvals.

Final Thoughts

Position Hierarchies provide a powerful way to model organizational structures in Oracle HCM. Unlike Manager Hierarchies, they focus on positions rather than individuals, creating a stable framework that survives employee movement, promotions, transfers, and vacancies.

By enabling Position Management, creating positions, defining parent-child relationships, and loading structures through HDL, organizations can build a scalable workforce model that supports planning, security, approvals, and reporting.

The key concept to remember is simple:

• Manager Hierarchy = People report to people
• Position Hierarchy = Positions report to positions

Workers may come and go, but the organizational structure remains unchanged. That stability is what makes Position Hierarchies such a valuable feature in Oracle HCM.