Search Results pa_project_role_types_b_n1

Overview

PA.PA_PROJECT_ROLE_TYPES_B is a foundational setup table in the Oracle Projects (PA) schema that stores implementation-defined project role types. These role types represent the roles or responsibilities that project players—key members associated with a project—can hold. A project role type is more than a label: it governs labor cost security. For each role type, the application determines whether the key member assigned that role can view labor costs both online and within reports. Oracle Projects seeds a Project Manager role type at installation, which implementations commonly use as a template for additional roles such as Project Accountant, Team Lead, or Billing Specialist.

The table's _B suffix denotes that it is the base (or "table") component of a translated or seeded entity. The physical record stores effective-dated, implementation-controlled configuration and is stored in the APPS_TS_TX_DATA tablespace with PCT Free 2. From a data modeling perspective, the metadata's heuristic classification of this object is satellite-leaning. This suggests the table behaves primarily as a descriptive attribute satellite attached to a more stable business key—in this case the project role identity—rather than as a transactional hub or a pure link table, though its foreign keys to PA_PROJECT_ASSIGNMENTS and PA_PROJECT_ROLE_TYPES introduce associative characteristics.

Key Information Stored

The table contains 38 documented columns. The most significant are summarized below, distinguishing surrogate keys from business keys.

• PROJECT_ROLE_TYPE (VARCHAR2(20)) — The unique, implementation-defined name of the project role type. This is a business-key candidate and the leading column of unique index PA_PROJECT_ROLE_TYPES_B_U1.
• PROJECT_ROLE_ID (NUMBER) — Surrogate identifier for the role type. It is a business-key candidate and the leading column of unique index PA_PROJECT_ROLE_TYPES_B_U3.
• QUERY_LABOR_COST_FLAG — Controls whether players assigned to this role can view labor costs online and in reports; the core labor cost security switch.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective dating window that determines when the role type is active.
• DESCRIPTION (VARCHAR2(250)) — Human-readable description of the role type.
• MEANING (VARCHAR2(80)) — Documented as obsolete and not used.
• MENU_ID — Foreign key to FND_MENUS, linking the role to a menu definition.
• DEFAULT_JOB_ID, DEFAULT_MIN_JOB_LEVEL, DEFAULT_MAX_JOB_LEVEL — Default job and grade/level boundaries associated with the role.
• ROLE_PARTY_CLASS — Party classification used by non-unique index PA_PROJECT_ROLE_TYPES_B_N1 for lookup filtering.
• DEFAULT_ACCESS_LEVEL, STATUS_LEVEL, FREEZE_RULES_FLAG — Access control and rule enforcement attributes.
• RECORD_VERSION_NUMBER — Optimistic locking counter for concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segments available for client extension.
• ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema; it participates in both unique indexes (PA_PROJECT_ROLE_TYPES_B_U1 and _U3).
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

A frequent requirement is listing the currently active project role types and their labor cost visibility setting:

SELECT prt.project_role_type, prt.description, prt.query_labor_cost_flag, prt.start_date_active, prt.end_date_active FROM pa.pa_project_role_types_b prt WHERE TRUNC(SYSDATE) BETWEEN NVL(prt.start_date_active, SYSDATE) AND NVL(prt.end_date_active, SYSDATE) ORDER BY prt.project_role_type;

Security auditing queries commonly filter on the flag to identify roles that expose labor costs, or to reconcile which roles are referenced by active project assignments through the PPT_ASSIGNMENT_ID link to PA_PROJECT_ASSIGNMENTS. Reporting layers frequently join on PROJECT_ROLE_ID to obtain the role description for a given assignment, while the ROLE_PARTY_CLASS index supports lookups by party classification in resource and staffing reports.

Related Objects

The following objects are most significant in relation to PA_PROJECT_ROLE_TYPES_B, based on the documented foreign key relationships:

• PA.PA_PROJECT_ROLE_TYPES — Referenced through PROJECT_ROLE_ID; the associated TL/translated or logical parent.
• PA.PA_PROJECT_ASSIGNMENTS — Referenced through PPT_ASSIGNMENT_ID, linking role types to specific project player assignments.
• FND_MENUS — Referenced through MENU_ID to associate a functional menu with the role type.
• PA_PROJECT_ROLE_TYPES_TL — Translation table supplying language-specific role names, joined on PROJECT_ROLE_ID.
• PA_PROJECT_PLAYERS / PA_PROJECT_PARTIES — Downstream consumers that apply role-based labor cost security.
• PA_PROJECT_ROLE_TYPES_B_U1 and _U3 — Unique indexes enforcing business-key uniqueness on PROJECT_ROLE_TYPE and PROJECT_ROLE_ID respectively.

Together these objects form the role configuration and security backbone that Oracle Projects uses to control who can see labor cost information across projects.