Search Results per_comp_element_outcomes_fk1

Overview

HR.PER_COMP_ELEMENT_OUTCOMES is a transactional table in the Oracle E-Business Suite Human Resources (HR) schema that records the outcomes achieved against a given competence element. In Oracle EBS 12.1.1 and 12.2.2, competencies are modeled as a hierarchy of competence elements (skills, abilities, knowledge, and behaviors), and each element may be associated with one or more measurable outcomes. This table stores the intersection between a competence element and the outcome that has been attained, recording validity periods and descriptive flexfield context.

The table is registered under FND Design Data as PER.PER_COMP_ELEMENT_OUTCOMES, resides in the APPS_TS_TX_DATA tablespace, and holds 53 documented columns in the 12.2.2 physical schema. It is a VALID, production-supported object owned by the HR schema.

From a Data Vault modeling perspective, the mined heuristic classification places this table as a link. It resolves a many-to-many relationship between competence elements and competence outcomes, with COMP_ELEMENT_OUTCOME_ID acting as the surrogate primary key and the entity pair COMPETENCE_ELEMENT_ID and OUTCOME_ID forming the natural business relationship. This classification is a modeling suggestion, not a prescriptive data-vault design.

Key Information Stored

• COMP_ELEMENT_OUTCOME_ID — System-generated surrogate primary key (NUMBER(15)). Enforced by unique index PER_COMP_ELEMENT_OUTCOMES_PK. No alternate unique business-key index is documented, so this is the sole documented unique key.
• COMPETENCE_ELEMENT_ID — Foreign key to PER_COMPETENCE_ELEMENTS, identifying the competence element for which an outcome is recorded. Indexed by PER_COMP_ELEMENT_OUTCOMES_FK1.
• OUTCOME_ID — Foreign key to PER_COMPETENCE_OUTCOMES, identifying the specific outcome attained. Indexed by PER_COMP_ELEMENT_OUTCOMES_FK2, the index referenced in the user's search.
• DATE_FROM and DATE_TO — Date-effective validity window controlling when the outcome association is active.
• OBJECT_VERSION_NUMBER — Optimistic locking column; increments by one on each row update.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield structure and column set for client-specific extension data.
• INFORMATION_CATEGORY and INFORMATION1–INFORMATION20 — Authoring/occupation information flexfield columns documented in the 12.2.2 physical schema.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY for standard WHO tracking.

Common Use Cases and Queries

Typical reporting scenarios include listing all outcomes defined for a competence element, tracing which outcomes a competency uses, and joining to outcome descriptions for competency-based assessment reporting. Because the table is date-effective, queries should apply a current-date filter for point-in-time results.

Sample pattern — outcomes for a competence element:

• SELECT ceo.COMP_ELEMENT_OUTCOME_ID, ceo.OUTCOME_ID, ceo.DATE_FROM, ceo.DATE_TO
• FROM PER_COMP_ELEMENT_OUTCOMES ceo
• WHERE ceo.COMPETENCE_ELEMENT_ID = :element_id
• AND TRUNC(SYSDATE) BETWEEN ceo.DATE_FROM AND NVL(ceo.DATE_TO, TRUNC(SYSDATE))

Because OUTCOME_ID is indexed via PER_COMP_ELEMENT_OUTCOMES_FK2, reverse lookups — finding every competence element that references a given outcome — are also efficient, which supports impact analysis before an outcome is retired or redefined.

Related Objects

• PER_COMPETENCE_ELEMENTS — Parent of COMPETENCE_ELEMENT_ID; defines the competence elements to which outcomes attach.
• PER_COMPETENCE_OUTCOMES — Parent of OUTCOME_ID; provides the outcome definitions (name, description) joined for reporting.
• PER_COMP_ELEMENT_OUTCOMES_PK — Unique index on COMP_ELEMENT_OUTCOME_ID.
• PER_COMP_ELEMENT_OUTCOMES_FK1 — Non-unique index on COMPETENCE_ELEMENT_ID.
• PER_COMP_ELEMENT_OUTCOMES_FK2 — Non-unique index on OUTCOME_ID; the subject of the user's search.
• FND Design Data: PER.PER_COMP_ELEMENT_OUTCOMES — Registration metadata controlling the object's application ownership and flexfield definitions.

These relationships establish the table as a central link in the Oracle HRMS competency model, connecting element definitions to measurable outcomes used throughout competency assessment and profile matching.