Search Results per_perf_mgmt_plans_pk

Overview

PER_PERF_MGMT_PLANS is a core Human Resources table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the HR schema. It stores Performance Management Plans, which are configuration records that control and automate goal setting and the broader performance management lifecycle. Each row defines the time-period, the population of participants, and the process rules that govern an appraisal or objective-setting cycle.

Functionally, this object acts as the master definition header for a performance management initiative. When an HR administrator or line manager launches a performance cycle, the application reads a row in this table to determine who is enrolled, which hierarchy drives supervision, what method of evaluation applies, and the applicable deadlines.

The mined Data Vault classification for this table is standalone. This suggests that, from a purely referential standpoint, PER_PERF_MGMT_PLANS behaves as a hub-like anchor: it holds the enduring business identity of a plan (PLAN_ID) without being subordinated to another parent entity through a foreign key within its own schema. The absence of inbound classifying relationships supports treating it as an independent reference point in a dimensional or Data Vault model.

Key Information Stored

The table contains 70 documented columns. The following are the most significant for functional and reporting purposes:

• PLAN_ID — The surrogate primary key, enforced by the unique index PER_PERF_MGMT_PLANS_PK. Every dependent child record (enrollment, objectives, etc.) references this value.
• PLAN_NAME — The business-friendly identifier of the plan; a natural business-key candidate.
• ADMINISTRATOR_PERSON_ID — The person responsible for administering the plan.
• START_DATE / END_DATE — The active window of the plan, defining the performance period.
• STATUS_CODE — The lifecycle state of the plan (for example draft, active, or completed).
• HIERARCHY_TYPE_CODE — Determines whether the plan is driven by organization or position hierarchy.
• SUPERVISOR_ID / SUPERVISOR_ASSIGNMENT_ID — The top-level supervisor and assignment anchoring the plan.
• ORGANIZATION_STRUCTURE_ID / ORG_STRUCTURE_VERSION_ID / TOP_ORGANIZATION_ID — Organization hierarchy and version used to select participants.
• POSITION_STRUCTURE_ID / POS_STRUCTURE_VERSION_ID / TOP_POSITION_ID — Position-based equivalents of the hierarchy selection.
• HIERARCHY_LEVELS — How many levels downward from the top node are included.
• AUTOMATIC_ENROLLMENT_FLAG — Whether eligible workers are enrolled automatically.
• METHOD_CODE — The appraisal or objective method applied.
• OBJ_SETTING_START_DATE / OBJ_SETTING_DEADLINE — The objective-setting window for participants.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns present on this and virtually all EBS tables.

Common Use Cases and Queries

Typical scenarios include identifying active plans, resolving participants, and auditing plan configuration across periods. A common query lists currently active plans with their date windows:

• SELECT plan_id, plan_name, status_code, start_date, end_date FROM per_perf_mgmt_plans WHERE status_code = 'ACTIVE' AND SYSDATE BETWEEN start_date AND end_date;

Joining to the parent structure tables resolves which organization or position hierarchy a plan uses, which is essential for impact analysis before restructuring:

• SELECT p.plan_id, p.plan_name, p.hierarchy_type_code, o.org_structure_version_id FROM per_perf_mgmt_plans p, per_organization_structures o WHERE p.organization_structure_id = o.organization_structure_id;

Reporting use cases include enrollment forecasting, late-objective analysis against OBJ_SETTING_DEADLINE, and compliance reporting that demonstrates which population was evaluated and when. The attribute columns (ATTRIBUTE1 through ATTRIBUTE30) provide a standard descriptive-flexfield extension point for customer-specific reporting data.

Related Objects

The foreign keys documented for this table connect it to hierarchy definition tables, while dependent transaction tables reference its primary key:

• PER_ORGANIZATION_STRUCTURES — joined via ORGANIZATION_STRUCTURE_ID.
• PER_ORG_STRUCTURE_VERSIONS — joined via ORG_STRUCTURE_VERSION_ID.
• PER_POSITION_STRUCTURES — joined via POSITION_STRUCTURE_ID.
• PER_POS_STRUCTURE_VERSIONS — joined via POS_STRUCTURE_VERSION_ID.
• PER_ALL_PEOPLE_F — resolves ADMINISTRATOR_PERSON_ID and SUPERVISOR_ID to person names.
• Performance Management child objects (plan enrollment, objectives, and appraisal records) reference PLAN_ID and cascade depend on the plan header.

Note that PREVIOUS_PLAN_ID allows a plan to relate to a prior cycle, which is useful when tracing the evolution of performance management configuration across successive periods.