Search Results pa_role_controls_u1

Overview

PA.PA_ROLE_CONTROLS is a transactional configuration table in the Oracle E-Business Suite Projects (PA) schema. It stores the association between a project role and the individual role controls granted to that role. In practice, this table implements the authorization matrix that determines which functional capabilities a given project role may exercise within Oracle Projects and its self-service pages. The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the PA schema, with FND design data registered as PA.PA_ROLE_CONTROLS.

From a dimensional modeling perspective, the mined relationship data classifies this object as standalone, which suggests a Data Vault treatment as a hub-and-satellite or reference construct rather than as a dependent child of a rigid hierarchy. Because the table holds descriptive state tied to a business key pair, it may alternatively be modeled as a satellite attached to the project role and role control hubs.

Key Information Stored

The table contains nine documented columns. The two business-key columns are PROJECT_ROLE_ID, a number that identifies the project role receiving the control, and ROLE_CONTROL_CODE, a VARCHAR2(30) that identifies the specific control granted. Together these form the composite primary key PA_ROLE_CONTROLS_PK and the unique business-key index PA_ROLE_CONTROLS_U1, which in the 12.2.2 ETRM documentation also includes ZD_EDITION_NAME, reflecting the edition-based redefinition architecture introduced in that release. ZD_EDITION_NAME is the remaining documented column and supports multiple editions of the same logical row.

RECORD_VERSION_NUMBER is a sequence number used for the optimistic locking strategy typical of self-service applications, allowing concurrent updates to be detected. The remaining columns are standard WHO audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These support audit tracking and are generally populated by the Oracle Forms and OAF frameworks rather than by application logic directly.

Common Use Cases and Queries

Typical usage involves security and authorization reporting, role setup validation, and migration verification. A common query pattern lists all controls granted to a specific project role:

• Selecting controls for one role: SELECT ROLE_CONTROL_CODE FROM PA.PA_ROLE_CONTROLS WHERE PROJECT_ROLE_ID = :role_id;
• Identifying roles that hold a particular control: SELECT PROJECT_ROLE_ID FROM PA.PA_ROLE_CONTROLS WHERE ROLE_CONTROL_CODE = :code;
• Verifying setup completeness by counting controls per role, grouped by PROJECT_ROLE_ID.
• Auditing changes using LAST_UPDATE_DATE and LAST_UPDATED_BY to detect recent authorization modifications.

Because the table is standalone in the FK data, reporting joins must typically be constructed manually against project role and role control reference tables rather than through enforced foreign keys.

Related Objects

The ETRM dependency data states that PA.PA_ROLE_CONTROLS does not reference any database object and is referenced by the APPS synonym PA_ROLE_CONTROLS. Consequently, join relationships are logical rather than FK-enforced. Significant related objects include:

• PA.PA_PROJECT_ROLES, joined on PA_ROLE_CONTROLS.PROJECT_ROLE_ID = PA_PROJECT_ROLES.PROJECT_ROLE_ID.
• The role control reference table, joined on ROLE_CONTROL_CODE to obtain control descriptions.
• APPS.PA_ROLE_CONTROLS, the synonym commonly used in custom queries.
• Project role assignment tables in PA that consume these roles for user authorization.
• FND security and role configuration objects that govern the broader EBS authorization model.