Results for “pa_project_role_types”

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

Overview

PA_PROJECT_ROLE_TYPES is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and belonging to the PA (Projects) product family. Its documented purpose is to expose a list of project role types for a specified language. The view serves as a filtered, language-aware access point to project role definitions used throughout Oracle Projects, and is the object typically queried when reporting, integration, or configuration work requires the set of person-based project roles defined in an environment.

Because Oracle Projects stores role definitions in a translated (multi-language) base table, the view resolves the language-specific display values and simultaneously applies a business filter. Rather than returning every role definition, PA_PROJECT_ROLE_TYPES restricts output to rows where ROLE_PARTY_CLASS equals 'PERSON'. This makes it the canonical source for "person" project roles — the roles that can be assigned to human resources on a project team — as opposed to roles tied to other party classes such as organizations or groups.

Underlying Base Objects

The documented view text is a straightforward projection over PA_PROJECT_ROLE_TYPES_VL, the translated view that resolves language-specific columns such as MEANING and DESCRIPTION. PA_PROJECT_ROLE_TYPES_VL is itself defined over the underlying base tables PA_PROJECT_ROLE_TYPES_B and PA_PROJECT_ROLE_TYPES_TL, which hold the language-independent attributes and the translated (TL) attributes respectively.

The ETRM metadata additionally records PA_ROLE_JOB_BG_UTILS as a referenced base object. This is a PL/SQL package that supplies supporting logic for role and job defaulting, such as default job, minimum and maximum job level derivation. Its presence in the dependency list indicates that role-type validation and defaulting behavior is coupled to the view through the Projects role/job utility layer.

The view inherits the standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 from the translated base object.

Key Columns

• PROJECT_ROLE_ID — The primary identifier for the role type; the key used in foreign-key relationships with project team and assignment tables.
• PROJECT_ROLE_TYPE — The internal (untranslated) role type code.
• MEANING / DESCRIPTION — The language-resolved name and description of the role type, dependent on the LANGUAGE column returned by the translated source.
• ROLE_PARTY_CLASS — The party class discriminator; the view hard-codes the filter to 'PERSON'.
• DEFAULT_JOB_ID, DEFAULT_MIN_JOB_LEVEL, DEFAULT_MAX_JOB_LEVEL — Defaulting values used when the role is applied to a job-based resource, supplied via the PA_ROLE_JOB_BG_UTILS package.
• DEFAULT_ACCESS_LEVEL — The access level granted by default to a person holding the role.
• QUERY_LABOR_COST_FLAG — Indicates whether labor cost information should be queried for the role.
• FREEZE_RULES_FLAG — Controls whether rules associated with the role are frozen.
• MENU_ID — Associates the role with a menu used for role-based navigation.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Date-effective range controlling when the role type is active.
• ROW_ID, RECORD_VERSION_NUMBER — Surrogate identifier and optimistic-locking version column.
• LANGUAGE, SOURCE_LANG — The language of the returned translation and the source language of the base record.

Common Use Cases and Queries

The view is commonly used to drive LOVs, reports, and integration extracts that require the list of person project roles. A typical query is:

SELECT project_role_id,
       project_role_type,
       meaning,
       default_access_level
FROM   apps.pa_project_role_types
WHERE  SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                   AND NVL(end_date_active, SYSDATE)
ORDER BY meaning;

To confirm defaulting behavior for role/job combinations, developers join the view to the job defaults:

SELECT prt.meaning,
       prt.default_job_id,
       prt.default_min_job_level,
       prt.default_max_job_level
FROM   apps.pa_project_role_types prt
WHERE  prt.freeze_rules_flag = 'Y';

Because the view filters to ROLE_PARTY_CLASS = 'PERSON', it should be used specifically for person-role scenarios. For organization or group party classes, the underlying translated view PA_PROJECT_ROLE_TYPES_VL must be queried directly. Reports sourcing from this view should always apply the date-effective predicates on START_DATE_ACTIVE and END_DATE_ACTIVE to avoid returning retired role definitions, and should filter on LANGUAGE where a single-language result set is required.