Search Results per_position_structures




Overview
Explore in AI Chat

Overview

The PER_POSITION_STRUCTURES table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically for releases 12.1.1 and 12.2.2. It serves as the master repository for defining and storing the names of position hierarchy structures. These structures are fundamental to modeling an organization's reporting relationships and chains of command based on positions, as distinct from organization-based hierarchies. The table acts as a header, defining the overall hierarchy, while its related objects, such as PER_POS_STRUCTURE_VERSIONS, manage the specific hierarchical relationships and their effective-dated changes. Its role is critical for security profiles, position-based reporting, and workflow routing that depends on the position hierarchy.

Key Information Stored

The table primarily stores metadata that uniquely identifies each position hierarchy within a business group. Its key columns, as defined by the primary and unique keys, are central to its function. The POSITION_STRUCTURE_ID is the system-generated primary key and unique identifier for each hierarchy definition. The NAME column stores the user-defined, descriptive title of the position hierarchy (e.g., "Management Reporting Line" or "Project Authority Structure"). The BUSINESS_GROUP_ID is a mandatory foreign key linking the structure to a specific HR business group in the HR_ALL_ORGANIZATION_UNITS table, enforcing data security and partitioning. This combination of NAME and BUSINESS_GROUP_ID is enforced as a unique key (PER_POSITION_STRUCTURES_UK2), preventing duplicate hierarchy names within a single business group.

Common Use Cases and Queries

This table is primarily referenced in administrative setups, security configurations, and hierarchical reporting. A common use case is retrieving a list of all defined position hierarchies for a business group to configure a security profile or a workflow routing rule. For example, an HR administrator might run a query to audit all structures. Sample SQL to list active hierarchies would join with the business group table for clarity:

  • SELECT pps.NAME, hou.NAME BUSINESS_GROUP
  • FROM hr.per_position_structures pps,
  • hr.hr_all_organization_units hou
  • WHERE pps.business_group_id = hou.organization_id
  • AND hou.business_group_id = &business_group;

Another critical use case involves troubleshooting or reporting on security profiles (PER_SECURITY_PROFILES) or position hierarchy versions, where queries would join PER_POSITION_STRUCTURES to these related tables using POSITION_STRUCTURE_ID.

Related Objects

As indicated by the foreign key relationships, PER_POSITION_STRUCTURES is a parent table with several key dependencies. The most direct child is the PER_POS_STRUCTURE_VERSIONS table, which holds the effective-dated hierarchy definitions (the actual parent-child position links) for each structure. It is also referenced by PER_SECURITY_PROFILES to define position-based security access. Furthermore, the PQH_ROUTING_CATEGORIES table in the Position Management (PQH) module references it to establish approval routing rules based on position hierarchies. The table's link to HR_ALL_ORGANIZATION_UNITS via BUSINESS_GROUP_ID anchors it within the correct organizational and security context.