Search Results per_career_paths_uk2

Overview

PER_CAREER_PATHS is a Human Resources (PER) table in Oracle E-Business Suite that stores the definition of career paths associated with jobs. A career path represents a structured progression model — a named sequence of jobs, positions, or assignments — that describes how an employee may advance within an enterprise. The table is owned by the HR schema and carries a status of VALID in the ETRM repository for both 12.1.1 and 12.2.2.

Each row in PER_CAREER_PATHS acts as the header (parent) record for a career path. The individual steps or stages that make up the path are stored separately in the child table PER_CAREER_PATH_ELEMENTS, which references this table through the CAREER_PATH_ID column. Because the table holds descriptive attributes about the path entity and is referenced by a downstream detail table, its heuristic Data Vault classification is satellite-leaning. In a Data Vault model, this would suggest treating PER_CAREER_PATHS as a satellite attached to a career path hub, with the business grouping acting as an additional contextual key.

Key Information Stored

The table contains 34 documented columns. The most significant are:

• CAREER_PATH_ID — the surrogate primary key, enforced by PER_CAREER_PATHS_PK. This is the value propagated to child records in PER_CAREER_PATH_ELEMENTS.
• NAME and BUSINESS_GROUP_ID — together these form the business-key candidate, enforced by the unique index PER_CAREER_PATHS_UK2. The name of a career path must therefore be unique within its business group.
• BUSINESS_GROUP_ID — the foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the business group (organization) that owns the career path. This column is central to multi-organization partitioning and Row-Level Security in HR.
• COMMENTS — free-form descriptive text associated with the career path.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard Oracle EBS descriptive flexfield (DFF) columns, allowing customers to extend the table with their own contextual attributes without schema changes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — concurrent program context columns recording the batch process that last created or updated the record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit columns.

The additional unique index SYS_IL0000043332C00034$$ is an internal Oracle LOB/interMedia index (the SYS_IL naming convention), not a functional business key.

Common Use Cases and Queries

The principal reporting scenarios involve listing the career paths defined within a business group, retrieving the ordered elements for a given path, and joining the header to organizational and element detail.

A typical lookup uses the business-key candidate:

• SELECT career_path_id, name, comments FROM per_career_paths WHERE business_group_id = :p_bg_id AND name = :p_name;

To expand a path into its constituent stages, join to the child table on the surrogate key:

• SELECT cp.name, cpe.* FROM per_career_paths cp, per_career_path_elements cpe WHERE cp.career_path_id = cpe.career_path_id AND cp.business_group_id = :p_bg_id ORDER BY cp.name;

Analysts frequently join to HR_ALL_ORGANIZATION_UNITS to resolve the owning organization name, and use the DFF attribute columns to expose customer-defined segmentation. Because the table stores the header only, any query reporting the sequence or content of a career path must include PER_CAREER_PATH_ELEMENTS.

Related Objects

• PER_CAREER_PATH_ELEMENTS — the child table; joins on CAREER_PATH_ID and holds the individual path steps. This is the primary dependent object.
• HR_ALL_ORGANIZATION_UNITS — referenced by PER_CAREER_PATHS.BUSINESS_GROUP_ID; the source of business group and organization information.
• PER_JOBS / PER_ALL_POSITIONS — the job and position definitions that career path elements ultimately point to, used for end-to-end progression reporting.
• PER_BUSINESS_GROUPS — provides details on the business group key itself.
• The Career Path definition forms (PERWSJPR) and the associated FND concurrent programs recorded in REQUEST_ID are the standard application interfaces for maintaining this data.