Search Results pa_project_players_v




Overview
Explore in AI Chat

Overview

The APPS.PA_PROJECT_PLAYERS_V view is a reporting construct within the Oracle E-Business Suite Projects (PA) module. It exposes the assignment of persons to projects in specific project roles, together with a denormalized set of personal attributes resolved at query time. The view is documented in ETRM as "10SC Only," indicating that it is a shared or localized configuration artifact intended for a specific release stream rather than a core, universally deployed object. Its status is VALID in the APPS schema under Oracle EBS 12.1.1 and 12.2.2.

Functionally, the view serves as a convenience layer over the PA_PROJECT_PLAYERS entity. Instead of requiring consumers to join to person and role lookups manually, the view returns the project identifier, the person identifier, the resolved person name components, the employee number, the active date range of the assignment, and the human-readable role meaning. Because the personal attributes are resolved through the PA_UTILS.GETPERSONINFO function, the view is intended for read-only reporting and integration use rather than transactional maintenance.

Underlying Base Objects

The view is defined over two primary data sources and depends on two PL/SQL packages:

The join is governed by a predicate on PA_UTILS.GETPERSONINFO(PRO.PERSON_ID) = 'FOUND', which excludes assignments whose person cannot be resolved. This behavior is significant: orphaned or unresolvable person references are silently dropped from the result set.

Key Columns

  • PROJECT_ID: Identifier of the project to which the person is assigned.
  • PERSON_ID: Identifier of the assigned person.
  • FULL_NAME: Complete formatted name, resolved via GETPERSONINFO.
  • LAST_NAME, FIRST_NAME, MIDDLE_NAMES: Individual name components. MIDDLE_NAMES is the column relevant to searches for middle-name data; it is not stored on the assignment itself but derived at runtime.
  • EMPLOYEE_NUMBER: The person's employee number, useful for reconciliation with HR records.
  • START_DATE_ACTIVE, END_DATE_ACTIVE: Effective range of the project role assignment; END_DATE_ACTIVE is null for open-ended assignments.
  • ROLE: The translated meaning of the project role type (ROL.MEANING).

Common Use Cases and Queries

Typical uses include project team rosters, resource utilization reporting, and integrations that require person names alongside project role assignments. Because MIDDLE_NAMES is exposed directly, the view is also convenient for name-matching and identity reconciliation tasks.

Listing the players on a given project:

  • SELECT project_id, person_id, full_name, role, start_date_active, end_date_active FROM apps.pa_project_players_v WHERE project_id = :project_id AND (end_date_active IS NULL OR end_date_active >= SYSDATE);

Searching by middle name:

  • SELECT project_id, person_id, full_name, middle_names FROM apps.pa_project_players_v WHERE UPPER(middle_names) LIKE UPPER('%' || :search_term || '%');

Because PA_PROJECT_PLAYERS_V ultimately depends on PA_PROJECT_PLAYERS, PA_PROJECT_ROLE_TYPES, and PA_UTILS, any performance tuning or functional change to those base objects can materially affect the view's output and cost.