Results for “project_role_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PROJECT_ROLES_RES_V is an Oracle Applications (APPS) view owned by the Projects (PA) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as a "Project roles resource view," meaning it exposes project role definitions in a form suitable for use as a resource source within the Projects application. The view presents role identifiers and role types alongside a fixed set of descriptive flags and unit attributes. It is a lightweight, read-only construct that flattens the role-type definition data held in PA_PROJECT_ROLE_TYPES and pairs it with resource-related constants that downstream logic and reporting layers consume.

The view is significant because the ROLLUP_QUANTITY_FLAG column, which is the term the user searched for, is exposed here. Although the view text assigns a literal value ('N') to this column, the alias makes the view a convenient single source for querying role-based resource behavior alongside rollout and labor-tracking flags.

Underlying Base Objects

The ETRM metadata identifies three referenced base objects: the PA_GET_RESOURCE package, the PA_PROJECT_ROLE_TYPES view, and the PA_ROLE_JOB_BG_UTILS package. The view text draws its core row set from PA_PROJECT_ROLE_TYPES, projecting PROJECT_ROLE_ID, PROJECT_ROLE_TYPE, and a truncated MEANING column. The PA_GET_RESOURCE package is invoked inside the WHERE clause through the function call PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES, which returns a flag governing date filtering. When that function returns 'Y', the view compares START_DATE_ACTIVE directly; otherwise it substitutes TRUNC(SYSDATE). The effective date filter is BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)), so only currently active role types are returned under normal conditions. PA_ROLE_JOB_BG_UTILS is referenced as a base object in the metadata, indicating a supporting utility role in the object's dependency chain.

Key Columns

• PROJECT_ROLE_ID — Primary identifier of the project role definition, sourced from PA_PROJECT_ROLE_TYPES.
• PROJECT_ROLE_TYPE — Code classifying the role type.
• MEANING — Descriptive name of the role type, truncated to 60 characters via SUBSTR(MEANING,1,60).
• TRACK_AS_LABOR_FLAG — Hard-coded literal 'Y', indicating that roles surfaced by this view are treated as labor resources.
• UNIT_OF_MEASURE — Hard-coded literal 'HOURS', the unit applied to the resource quantity.
• ROLLUP_QUANTITY_FLAG — Hard-coded literal 'N', indicating that quantities for these roles are not rolled up by default at this level.

Because three of the six columns are constants, the view effectively re-packages the role-type definition with a consistent resource profile. The ROLLUP_QUANTITY_FLAG literal of 'N' means consumers can rely on a stable, non-rolled-up quantity semantics for these role resources.

Common Use Cases and Queries

Typical uses include populating project role resource lists, feeding role-based cost or effort reporting, and validating which role types are currently active. A simple query lists active role resources:

• SELECT PROJECT_ROLE_ID, PROJECT_ROLE_TYPE, MEANING, ROLLUP_QUANTITY_FLAG FROM APPS.PA_PROJECT_ROLES_RES_V WHERE PROJECT_ROLE_ID = :role_id;
• SELECT MEANING, UNIT_OF_MEASURE FROM APPS.PA_PROJECT_ROLES_RES_V ORDER BY MEANING;
• SELECT PROJECT_ROLE_TYPE, COUNT(*) FROM APPS.PA_PROJECT_ROLES_RES_V GROUP BY PROJECT_ROLE_TYPE;

Because ROLLUP_QUANTITY_FLAG and TRACK_AS_LABOR_FLAG are constants, queries filtering on them confirm the view's uniform behavior rather than discriminating between rows. Reporting integrations should therefore treat the view as a normalized, currently-effective role resource feed, and rely on PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES to control whether inactive role types are included at runtime.