Results for “requirement_end_date”

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

Overview

PA_REQMNT_COMPETENCES_AMG_V is a reporting and integration view in the Oracle E-Business Suite Applications (APPS) schema, owned by the Projects (PA) product family. The view presents the complete set of competences associated with a project requirement. In this context a "requirement" corresponds to an open project assignment. The view therefore exposes the competences that a given project assignment demands, together with the associated proficiency (rating level) and whether each competence is mandatory. Because it consolidates data across the Projects and Human Resources (PER) schemas, it is intended for reporting, inquiry, and integration scenarios where a denormalized, read-only representation of requirement competences is required. The object is documented as a VIEW with STATUS VALID across 12.1.1 and 12.2.2, and the underlying ETRM metadata is consistent between the two releases regarding owner and referenced base objects.

Underlying Base Objects

The view is defined over five documented base objects, all accessed through APPS synonyms: PA_PROJECTS_ALL, PA_PROJECT_ASSIGNMENTS, PER_COMPETENCES, PER_COMPETENCE_ELEMENTS, and PER_RATING_LEVELS. The join logic is significant:

• PER_COMPETENCE_ELEMENTS is the driving table, filtered by OBJECT_NAME = 'OPEN_ASSIGNMENT'. Its OBJECT_ID links to the assignment and its COMPETENCE_ID links to the competence definition.
• PA_PROJECT_ASSIGNMENTS supplies the assignment context (ASSIGNMENT_ID, ASSIGNMENT_NAME, START_DATE, END_DATE, PROJECT_ID). The join is COMP_ELE.OBJECT_ID = ASGMT.ASSIGNMENT_ID.
• PA_PROJECTS_ALL provides the project header (NAME, SEGMENT1) via ASGMT.PROJECT_ID = PROJ.PROJECT_ID.
• PER_COMPETENCES provides the competence master data (NAME, COMPETENCE_ALIAS, BUSINESS_GROUP_ID) via COMP_ELE.COMPETENCE_ID = COMP.COMPETENCE_ID.
• PER_RATING_LEVELS is outer-joined (PROFICIENCY_LEVEL_ID = RL.RATING_LEVEL_ID (+)) so that competences lacking a defined rating level are still returned, with RL.STEP_VALUE null.

Key Columns

The view publishes the following columns (view text aliases shown in parentheses where applicable):

• REQUIREMENT_ID (OBJECT_ID) — identifier of the open assignment acting as the requirement.
• REQUIREMENT_NAME (ASSIGNMENT_NAME) — name of the project assignment.
• REQUIREMENT_START_DATE / REQUIREMENT_END_DATE — assignment date range.
• PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER — project context (PROJ.NAME, PROJ.SEGMENT1).
• COMPETENCE_ELEMENT_ID, COMPETENCE_ID — identifiers linking to the competence element and the competence definition.
• COMPETENCE_NAME, COMPETENCE_ALIAS — competence description and short alias.
• RATING_LEVEL_ID, RATING_LEVEL_VALUE — proficiency level id and its step value (RL.STEP_VALUE).
• MANDATORY_FLAG (MANDATORY) — indicates whether the competence is required.
• RECORD_VERSION_NUMBER (OBJECT_VERSION_NUMBER) — optimistic locking/version column.
• BUSINESS_GROUP_ID, CREATION_DATE, LAST_UPDATE_DATE — audit and business group columns sourced from PER_COMPETENCES.

Common Use Cases and Queries

Typical uses include requirement competency reporting, staffing gap analysis, and exposing competences to integration or BI layers. A basic query lists all competences for a specific project requirement:

• SELECT requirement_id, requirement_name, competence_name, competence_alias, rating_level_value, mandatory_flag FROM pa_reqmnt_competences_amg_v WHERE requirement_id = :assignment_id;
• SELECT project_number, project_name, requirement_name, competence_name, rating_level_value FROM pa_reqmnt_competences_amg_v WHERE project_id = :project_id ORDER BY requirement_name, competence_name;
• SELECT requirement_name, competence_name FROM pa_reqmnt_competences_amg_v WHERE mandatory_flag = 'Y'; — isolate mandatory competences.

Because PER_RATING_LEVELS is outer-joined, reports should tolerate null RATING_LEVEL_VALUE. All access should be read-only via the APPS synonym; the view is not intended as a DML target.