Results for “pa_project_role_types_vl”

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

Overview

PA_PROJECT_ROLE_TYPES_VL is a validation view (the "_VL" suffix) owned by the APPS schema within the Oracle Projects (PA) module. It presents a language-translated, user-facing representation of project role type definitions used throughout Oracle E-Business Suite release 12.1.1 and 12.2.2. Role types define the functional roles that parties can assume on a project — for example, project manager, team member, or administrator — and they carry configuration attributes that govern labor cost querying, access levels, rule freezing, and job-level constraints.

Because the view joins the base table to its translation table and restricts output to the session language via USERENV('LANG'), it returns exactly one row per role type, with the meaning and description rendered in the user's current language. This makes it the standard source for LOVs (lists of values), concurrent program parameters, Oracle Forms blocks, OAF pages, and custom BI Publisher or Discoverer reports that need to display role types by name rather than by internal identifier. Status is documented as VALID, confirming the object is compiled and usable in a supported environment.

Underlying Base Objects

ETRM metadata documents three referenced objects behind this view:

• PA_PROJECT_ROLE_TYPES_B (SYNONYM) — the base table holding the non-translatable attributes of each role type, keyed by PROJECT_ROLE_ID.
• PA_PROJECT_ROLE_TYPES_TL (SYNONYM) — the translation table supplying MEANING and DESCRIPTION per LANGUAGE, joined on PROJECT_ROLE_ID and LANGUAGE.
• PA_ROLE_JOB_BG_UTILS (PACKAGE) — a PL/SQL utility package whose functions are invoked directly in the view definition.

The view text confirms an inner join between the _B and _TL tables on PROJECT_ROLE_ID, filtered by the session language. Three columns are derived at runtime through package calls: PA_ROLE_JOB_BG_UTILS.GET_JOB_ID, GET_MIN_JOB_LEVEL, and GET_MAX_JOB_LEVEL, each passed the PROJECT_ROLE_ID. This design means the view is not a simple projection; its cost includes function execution, and its performance depends on the role-to-job configuration data those functions resolve.

Key Columns

• PROJECT_ROLE_ID — the primary business key of the role type; the join key to the translation table and the input to all package functions.
• PROJECT_ROLE_TYPE — the internal code identifying the role type.
• MEANING / DESCRIPTION — the translated display name and long description, sourced from the _TL table and filtered to the session language.
• QUERY_LABOR_COST_FLAG — indicates whether labor costs may be queried for the role.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the role type is usable.
• DEFAULT_JOB_ID, DEFAULT_MIN_JOB_LEVEL, DEFAULT_MAX_JOB_LEVEL — job and job-level defaults and bounds derived from PA_ROLE_JOB_BG_UTILS.
• FREEZE_RULES_FLAG, DEFAULT_ACCESS_LEVEL, ROLE_PARTY_CLASS, STATUS_LEVEL — governance attributes controlling rule freezing, default access, the party classification applicable to the role, and its status.
• MENU_ID, RECORD_VERSION_NUMBER — menu association and optimistic locking version.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the standard Oracle Flexfield descriptive attribute set.
• LANGUAGE, SOURCE_LANG, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — translation context and audit columns.

Common Use Cases and Queries

Typical uses include populating role-type LOVs in custom forms and OAF pages, filtering role types by expiry date for validation logic, and reporting on role-to-job-level configuration. A basic active-role listing:

• SELECT project_role_id, project_role_type, meaning, start_date_active, end_date_active FROM apps.pa_project_role_types_vl WHERE NVL(end_date_active, SYSDATE) >= SYSDATE ORDER BY meaning;
• SELECT meaning, default_job_id, default_min_job_level, default_max_job_level, freeze_rules_flag FROM apps.pa_project_role_types_vl ORDER BY meaning;
• SELECT role_party_class, default_access_level, COUNT(*) FROM apps.pa_project_role_types_vl GROUP BY role_party_class, default_access_level;

Because package functions execute per row, restrict queries with WHERE clauses wherever possible, and avoid unbounded full scans in high-volume reporting.