Search Results evaluation_method

Overview

PER_COMPETENCES_VL is an APPS-owned, VALID database view in the Oracle E-Business Suite Human Resources (PER) product module. It is a "VL" (view-language) construct, meaning it exposes a translatable entity by joining the base transactional table to its translation table and restricting the translation rows to the session's current language via USERENV('LANG'). In practice, the view presents competency definitions combined with their language-specific descriptive attributes—name, alias, behavioural indicator, and description—so that consumers see a single, already-localized record per competency.

Because competency data is central to competency-based management in EBS HR, this view serves as a convenient reporting and integration surface. Rather than requiring report authors, APIs, or external integrations to join the base and translation tables manually and filter on language, the view encapsulates that logic and exposes a denormalized result set. It is referenced by forms, concurrent programs, and custom reports that display competencies in the user's language, and it appears in the documented (ETRM 12.2.2) metadata as a stable, valid object suitable for query-based access. It behaves consistently across EBS 12.1.1 and 12.2.2, with the 12.2.2 metadata confirming the same underlying definition.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through synonyms:

• PER_COMPETENCES (aliased CPN) — the base (non-translatable) competency table holding the core competency record and all descriptive flexfield and audit columns. This is the primary row source.
• PER_COMPETENCES_TL (aliased CPL) — the translation table holding language-specific text (NAME, COMPETENCE_ALIAS, BEHAVIOURAL_INDICATOR, DESCRIPTION).

The join predicate is CPN.COMPETENCE_ID = CPL.COMPETENCE_ID combined with CPL.LANGUAGE = USERENV('LANG'). This means every row returned represents one competency in the caller's session language. The view also selects CPN.ROWID as ROW_ID, which supports row identification in forms and certain update-through-view patterns.

Key Columns

• ROW_ID — the ROWID of the underlying PER_COMPETENCES row, useful for direct addressing.
• COMPETENCE_ID — primary identifier of the competency; the join key between base and translation tables.
• BUSINESS_GROUP_ID — the HR business group that owns the competency.
• NAME, COMPETENCE_ALIAS, BEHAVIOURAL_INDICATOR, DESCRIPTION — language-specific attributes sourced from PER_COMPETENCES_TL.
• DATE_FROM, DATE_TO — effective dates of the competency definition.
• CERTIFICATION_REQUIRED, EVALUATION_METHOD, RENEWAL_PERIOD_FREQUENCY, RENEWAL_PERIOD_UNITS, MAX_LEVEL, MIN_LEVEL, RATING_SCALE_ID — the configuration controlling how the competency is assessed, certified, renewed, and rated.
• COMPETENCE_DEFINITION_ID — links the competency to its definition grouping.
• OBJECT_VERSION_NUMBER — optimistic locking/versioning support.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield columns.

Common Use Cases and Queries

Typical scenarios include competency catalog reporting, list-of-values population, and data extraction for talent or learning integrations. Because the view is already language-filtered, queries remain simple and consistent.

Example — list all competencies in the current language for a business group:

SELECT competence_id, name, competence_alias
FROM   apps.per_competences_vl
WHERE  business_group_id = :p_bg_id
AND    TRUNC(SYSDATE) BETWEEN date_from AND NVL(date_to, TRUNC(SYSDATE))
ORDER BY name;

Example — retrieve rating configuration for a competency:

SELECT name, min_level, max_level, rating_scale_id
FROM   apps.per_competences_vl
WHERE  competence_id = :p_competence_id;

Example — identify competencies requiring certification:

SELECT competence_id, name, evaluation_method, renewal_period_frequency
FROM   apps.per_competences_vl
WHERE  certification_required = 'Y';

Because the view performs the language restriction internally, callers should avoid re-joining PER_COMPETENCES_TL. For set-based extraction, filter on BUSINESS_GROUP_ID and effective dates to keep results performant.