Results for “pa_competences_v”

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

Overview

PA_COMPETENCES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. The view flattens the relationship between a defined competence and its parent competence definition, exposing a single denormalized row per competence along with up to thirty descriptive flexfield segments. In Oracle EBS 12.1.1 and 12.2.2 this view is registered as VALID and is intended for read-only consumption by reports, concurrent programs, and external integrations that need competence data without navigating the parent-child join themselves.

Competences in Oracle Projects represent the skills, attributes, or qualifiers that an organization tracks against people, assignments, and resource searches. A competence is an instance of a competence definition; the definition supplies the structural identity and flexfield context, while the competence supplies the actual named value, its alias, description, and effective dating. PA_COMPETENCES_V presents that combined picture, which is why it is frequently surfaced in Oracle Projects reporting and in the resource management areas that consume competence data.

Underlying Base Objects

The view text is a two-table equijoin over two APPS synonyms:

• PER_COMPETENCES (alias COMP) — the transactional competence entity, supplying COMPETENCE_ID, COMPETENCE_ALIAS, NAME, DESCRIPTION, DATE_FROM, DATE_TO, and the foreign key COMPETENCE_DEFINITION_ID.
• PER_COMPETENCE_DEFINITIONS (alias COMP_DEF) — the definition entity that owns the thirty SEGMENTn flexfield columns. It is joined on COMPETENCE_DEFINITION_ID.

The join is an inner join: COMP.COMPETENCE_DEFINITION_ID = COMP_DEF.COMPETENCE_DEFINITION_ID. A competence row that lacks a matching definition row is therefore not returned. Although the underlying objects reside in the PER (Human Resources) product area, the view is delivered and owned under APPS in the PA product context, reflecting its use in Oracle Projects resource and competence reporting.

Key Columns

• COMPETENCE_ID — Primary key of the competence instance; the safest join key back to PER_COMPETENCES.
• COMPETENCE_ALIAS — Short user-facing code or alias for the competence.
• COMPETENCE_NAME — The descriptive name of the competence (sourced from PER_COMPETENCES.NAME).
• DESCRIPTION — Free-text description of the competence.
• DATE_FROM / DATE_TO — Effective date range of the competence, used for date-filtered reporting.
• SEGMENT1 … SEGMENT30 — Descriptive flexfield segments inherited from PER_COMPETENCE_DEFINITIONS, providing the configurable classification attributes of the definition.

Common Use Cases and Queries

The view is used to list competences with their segment classifications, to feed resource-search and qualification reports, and to support integration extracts that require a flat, joined structure.

Listing active competences with segment values:

SELECT competence_id, competence_alias, competence_name,
       date_from, date_to, segment1, segment2
  FROM   apps.pa_competences_v
 WHERE  SYSDATE BETWEEN NVL(date_from, SYSDATE)
                    AND NVL(date_to, SYSDATE);

Joining to assignments or resource records by COMPETENCE_ID provides the competence name and flexfield context in a single pass. Because the view is owned by APPS and is a simple join without aggregation, it performs well for lookup-style reporting, though large extracts should still filter on DATE_FROM/DATE_TO to limit the result set.