Search Results per_comp_element_outcomes_pk

Overview

PER_COMP_ELEMENT_OUTCOMES is an Oracle E-Business Suite Human Resources (PER) table that stores the outcomes achieved towards a given Competency. In the Oracle EBS 12.1.1 and 12.2.2 data models, competencies are decomposed into finer building blocks called competence elements, and each element can be measured against a set of defined outcomes. This table is the associative structure that binds a specific competence element to a specific outcome, capturing the many-to-many relationship between the two parent entities.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure suggests that PER_COMP_ELEMENT_OUTCOMES behaves as a link table. It resolves the relationship between PER_COMPETENCE_ELEMENTS and PER_COMPETENCE_OUTCOMES, while also carrying descriptive and audit attributes that would, in a strict Data Vault model, typically be split into an adjacent satellite. This dual nature — foreign-key association plus effective-dating and descriptive columns — is characteristic of EBS intersection tables that also serve as operational entities.

Key Information Stored

The table is owned by the HR schema and, per the documented 12.2.2 physical schema, contains 53 columns. The central columns are:

• COMP_ELEMENT_OUTCOME_ID — the surrogate primary key, uniquely enforcing the PER_COMP_ELEMENT_OUTCOMES_PK constraint for each outcome association record.
• COMPETENCE_ELEMENT_ID — foreign key to PER_COMPETENCE_ELEMENTS, identifying the competence element being measured.
• OUTCOME_ID — foreign key to PER_COMPETENCE_OUTCOMES, identifying the outcome achieved.
• DATE_FROM and DATE_TO — effective dating that allows the association to be time-bounded, supporting historical accuracy.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard Oracle descriptive flexfield (DFF) columns for customer-specific extensions.
• INFORMATION_CATEGORY and INFORMATION1 through INFORMATION20 — the standard Oracle "information" flexfield columns used for additional context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the WHO audit columns applied consistently across EBS tables.

The primary key COMP_ELEMENT_OUTCOME_ID is the sole documented unique index and therefore the only documented business-key candidate. The pairing of COMPETENCE_ELEMENT_ID with OUTCOME_ID functions as the meaningful business relationship, though the metadata documents uniqueness only on the surrogate key.

Common Use Cases and Queries

Typical usage centers on competency assessment and reporting. Frequently encountered patterns include:

• Retrieving all outcomes associated with a competence element:

SELECT c.COMP_ELEMENT_OUTCOME_ID, c.COMPETENCE_ELEMENT_ID, c.OUTCOME_ID, c.DATE_FROM, c.DATE_TO FROM PER_COMP_ELEMENT_OUTCOMES c WHERE c.COMPETENCE_ELEMENT_ID = :element_id;

• Resolving outcomes to their descriptions by joining to PER_COMPETENCE_OUTCOMES, and elements to their parent competencies via PER_COMPETENCE_ELEMENTS.
• Historical analysis using DATE_FROM/DATE_TO to determine which outcome definitions were active during a given assessment period.
• Extract and load processes into enterprise reporting or data warehouse platforms, where the DFF columns (ATTRIBUTE1–ATTRIBUTE20) often need context-sensitive decoding.
• Data migration or validation scripts verifying that no orphan outcome references exist against the parent tables.

Related Objects

The most significant related objects, grounded in the documented foreign-key relationships, are:

• PER_COMPETENCE_ELEMENTS — joined on PER_COMP_ELEMENT_OUTCOMES.COMPETENCE_ELEMENT_ID = PER_COMPETENCE_ELEMENTS.COMPETENCE_ELEMENT_ID.
• PER_COMPETENCE_OUTCOMES — joined on PER_COMP_ELEMENT_OUTCOMES.OUTCOME_ID = PER_COMPETENCE_OUTCOMES.OUTCOME_ID.
• Competency definition tables (such as PER_COMPETENCES) reached indirectly through PER_COMPETENCE_ELEMENTS, providing the top-level competency context.
• PER competency assessment and profile tables that consume element/outcome combinations when evaluating employee competence.
• Standard EBS flexfield and audit infrastructure referenced indirectly through the ATTRIBUTE_CATEGORY, ATTRIBUTE1–20, and WHO columns.

Together these relationships position PER_COMP_ELEMENT_OUTCOMES as a crucial junction within the Human Resources competency model, linking structured element definitions to the measurable outcomes used throughout competency assessment processes.