Search Results oke_compiled_access_rules

Overview

PA_PROJECT_ROLE_TYPES is a Projects (PA) module reference table that defines implementation-defined responsibilities or positions assigned to employees on projects. Each row represents a named project role type — such as project manager, team lead, or reviewer — that an organization configures to describe how personnel participate on a project. The table functions as a shared master list consumed by project staffing, resource assignment, and access-control processes throughout Oracle EBS.

In the supplied environment the table is documented as "Not implemented in this database," meaning it exists in the application data model but carries no rows in the instance from which the metadata was extracted. The primary key is PA_PROJECT_ROLE_TYPES_PK, defined on the PROJECT_ROLE_ID column. Under the heuristic Data Vault classification supplied in the metadata, the object is described as hub-leaning: it is best modeled as a hub because it holds a stable, non-transactional business key (the role type identifier) that many dependent objects reference through foreign keys, rather than as a link or satellite.

Key Information Stored

The most significant documented columns are:

• PROJECT_ROLE_ID — the surrogate primary key and the column to which nearly all downstream foreign keys point.
• MENU_ID — foreign key to FND_MENUS, associating the role type with a menu definition used for role-based access.
• DEFAULT_JOB_ID — foreign key to PER_JOBS, providing a default job for the role type.

Conventional implementations of this table also carry a role name and description (the translatable text resides in the companion _TL table), a flag indicating whether the role type is active or reportable, and audit columns. The business-key candidate is the role type name or code rather than the surrogate PROJECT_ROLE_ID, since the latter is generated and meaningless outside the system. The presence of both a menu reference and an access-rule reference confirms that role types double as an access-control construct, not merely a staffing label.

Common Use Cases and Queries

The primary use case is validating and reporting project staffing. A typical query joins the base table to its translation table and to PA_PROJECT_PLAYERS to list roles in use on a project:

• Lookup validation — confirm that a PROJECT_ROLE_TYPE supplied by a resource assignment exists and is active before insert.
• Staffing reports — aggregate assignments by role to analyze resource mix across projects.
• Access analysis — because OKE_K_ACCESS_RULES and OKE_COMPILED_ACCESS_RULES reference ROLE_ID, this table participates in Oracle Knowledge/access-rule resolution, so queries often join it to compiled access rules to determine entitlement.
• Default derivation — resolving DEFAULT_JOB_ID from PER_JOBS to propose a job when a resource is assigned.

Queries should generally filter on the active flag and join through the _TL table when displaying user-facing names, and should be written against PROJECT_ROLE_ID for deterministic joins with dependent assignment and history tables.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

• FND_MENUS — joined on MENU_ID, supplies the menu definition tied to the role type.
• PER_JOBS — joined on DEFAULT_JOB_ID, supplies the default job.
• OKE_COMPILED_ACCESS_RULES — joined on ROLE_ID, the compiled access-rule table that references project role types.
• OKE_K_ACCESS_RULES — joined on ROLE_ID, the source access-rule definitions.
• PA_PROJECT_PLAYERS — joined on PROJECT_ROLE_TYPE, links role types to project participants.
• PA_PROJECT_ASSIGNMENTS and PA_RESOURCE_ASSIGNMENTS — joined on PROJECT_ROLE_ID, the transactional staffing records.
• PA_PROJECT_ROLE_TYPES_TL — the translation table, joined on PROJECT_ROLE_ID, holding language-specific names and descriptions.
• PA_ROLE_PROFILE_LINES — joined on PROJECT_ROLE_ID, linking role types to role profiles.