Search Results competence_definition_id




Overview
Explore in AI Chat

Overview

The PER_COMPETENCE_DEFINITIONS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically under the PER product family. As explicitly stated in the ETRM documentation, it serves as the combinations table for the COMPETENCES Key Flexfield (KFF). In Oracle EBS, a Key Flexfield is a configurable data structure used to capture and represent unique business identifiers, such as accounting codes or, in this context, competency definitions. This table stores the validated, fully-qualified combinations of segments that define specific competencies within the organization's competency framework. Its role is central to the competency management functionality, acting as the master reference for all defined competencies against which employee skills, job requirements, and development goals can be mapped and assessed.

Key Information Stored

The table's primary function is to store each unique competency definition as a flexfield combination. The most critical column is COMPETENCE_DEFINITION_ID, which is the unique identifier (primary key) for each competency record. While the full column list is not detailed in the provided metadata, a competence definition combination table typically stores the concatenated segments (e.g., competency category, skill type, proficiency level) and their individual segment values. It also contains control columns managed by the flexfield infrastructure, such as the APPLICATION_ID, KEY_FLEXFIELD_CODE, and COMBINATION_ID. The ETRM confirms that the primary key constraint PER_COMPETENCE_DEFINITIONS_PK is enforced on the COMPETENCE_DEFINITION_ID column, ensuring data integrity for all related competency transactions.

Common Use Cases and Queries

This table is primarily accessed indirectly through the Oracle HRMS user interface for defining, querying, and reporting on competencies. Common business scenarios include creating a new competency for technical skills, defining behavioral competencies for performance management, or setting required competencies for a job. From a reporting or data extraction standpoint, a typical query would join this table to the PER_COMPETENCES table (which holds instances of competencies assigned to people or positions) to generate a comprehensive skills inventory. A foundational SQL pattern would be:

  • SELECT pcd.COMPETENCE_DEFINITION_ID, pcd.[SEGMENT1], pcd.[SEGMENT2], pc.PERSON_ID
  • FROM HR.PER_COMPETENCE_DEFINITIONS pcd,
  • HR.PER_COMPETENCES pc
  • WHERE pcd.COMPETENCE_DEFINITION_ID = pc.COMPETENCE_DEFINITION_ID;

This table is also crucial for any custom integrations or extensions that need to validate or reference the master list of organizational competencies.

Related Objects

As per the documented foreign key relationship, the most directly dependent object is the PER_COMPETENCES table. The PER_COMPETENCES table references PER_COMPETENCE_DEFINITIONS via its COMPETENCE_DEFINITION_ID column, meaning every competence recorded for an employee, job, or position must link to a valid definition in this master table. This table is also intrinsically linked to the underlying flexfield structures, specifically the FND_FLEX_VALUES and related tables that store the valid segment values. While not listed in the brief metadata, it is common for other HR objects like PER_JOBS (for job requirements) and performance management tables to have indirect dependencies on the competency definitions stored here.