Search Results pa_proj_members_view




Overview
Explore in AI Chat

Overview

PA_PROJ_MEMBERS_VIEW is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered as part of the PA (Projects) product family and is documented as VALID in the ETRM repository. As its description states, the view exposes project information organized for reporting projects by project member. In practical terms, it answers the question: "Which people are assigned to which projects, in what project role, and what is the current status and organizational context of that project?"

The view consolidates data drawn from the project definition, the carrying-out organization, the project player (team member) assignments, the project role types, the project status codes, and the lookup that identifies the public-sector indicator. Because it joins these sources, it is intended for ad-hoc queries, custom reports, and integration extracts where a denormalized, member-centric project listing is required without having to reproduce the multi-table join logic manually.

Underlying Base Objects

The view is defined over the following documented base objects: PA_PROJECTS (SYNONYM), PA_PROJECT_PLAYERS (VIEW), PA_PROJECT_ROLE_TYPES (VIEW), PA_PROJECT_STATUSES (SYNONYM), HR_ORGANIZATION_UNITS (VIEW), PER_PEOPLE_F (VIEW), and FND_LOOKUPS (VIEW). Supporting logic and security/derivation routines are referenced through packages including FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and PA_ROLE_JOB_BG_UTILS.

In the view text, the primary driving tables are aliased as PROJ (PA_PROJECTS), ORG (HR_ORGANIZATION_UNITS), PEOPLE (PER_PEOPLE_F), PLAYER (PA_PROJECT_PLAYERS), ROLES (PA_PROJECT_ROLE_TYPES), PS (PA_PROJECT_STATUSES), and FND (FND_LOOKUPS). The join conditions link each project to its carrying-out organization, to its players, and each player to the person record; each player's project role type is resolved to the role types reference, the project status code is resolved to project status names, and the project's public-sector flag is decoded against the YES_NO lookup. The view filters to current people (via effective dates and CURRENT_EMPLOYEE_FLAG/CURRENT_NPW_FLAG) and to active player assignments (SYSDATE <= NVL(PLAYER.END_DATE_ACTIVE, SYSDATE+1)).

Key Columns

The view returns the following columns as documented:

Common Use Cases and Queries

Typical uses include building a directory of project team members, reporting a person's current project assignments, filtering active projects by member or role, and feeding external reporting or integration layers. A simple listing by member can be written as:

SELECT member_name, project_number, project_name, project_status, project_role FROM apps.pa_proj_members_view ORDER BY member_name, project_number;

To restrict to a single member and only active roles:

SELECT project_number, project_name, project_status, project_role, start_date, completion_date FROM apps.pa_proj_members_view WHERE member_person_id = :p_person_id ORDER BY start_date DESC;

To count team members per project role for a given project:

SELECT project_role, COUNT(DISTINCT member_person_id) member_count FROM apps.pa_proj_members_view WHERE project_id = :p_project_id GROUP BY project_role ORDER BY project_role;

Because the view already applies current-person and active-assignment predicates as well as Oracle HR security logic through the referenced packages, reports built on it automatically reflect the effective-dated and security-filtered population at query time.