Results for “per_personal_scorecards_pk”

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

Overview

PER_PERSONAL_SCORECARDS is an Oracle E-Business Suite Human Resources (PER) table that stores personal scorecards. Each row represents a single worker's objectives for one particular performance management plan, providing the goal setting, performance review, and scoring basis used by the Oracle Performance Management product. The table resides in the HR schema and is documented as valid across Oracle EBS 12.1.1 and 12.2.2.

The physical schema comprises 52 columns and is uniquely identified by the primary key constraint PER_PERSONAL_SCORECARDS_PK, which is enforced on the SCORECARD_ID column. Under the heuristic Data Vault classification mined from the foreign-key structure, this object is treated as standalone, suggesting it be modeled as an independent hub or satellite rather than as a dependent link. This classification should be regarded as a modeling suggestion rather than a prescriptive rule, since the ETRM relationship mining did not surface durable foreign-key dependencies for this table.

Key Information Stored

The most significant columns and their roles are as follows:

• SCORECARD_ID — the surrogate primary key and sole documented unique index (PER_PERSONAL_SCORECARDS_PK); a system-generated identifier for each scorecard record.
• SCORECARD_NAME — the descriptive name assigned to the personal scorecard.
• PERSON_ID — the worker to whom the scorecard belongs; the primary business reference for the record.
• ASSIGNMENT_ID — the assignment context under which the objectives are held.
• PLAN_ID — the performance management plan the scorecard is associated with, linking objectives to a specific plan instance.
• START_DATE and END_DATE — the effective period covered by the scorecard.
• STATUS_CODE — the lifecycle state of the scorecard (for example, draft, active, or completed).
• ELIGIBILITY_STATUS and ELIGIBILITY_EVAL_DATE — eligibility determination and the date it was evaluated.
• OBJ_SETTING_DEADLINE — the deadline by which objectives must be set.
• SUPERVISOR_ID and SUPERVISOR_ASSIGNMENT_ID — the reviewing supervisor and associated assignment.
• CREATOR_TYPE — indicates how the scorecard was created.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework for concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) segment set, available for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit WHO columns, plus ERROR_LOG for capturing processing errors.

Note that SCORECARD_ID is the surrogate key; the documented metadata does not expose a separate business-key unique index beyond the primary key.

Common Use Cases and Queries

Typical usage centers on retrieving a worker's scorecards for a given plan, reporting objective coverage, and monitoring eligibility and deadline compliance. A representative query joining the person context might read:

• SELECT sc.scorecard_id, sc.scorecard_name, sc.status_code, sc.start_date, sc.end_date FROM per_personal_scorecards sc WHERE sc.person_id = :p_person_id AND sc.plan_id = :p_plan_id ORDER BY sc.start_date DESC;
• SELECT sc.scorecard_id, sc.person_id, sc.supervisor_id, sc.obj_setting_deadline FROM per_personal_scorecards sc WHERE sc.obj_setting_deadline < SYSDATE AND sc.status_code = 'DRAFT';
• SELECT sc.eligibility_status, COUNT(*) FROM per_personal_scorecards sc GROUP BY sc.eligibility_status;

Reporting use cases include supervisor dashboards of direct-report scorecards (filtering on SUPERVISOR_ID and SUPERVISOR_ASSIGNMENT_ID), audit extracts of scorecard activity over CREATION_DATE and LAST_UPDATE_DATE, and DFF-based reporting via ATTRIBUTE_CATEGORY and ATTRIBUTE1–30.

Related Objects

The heuristic relationship classification lists this object as standalone, so durable foreign keys are not documented. The following objects are nonetheless significant because they reference or depend on this table through its key columns:

• PER_PERFORMANCE_PLANS — the performance management plan referenced by PLAN_ID.
• PER_ALL_PEOPLE_F — the person referenced by PERSON_ID.
• PER_ALL_ASSIGNMENTS_F — the assignment referenced by ASSIGNMENT_ID and SUPERVISOR_ASSIGNMENT_ID.
• PER_PERSONAL_SCORECARD_ITEMS — child objective rows keyed by SCORECARD_ID.
• PER_SCORE_ITEMS / PER_SCORES — scoring records linked to the scorecard.
• PER_SCORECARD_REVIEWS — review rows associated with the scorecard.

Because the ETRM mining did not surface formal FK constraints, joins to these objects should be validated against the specific implementation.