Search Results allow_as_proj_member




Overview
Explore in AI Chat

Overview

APPS.PA_PROJECT_ROLELIST_LOV_V is a reporting and list-of-values (LOV) view in the Oracle E-Business Suite Projects (PA) module. Its purpose is to present the set of project roles that are valid for assignment as project team members, filtered by the role control code ALLOW_AS_PROJ_MEMBER. In Oracle Projects, role controls determine which actions a given project role type is permitted to perform on a project; the ALLOW_AS_PROJ_MEMBER control specifically governs whether a role may be added to a project's role list and therefore appear as a project member. This view exposes that filtered role list joined with the owning project and role list identifiers, making it suitable for LOV definitions, project team setup screens, concurrent program lookups, and custom reporting. Because the underlying objects include both the role type definition view and the role list membership table, the view effectively answers the question: "for a given project and role list, which roles are permitted to be used as project members?"

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

  • PA_PROJECT_ROLE_TYPES_V (view) — supplies the role type definition and attribute columns aliased as role.
  • PA_ROLE_CONTROLS (synonym to table) — supplies the role control rows aliased as control, filtered on role_control_code = 'ALLOW_AS_PROJ_MEMBER'.
  • PA_ROLE_LIST_MEMBERS (synonym to table) — links role list identifiers to project role identifiers, aliased as prlm.
  • PA_PROJECTS_ALL (synonym to table) — provides the project name and segment1 (project number), aliased as ppa, joined via role_list_id.
  • PA_ROLE_UTILS and PA_ROLE_JOB_BG_UTILS (packages) — utility packages documented as dependencies supporting role and job default logic.

The view text is a UNION ALL of two SELECT DISTINCT branches that share an identical column projection but differ in how the role list linkage is resolved, ultimately joining PA_ROLE_LIST_MEMBERS to PA_PROJECTS_ALL on role_list_id.

Key Columns

Common Use Cases and Queries

Typical usage covers validating project member assignments, populating LOVs on project team forms, and reporting the roles enabled for project membership per project. A representative query listing member roles for a project is:

  • SELECT meaning, project_role_id, role_list_id FROM apps.pa_project_rolelist_lov_v WHERE segment1 = :project_number;
  • SELECT DISTINCT meaning FROM apps.pa_project_rolelist_lov_v ORDER BY 1; — builds a simple role LOV.
  • SELECT p.name, v.meaning FROM apps.pa_project_rolelist_lov_v v, apps.pa_projects_all p WHERE v.role_list_id = p.role_list_id; — reports member roles across projects.

Because the view is filtered by the ALLOW_AS_PROJ_MEMBER role control, its result set is intentionally narrower than PA_PROJECT_ROLE_TYPES_V; consumers should not treat it as a complete catalog of project roles. The DISTINCT and UNION ALL structure can also produce duplicate role rows when a role belongs to multiple role lists, so join predicates to project should be applied carefully. For integration or BI Publisher extracts, this view provides a convenient, pre-filtered source that already encodes the role control and role list membership logic maintained by the PA_ROLE_UTILS utilities.