Search Results pa_project_role_types_v




Overview

PA_PROJECT_ROLE_TYPES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It presents the set of active project role types that may be assigned to persons within Oracle Projects. The view functions as a filtered, runtime-restricted projection over the role-type definitions maintained in the Projects repository, exposing role attributes such as schedulability, labor cost query privileges, job level boundaries, menu assignment, and descriptive flexfield segments.

From a reporting and integration standpoint, the view is the standard access point for consumers that require a current, person-oriented list of project roles without needing to inspect the underlying role definition tables directly. Because it applies date-range and exclusions at runtime, it returns only role types that are effective as of the current system date and that are intended for assignment to persons. Integrations, concurrent programs, and custom reports that populate role selection lists or validate role assignments typically resolve role types through this view rather than through the base definition tables.

Underlying Base Objects

The view is defined over PA_PROJECT_ROLE_TYPES_VL, the multi-language base view for project role type definitions. Two PL/SQL packages are referenced in the definition: PA_ROLE_UTILS and PA_ROLE_JOB_BG_UTILS. Documented in ETRM 12.2.2, the referenced base objects are PA_PROJECT_ROLE_TYPES_VL (VIEW), PA_ROLE_JOB_BG_UTILS (PACKAGE), and PA_ROLE_UTILS (PACKAGE).

The view applies three restricting predicates. First, it enforces an effective-date window, requiring TRUNC(SYSDATE) to fall between the role's start date and its end date, with a null end date treated as open-ended. Second, it excludes a fixed set of system role identifiers (2, 3, 4, 5, 6, and 7), removing seeded or internal role types from the result set. Third, it restricts rows to those whose ROLE_PARTY_CLASS is 'PERSON'. Together these predicates yield the active, person-assignable role types only.

The SCHEDULABLE_FLAG column is not a stored value in the base view but is derived at query time through a call to PA_ROLE_UTILS.GET_SCHEDULABLE_FLAG, which accepts the project role identifier and returns the flag dynamically.

Key Columns

Common Use Cases and Queries

Typical uses include populating role selection lists, validating that a proposed role is currently active and person-assignable, and reporting on schedulable role types. The following query lists active, schedulable project roles with their effective dates:

  • SELECT project_role_id, project_role_type, meaning, schedulable_flag, start_date_active, end_date_active FROM apps.pa_project_role_types_v WHERE schedulable_flag = 'Y' ORDER BY meaning;

To report all roles eligible to query labor costs:

  • SELECT project_role_id, meaning, query_labor_cost_flag FROM apps.pa_project_role_types_v WHERE query_labor_cost_flag = 'Y';

To inspect job-level defaults for a specific role:

  • SELECT meaning, default_min_job_level, default_max_job_level, default_job_id FROM apps.pa_project_role_types_v WHERE project_role_id = :role_id;

Because SCHEDULABLE_FLAG is computed through a package function, queries returning large result sets should account for the per-row function call. All access should be performed through the APPS schema or a synonym with appropriate privileges, consistent with standard Oracle EBS security practice.