Search Results per_career_path_elements




Overview
Explore in AI Chat

Overview

The PER_CAREER_PATH_ELEMENTS table is a core Oracle Human Resources (PER) object that stores the constituent elements of career progression paths in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a directed progression relationship between a parent job and a subordinate job within a named career path, enabling organizations to model structured job ladders and succession-oriented advancement routes. The table resides in the HR schema and is central to career development and succession planning functionality delivered through Oracle HRMS.

From a Data Vault modeling perspective, the mined foreign key structure suggests classifying PER_CAREER_PATH_ELEMENTS as a link table. The heuristic reflects that its principal role is to associate independent business entities — career paths, parent jobs, subordinate jobs, and a business group — rather than to serve as a standalone hub or descriptive satellite. This classification is offered as a modeling suggestion and should be validated against the enterprise's own warehouse design conventions.

Key Information Stored

The table is documented with 14 columns. The most significant are summarized below.

Together, the parent and subordinate job identifiers plus the career path identifier form the meaningful business combination; however, no alternate unique index beyond the surrogate primary key is documented.

Common Use Cases and Queries

Typical scenarios include building career ladder reports, validating progression eligibility, and analyzing succession coverage. A representative join returns each element with its path, business group, and both job names:

  • Reporting all parent-to-subordinate job pairs grouped by CAREER_PATH_ID.
  • Identifying all subordinate jobs reachable from a given parent job.
  • Reconciling career paths against current job definitions for obsolete job references.
  • Auditing rows changed after a given date using LAST_UPDATE_DATE or PROGRAM_UPDATE_DATE.

A sample query pattern is: select CAREER_PATH_ID, PARENT_JOB_ID, SUBORDINATE_JOB_ID from PER_CAREER_PATH_ELEMENTS joined to PER_CAREER_PATHS on CAREER_PATH_ID and to PER_JOBS twice — once on PARENT_JOB_ID and once on SUBORDINATE_JOB_ID — always constraining on BUSINESS_GROUP_ID to preserve data isolation.

Related Objects

  • PER_CAREER_PATHS — Joined on CAREER_PATH_ID; defines the parent career path header.
  • PER_JOBS — Joined twice via PARENT_JOB_ID and SUBORDINATE_JOB_ID; supplies job names and validity.
  • HR_ALL_ORGANIZATION_UNITS — Joined on BUSINESS_GROUP_ID; provides business group context.
  • Standard PER audit and concurrent request tables (e.g., FND_CONCURRENT_REQUESTS) referenced through REQUEST_ID for operational tracing.
  • Career-path and succession planning views and APIs in HRMS that consume these elements to render progression hierarchies and eligibility results.