Search Results max_proficiency

Overview

HRFV_REQUIRED_COMPETENCES is a business view template owned by the APPS schema in Oracle E-Business Suite, maintained by the PER (Human Resources) product module. ETRM documents the object as VALID and describes it as the business view template from which the flexfield view is generated. In practice, the view consolidates the requirements side of the competency framework: it associates competences with the organizational entities that require them — business groups, organizations, positions, jobs, and grades — together with the mandatory flag, proficiency thresholds, validity dates, and the core competence indicator derived at runtime.

The view functions as a reporting and integration surface rather than a transactional entity. Rather than joining the full normalized set of PER competency tables manually, report authors, extracts, and interface programs can query HRFV_REQUIRED_COMPETENCES to obtain a denormalized description of required competences with resolved names. It is one of the HRFV family of flexfield business view templates, and its remaining view text (beyond the excerpt) is generated with the descriptor references such as '_DF:PER:PER_COMPETENCE_ELEMENTS:COMP' and '_KF:PER:CMP:CDEF' that support flexfield-style key and descriptive handling of the competence element and competence definition.

Underlying Base Objects

The documented base objects for this view include the following synonym references and one PL/SQL package:

• PER_COMPETENCE_ELEMENTS — the driving table (alias COMP); holds the requirement rows that link a competence to a job, position, organization, or grade.
• PER_COMPETENCES and PER_COMPETENCES_TL — the competence entity and its translated names (CPN).
• PER_COMPETENCE_DEFINITIONS — the competence definition to which each competence belongs (CDEF).
• PER_ALL_POSITIONS and HR_ALL_POSITIONS_F_TL — position entities and translated position names (POS).
• PER_JOBS_TL — translated job names (JOBS), joined with an outer join on JOB_ID.
• PER_VALID_GRADES and PER_GRADES_TL — valid grade mapping and translated grade names (VGRD, GRD).
• HR_ALL_ORGANIZATION_UNITS_TL — translated organization and business group names, used twice (ORGST, BGRT).
• PER_RATING_LEVELS and PER_RATING_LEVELS_TL — rating levels used twice (RATL1, RATL2) to express minimum and maximum proficiency.
• HR_BIS — PL/SQL package, specifically HR_BIS.BIS_DECODE_LOOKUP, used for lookup decoding.

Outer joins are applied so that requirement rows without a position, grade, or organization still return. The business group name is supplied from HR_ALL_ORGANIZATION_UNITS_TL (BGRT) keyed by the element's BUSINESS_GROUP_ID.

Key Columns

• BUSINESS_GROUP_NAME, ORGANIZATION_NAME, POSITION_NAME, JOB_NAME, GRADE_NAME — resolved names of the organizational context of the requirement.
• COMPETENCE_NAME — name of the required competence (CPN.NAME).
• MANDATORY — lookup-decoded YES/NO value via HR_BIS.BIS_DECODE_LOOKUP('YES_NO', COMP.MANDATORY).
• DATE_FROM, DATE_TO — the effective date range of the competence requirement.
• MIN_PROFICIENCY, MAX_PROFICIENCY — concatenations of rating level STEP_VALUE and NAME from PER_RATING_LEVELS.
• CORE_COMPETENCE_FLAG — derived flag; a requirement is core when no ORGANIZATION_ID, POSITION_ID, or JOB_ID is specified.
• COMMENTS — free-text comments on the requirement.
• Primary keys/IDs — BUSINESS_GROUP_ID, COMPETENCE_ID, COMPETENCE_ELEMENT_ID, ENTERPRISE_ID, HIGH_PROFICIENCY_LEVEL_ID, JOB_ID, ORGANIZATION_ID, POSITION_ID, PROFICIENCY_LEVEL_ID, GRADE_ID.

Common Use Cases and Queries

Typical usage includes competency gap analysis, requirement extracts for HR interfaces, and validation of mandatory competences per position or job. A representative query lists mandatory requirements with resolved names:

• SELECT business_group_name, organization_name, position_name, job_name, grade_name, competence_name, mandatory, min_proficiency, max_proficiency FROM apps.hrfv_required_competences;
• SELECT competence_name, min_proficiency, max_proficiency FROM apps.hrfv_required_competences WHERE mandatory = 'Y' AND core_competence_flag = 'Y';
• SELECT position_name, competence_name FROM apps.hrfv_required_competences WHERE position_name IS NOT NULL AND SYSDATE BETWEEN date_from AND NVL(date_to, SYSDATE + 1);

Because the view applies lookup decoding and outer joins, it is well suited to ad hoc reporting and BIP data models, though heavy extracts should still consider the underlying PER tables for performance tuning.