Results for “per_competence_outcomes”

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

Overview

PER_COMPETENCE_OUTCOMES is a Human Resources (PER) module table that stores competence outcomes within the Oracle E-Business Suite competency management framework. In Oracle EBS 12.1.1 and 12.2.2, competencies are defined as measurable skills, behaviors, or knowledge areas required for jobs, positions, and individual development. A competence outcome represents a specific observable result or level of achievement associated with a parent competence, allowing organizations to decompose broad competencies into discrete, assessable outcomes that can be referenced during appraisals, gap analysis, and learning management.

The table resides in the HR schema and is documented as holding 55 columns in the 12.2.2 physical schema. Based on the heuristic Data Vault classification derived from its foreign key structure, PER_COMPETENCE_OUTCOMES is satellite-leaning: it carries descriptive attributes and depends on a parent entity (PER_COMPETENCES) for its core identity. This classification is offered as a modeling suggestion rather than a prescriptive design, since the table also serves as a parent for downstream outcome-element relationships.

Key Information Stored

The table is anchored by the surrogate primary key OUTCOME_ID, defined through the unique index PER_COMPETENCE_OUTCOMES_PK. Notable columns include:

• OUTCOME_ID – Surrogate primary key uniquely identifying each competence outcome record.
• COMPETENCE_ID – Foreign key to PER_COMPETENCES, establishing the parent competence to which the outcome belongs.
• NAME – Descriptive name of the outcome.
• OUTCOME_NUMBER – Sequencing or reference number for the outcome.
• ASSESSMENT_CRITERIA – Text describing the criteria against which the outcome is assessed.
• DATE_FROM / DATE_TO – Effective dating window controlling when the outcome is active.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the Oracle framework for concurrent update control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 – Descriptive flexfield (DFF) columns supporting organization-specific extensions.
• INFORMATION_CATEGORY and INFORMATION1–INFORMATION20 – Additional attribute segments often used for supplementary or localized information.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns tracking record creation and modification.

The business-key candidate is OUTCOME_ID via the unique index; there is no separate composite business key documented, so OUTCOME_ID serves both surrogate and functional identity.

Common Use Cases and Queries

Typical scenarios include retrieving all outcomes for a given competence, building assessment templates, and joining outcomes to element-level detail. A representative query follows:

• SELECT o.outcome_id, o.name, o.assessment_criteria FROM per_competence_outcomes o WHERE o.competence_id = :p_competence_id AND TRUNC(SYSDATE) BETWEEN o.date_from AND NVL(o.date_to, TRUNC(SYSDATE));
• Reporting competency-to-outcome hierarchies for gap analysis by joining PER_COMPETENCES to PER_COMPETENCE_OUTCOMES on COMPETENCE_ID.
• Extracting element-level scoring by joining PER_COMP_ELEMENT_OUTCOMES.OUTCOME_ID back to OUTCOME_ID.
• Date-effective filtering using DATE_FROM and DATE_TO for point-in-time reporting.
• DFF-driven reporting on ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 for customer-specific classifications.

Related Objects

• PER_COMPETENCES – Parent table; joined via PER_COMPETENCE_OUTCOMES.COMPETENCE_ID = PER_COMPETENCES.COMPETENCE_ID.
• PER_COMP_ELEMENT_OUTCOMES – Child/detail table referencing outcomes; joined via OUTCOME_ID.
• PER_COMPETENCE_OUTCOMES_PK – Primary key unique index on OUTCOME_ID.

Additional dependent objects include competency assessment and profile APIs that consume outcome data during evaluation, though the documented FK relationships above are the definitive join paths.