Search Results public_sector_flag




Overview
Explore in AI Chat

Overview

APPS.PA_PROJ_MEMBERS_VIEW is an Oracle E-Business Suite internal reporting view that presents project header attributes joined to project member (project player) and organization information in a single denormalized result set. It is defined in the APPS schema and carries an FND Design Data registration of PA.PA_PROJ_MEMBERS_VIEW. Because the object is documented as "Oracle Internal Use Only," Oracle Corporation does not support direct access to it except from standard Oracle Applications programs; nevertheless, it is widely used in custom reports, concurrent program queries, and integration extracts where a consolidated project-and-member listing is required.

The view is particularly relevant when querying the PUBLIC_SECTOR_FLAG column — the attribute referenced in the original search. This flag indicates whether a project is classified as public sector or private sector, making the view a natural source for public sector reporting, funding classification extracts, and access reviews.

Underlying Base Objects

The view is not a simple projection of a single table. Its documented dependencies include:

This composition explains why the view enforces multi-org and HR security implicitly: ORG_ID is supplied through FND_GLOBAL, and person rows visible to the querying user are constrained via HR_SECURITY. Because it spans PA and HR objects, it is a cross-product-family view rather than a pure project module object.

Key Columns

Common Use Cases and Queries

Typical scenarios include public sector project listings, project team roster reports, role-based access reviews, and organization-level project summaries. A representative query filtering on the searched attribute is:

  • SELECT project_number, project_name, public_sector_flag, project_status, member_name
  • FROM apps.pa_proj_members_view
  • WHERE public_sector_flag = 'Y'
  • AND project_status_code = 'APPROVED';

A second pattern joins the view to entitlements or funding tables on PROJECT_ID to reconcile members against authorized roles, and a third aggregates member counts by ORGANIZATION_NAME. Because the view is internal and unsupported for direct access, custom code should pin the release (12.1.1 or 12.2.2), avoid reliance on implicit ORG_ID filtering in cross-organization reports, and consider creating a supported extract through the Project Management public APIs where long-term maintenance is required.