Results for “per_succession_planning”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_SUCCESSION_PLANNING is an Oracle Human Resources (PER) table that stores the record of a person's proposed succession to a position. In Oracle EBS 12.1.1 and 12.2.2, it sits at the heart of the Succession Planning functionality, capturing the association between a successor (an employee or applicant) and the position into which that individual may eventually move. Each row represents one succession plan entry: a named individual, a target position and job, a readiness assessment, and the business group within which the plan is valid.

The table is owned by the HR schema and is documented as VALID in the ETRM 12.2.2 schema, which lists 43 columns. Based on the heuristic Data Vault classification derived from its foreign key structure, PER_SUCCESSION_PLANNING is best modeled as a link table. It resolves relationships between independent business entities — a person, a successor person, a position, a job, and a business group — rather than acting as a standalone hub or a descriptive satellite.

Key Information Stored

The surrogate primary key is SUCCESSION_PLAN_ID, enforced by the PER_SUCCESSION_PLANNING_PK index. The documented business-key candidate is PER_SUCCESSION_PLANNING_UK1, which spans PERSON_ID, JOB_ID, POSITION_ID, SUCCESSEE_PERSON_ID, BUSINESS_GROUP_ID, and START_DATE — a composite that uniquely identifies a plan for a given successor, target position/job, and start date within a business group.

• SUCCESSION_PLAN_ID — surrogate primary key for the plan record.
• PERSON_ID — the person associated with the plan (typically the incumbent or planning owner).
• SUCCESSEE_PERSON_ID — the individual proposed as the successor.
• POSITION_ID — the target position being planned for (FK to PER_ALL_POSITIONS).
• JOB_ID — the job associated with the succession plan.
• BUSINESS_GROUP_ID — the business group context (FK to HR_ALL_ORGANIZATION_UNITS).
• START_DATE / END_DATE — effective dating for the plan.
• PLAN_STATUS — current state of the succession plan.
• READINESS_PERCENTAGE and PERFORMANCE — readiness and performance indicators for the successor.
• PERSON_RANK — ranking of the successor relative to others for the same position.
• AVAILABLE_FOR_PROMOTION — promotion eligibility flag.
• MANAGER_COMMENTS — free-text manager notes.
• OBJECT_VERSION_NUMBER and the ATTRIBUTE1–ATTRIBUTE20 flexfield columns — concurrency control and descriptive flexfield storage.

Common Use Cases and Queries

Typical reporting scenarios include listing successors for a given position, ranking candidates, and assessing readiness across an organization. A basic query joining to positions might read:

SELECT sp.SUCCESSEE_PERSON_ID, sp.POSITION_ID, sp.PERSON_RANK, sp.READINESS_PERCENTAGE
FROM PER_SUCCESSION_PLANNING sp
WHERE sp.POSITION_ID = :position_id
AND sp.PLAN_STATUS = 'ACTIVE';

To scope by business group and effective dates, filter on BUSINESS_GROUP_ID and START_DATE. Rank-based reporting orders by PERSON_RANK, while readiness dashboards aggregate READINESS_PERCENTAGE. The table also supports promotion-eligibility reports via AVAILABLE_FOR_PROMOTION.

Related Objects

• PER_ALL_POSITIONS — joined via PER_SUCCESSION_PLANNING.POSITION_ID.
• HR_ALL_ORGANIZATION_UNITS — joined via PER_SUCCESSION_PLANNING.BUSINESS_GROUP_ID for the business group.
• PER_ALL_PEOPLE_F — the standard person view for resolving PERSON_ID and SUCCESSEE_PERSON_ID.
• PER_JOBS — resolves JOB_ID.
• PER_SUCCESSION_PLANNING_PK / _UK1 — the indexes enforcing the surrogate and business keys.