Search Results proj_res_info

Overview

APPS.PA_REP_PROJ_RES_COMP_V is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, owned by the APPS schema. It is part of the Oracle Projects (PA) reporting layer and presents a consolidated, denormalized picture of project resources together with their competency profile, job classification, and organizational context. The name reflects its purpose: PA (Projects), REP (reporting), PROJ (project), RES (resource), and COMP (competence).

The view was designed for out-of-the-box Projects reporting—most notably resource competency and utilization reporting—where users need to relate a resource to the projects they are assigned to, the organization unit they belong to, and the competencies registered against their person record. In the searched context ("proj_res_info"), the term corresponds to the inline subquery alias proj_res_info used in the view definition, which returns the distinct pairing of resource and project assignment. The view therefore acts as a bridge between PA staffing/assignment data, HR organization and job data, and competency data.

Underlying Base Objects

The view is defined over both tables (referenced mostly through APPS synonyms) and supporting packages and views:

• PA_RESOURCES_DENORM — the primary resource source, filtered on effective-dated rows, utilization_flag = 'Y', and joined to job/organization.
• PA_PROJECT_ASSIGNMENTS — used in an inline subquery (proj_res_info) to obtain distinct resource/project assignment pairs.
• PA_PROJECTS_ALL — supplies project name and the project number (segment1).
• HR_ORGANIZATION_UNITS — provides the resource organization unit name and ID.
• PER_JOBS — provides job ID and job name.
• PER_JOB_EXTRA_INFO — outer-joined on 'Job Category' to return jei_information4 and jei_information5.
• PA_HR_COMPETENCE_UTILS — package whose functions Get_Res_Competences, Get_Res_Competences_Count, and Get_Res_Comp_Last_Updated are called per resource row.
• Supporting objects HR_GENERAL and HR_SECURITY (both packages) are referenced in the documented dependency graph, typically invoked indirectly for security and person lookups.

The effective-dating predicate ensures only the current effective resource row is returned for each resource.

Key Columns

• organization_id / name — the resource's home organization unit.
• project_id / name / segment1 — the project the resource is assigned to.
• resource_id / resource_name — the resource identifier and display name.
• PA_HR_COMPETENCE_UTILS.Get_Res_Competences(person_id) — competency text for the resource.
• Get_Res_Competences_Count(person_id) — count of competencies.
• Get_Res_Comp_Last_Updated(person_id) — date the competency record was last updated.
• manager_id / manager_name — the resource's manager.
• job_id / name — the resource's assigned job.
• jei_information4 / jei_information5 — descriptive flexfield job information values.
• schedulable_flag — decoded so a NULL value yields 'N'.
• billable_flag — indicates whether the resource is billable.
• resource_person_type — the resource's person classification.

Common Use Cases and Queries

This view is typically queried for resource competency dashboards, staffing reports, and project resource utilization analysis, often joined back to project or resource keys.

Sample query listing competencies for all resources on a given project:

• SELECT resource_name, name, segment1, Get_Res_Competences_Count(person_id) ... — note that the function columns are not always separately named in external queries, so referencing the view columns directly is preferred.

A more practical form selects the named view columns:

SELECT project_id, name, resource_id, resource_name,
       PA_HR_COMPETENCE_UTILS.Get_Res_Competences_Count(person_id) AS comp_count,
       billable_flag
FROM   apps.pa_rep_proj_res_comp_v
WHERE  segment1 = :project_number
ORDER  BY resource_name;

Because the competency functions execute in SQL, queries should be run with appropriate bind parameters and filtering to avoid performance overhead. The view respects HR security indirectly through its base objects, so results may vary by user responsibility and security profile.