Results for “pa_global_competences_lov_v”

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

Overview

PA_GLOBAL_COMPETENCES_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides within the PA (Projects) product family and is registered in ETRM as a VALID view whose stated purpose is to return all the global competences. A competence in Oracle EBS is a defined skill, attribute, or qualification (for example, a language, a technical certification, or a domain expertise) that can be associated with people and, in the Projects context, used to qualify resources against project requirements.

The view functions as a List of Values (LOV) source. Its name explicitly carries the LOV suffix, indicating that it is intended to populate a selection list in an Oracle Forms-based Projects screen or a related OAF page, rather than to serve as a general-purpose reporting entity. Its defining characteristic is the word global: the view deliberately restricts its output to competences that are not tied to any specific business group, and that have at least one associated competence level. This makes it a curated, ready-to-consume list of organization-wide competences suitable for validation and selection logic.

Because it is a view rather than a table, it stores no data of its own. All content is derived at query time from the underlying Human Resources competence structures, which means results always reflect the current state of competence definitions in the instance.

Underlying Base Objects

The view text is documented as follows:

SELECT COMP.COMPETENCE_ID, COMP.COMPETENCE_ALIAS, COMP.NAME, COMP.DESCRIPTION FROM PER_COMPETENCES COMP WHERE BUSINESS_GROUP_ID IS NULL AND EXISTS (SELECT COMPETENCE_ID FROM PER_COMPETENCE_LEVELS_V COMP_LVL WHERE COMP_LVL.COMPETENCE_ID = COMP.COMPETENCE_ID)

Two base objects are referenced, both resolved through synonyms and recorded in the documented metadata:

• PER_COMPETENCES (SYNONYM) — the core competence definition object, aliased as COMP. It supplies the competence identifier, alias, name, and description. The predicate BUSINESS_GROUP_ID IS NULL isolates the global, non-business-group-specific rows.
• PER_COMPETENCE_LEVELS_V (VIEW) — aliased as COMP_LVL, this view exposes competence levels. It is used only in a correlated EXISTS subquery to confirm that a given competence has at least one defined level; competences without levels are excluded from the LOV.

The relationship is therefore a filtered one-to-many: PER_COMPETENCES provides one row per global competence, and PER_COMPETENCE_LEVELS_V is consulted as an existence test rather than joined for data. This design avoids row duplication while guaranteeing that only usable competences appear.

Key Columns

• COMPETENCE_ID — the unique numeric identifier of the competence. This is the primary join key back to PER_COMPETENCES and to level records, and is typically the value flexed or assigned when a competence is selected.
• COMPETENCE_ALIAS — a short, user-defined code or abbreviation for the competence. Useful where space is limited or where integration systems expect a compact reference.
• COMPETENCE_NAME — the descriptive name of the competence, returned from the COMP.NAME column. This is the value users most commonly search and select, and it is the target of the "competence_name" keyword associated with this object.
• DESCRIPTION — free-text detail explaining the competence, used to disambiguate similar entries in the LOV.

Common Use Cases and Queries

The principal use case is supplying the LOV behind a competence field in Projects, or providing an integration a validated list of global competences. Typical patterns include:

• Populating a selection list in a custom form or OAF page.
• Validating a competence identifier or name supplied by an external system before it is accepted into Projects data.
• Reporting on available global competences for resource-planning analysis.

A simple lookup by name:

SELECT competence_id, competence_alias, competence_name FROM apps.pa_global_competences_lov_v WHERE competence_name LIKE :p_name ORDER BY competence_name;

A full LOV population:

SELECT competence_name, competence_id FROM apps.pa_global_competences_lov_v ORDER BY competence_name;

Because the view already excludes non-global and level-less competences, queries need no additional filtering, and no DML should ever be issued against it.