Search Results pa_project_rolelist_lov_v




Overview
Explore in AI Chat

Overview

PA_PROJECT_ROLELIST_LOV_V is a reporting and validation view owned by the APPS schema in Oracle E-Business Suite, released under the Projects (PA) product family. Its name indicates two distinct design purposes: it functions as a List of Values (LOV) source and as a role-list membership joiner for project roles. The view presents project role types that are eligible to be assigned as project members, resolved against the role lists attached to specific projects.

Because the view is defined over several role control and role list tables, it consolidates role definitions with the project-level configuration that constrains them. This makes it suitable for reporting on which roles are permitted on a given project, for populating selection lists in concurrent programs or custom forms, and for integration extracts that require role eligibility information without reproducing the multi-table join logic.

The "ALLOW_AS_PROJ_MEMBER" search term maps directly to the ROLE_CONTROL_CODE filter in the view definition. This control code gates which project role types may be designated as project members, so the view is the canonical source for that eligibility question. In 12.1.1 and 12.2.2 the object retains the same name, schema, and purpose; the documented 12.2.2 metadata confirms it remains VALID and references the same core role tables.

Underlying Base Objects

The documented base objects referenced by the view are PA_PROJECT_ROLE_TYPES_V (a view), PA_ROLE_CONTROLS, PA_ROLE_LIST_MEMBERS, PA_PROJECTS_ALL, PA_ROLE_UTILS (package), and PA_ROLE_JOB_BG_UTILS (package). PA_PROJECTS_ALL, PA_ROLE_CONTROLS, and PA_ROLE_LIST_MEMBERS are exposed through synonyms to the APPS schema.

The view text is a UNION ALL of two branches. Both branches select from PA_PROJECT_ROLE_TYPES_V aliased as ROLE, joined to PA_ROLE_CONTROLS (CONTROL), PA_ROLE_LIST_MEMBERS (PRLM), and PA_PROJECTS_ALL (PPA). The join predicates link PRLM.PROJECT_ROLE_ID to ROLE.PROJECT_ROLE_ID, ROLE.PROJECT_ROLE_ID to CONTROL.PROJECT_ROLE_ID, and PPA.ROLE_LIST_ID to PRLM.ROLE_LIST_ID. The first branch applies the filter CONTROL.ROLE_CONTROL_CODE = 'ALLOW_AS_PROJ_MEMBER'. The DISTINCT keyword appears in each branch, indicating that the underlying joins may produce duplicate role rows that the view deduplicates.

The packages PA_ROLE_UTILS and PA_ROLE_JOB_BG_UTILS are recorded as referenced objects, indicating that role list and role control maintenance logic is implemented in PL/SQL rather than through direct table manipulation. Modifications to role eligibility should therefore follow the supported package APIs to preserve view consistency.

Key Columns

  • ROW_ID — Surrogate identifier from the role type view, used by the LOV framework for row identification.
  • PROJECT_ROLE_ID — Primary key linking a role to its control record and role list membership.
  • PROJECT_ROLE_TYPE — Classification of the role, distinguishing role categories used in project staffing.
  • MEANING — Descriptive name of the role, the value typically displayed in the LOV.
  • SCHEDULABLE_FLAG, QUERY_LABOR_COST_FLAG — Flags governing whether the role can be scheduled or can query labor costs.
  • START_DATE_ACTIVE, END_DATE_ACTIVE — Effective date range controlling role availability.
  • DEFAULT_MIN_JOB_LEVEL, DEFAULT_MAX_JOB_LEVEL, DEFAULT_JOB_ID — Default job grade boundaries and job assignment.
  • DEFAULT_ACCESS_LEVEL, FREEZE_RULES_FLAG — Security and rule-freeze configuration for the role.
  • ROLE_LIST_ID — Identifier of the role list to which the role belongs, joined from PA_ROLE_LIST_MEMBERS.
  • NAME, SEGMENT1 — Project name and project number from PA_PROJECTS_ALL, contextualising the role list.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns carried through from the role type definition.

Common Use Cases and Queries

A frequent use is retrieving the valid project member roles for a specific project, filtered by the project number segment. The LOV framework also queries this view to populate role selection fields on project staffing forms, relying on NAME and SEGMENT1 to scope results to the active project.

  • Reporting all roles eligible as project members for a project number.
  • Validating a role before inserting a project member assignment.
  • Extracting role lists for integration into external staffing systems.

A representative query is: SELECT project_role_id, meaning, role_list_id, name, segment1 FROM pa_project_rolelist_lov_v WHERE segment1 = :project_number AND NVL(end_date_active, SYSDATE) > SYSDATE ORDER BY meaning; A broader query omitting the project filter returns all eligible role to project combinations, which is useful for reconciliation reports. Consumers should note that the effective date columns are role-level, and that project-specific role lists are resolved through the ROLE_LIST_ID join to PA_PROJECTS_ALL.