Results for “competence_id”

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

Overview

PA_COMPETENCE_CRITERIA_TEMP is a temporary (staging) table within the Oracle Projects (PA) module of Oracle E-Business Suite, owned by the PA schema and valid in releases 12.1.1 and 12.2.2. Its purpose is to hold competence criteria records—skill, competency, and rating requirements associated with project staffing and resource qualification—during intermediate processing before those records are validated and moved into their permanent destination tables. As the _TEMP suffix indicates, the table functions as a transient workspace rather than a system of record. ETRM documentation confirms a physical schema of four columns in 12.2.2.

Under a heuristic Data Vault classification, this table is characterized as standalone: it is modeled as an isolated structure that does not participate in the hub-and-link relationships typical of a fully normalized Data Vault, though it retains a foreign-key reference outward to PER_COMPETENCES. This classification is offered as a modeling suggestion only. In practice the temporary table supports batch uploads, interface programs, and concurrent processing routines that populate, evaluate, and consume competence criteria rows within a single session or transaction scope.

Key Information Stored

The documented physical schema comprises four columns. These are the essential attributes of the staging record:

• COMPETENCE_ID — The identifier of the competence being staged. Per the FK metadata, this column references PER_COMPETENCES.COMPETENCE_ID, tying each temporary row back to a defined competency in the common HR competency model.
• COMPETENCE_NAME — The descriptive name of the competence. As a denormalized, human-readable attribute, it is a strong business-key candidate for matching and reporting, though ETRM documentation does not record a unique index on it.
• RATING_LEVEL — The proficiency or rating level required or expected for the competence, used to express grading thresholds (for example novice through expert) during qualification checks.
• MANDATORY_FLAG — A flag indicating whether the competence is mandatory for the associated criterion or assignment. This drives validation and gating logic in staffing and qualification processes.

No dedicated surrogate primary key is documented; the natural key is effectively the combination of the competence identifier with the associated criterion context and rating. Because the table is temporary, key constraints are typically deferred or omitted, and row identity depends on the originating interface or program.

Common Use Cases and Queries

The table is most often encountered in competency upload and validation workflows. Typical scenarios include loading a set of required competences for a project role or job, verifying that each referenced competence exists in PER_COMPETENCES, and confirming whether mandatory competences are satisfied. Reporting against the staging set frequently precedes promotion into permanent staffing requirement tables.

Representative SQL patterns include:

• Validating references: SELECT t.competence_id FROM pa_competence_criteria_temp t WHERE NOT EXISTS (SELECT 1 FROM per_competences c WHERE c.competence_id = t.competence_id);
• Counting mandatory requirements: SELECT competence_name, rating_level FROM pa_competence_criteria_temp WHERE mandatory_flag = 'Y';
• Generating criteria summaries: SELECT competence_id, competence_name, rating_level, mandatory_flag FROM pa_competence_criteria_temp ORDER BY competence_name;

Because content is transient, queries should generally be restricted to the session or program that populated the table.

Related Objects

The most significant related object is the referenced parent table:

• PER_COMPETENCES — The competency definition table. Joined on PA_COMPETENCE_CRITERIA_TEMP.COMPETENCE_ID = PER_COMPETENCES.COMPETENCE_ID, it supplies the authoritative competence definition and validates staging rows.

Beyond this documented FK, the temporary table interacts logically with Oracle Projects staffing and requirement structures and with the PA competency-related concurrent programs and interfaces that populate it, consistent with its role as an intermediate staging object within the Projects module.