Search Results pa_role_controls




Overview
Explore in AI Chat

Overview

PA_ROLE_CONTROLS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the controls defined against project roles. Each row associates a specific control code with a project role, forming the authorization and behaviour rules that govern what a role is permitted to do within Oracle Projects. The table is owned by the PA schema and holds a VALID status in the ETRM object registry.

The primary key is PA_ROLE_CONTROLS_PK, defined over the composite of PROJECT_ROLE_ID and ROLE_CONTROL_CODE. The mined Data Vault classification for this object is standalone. As a modeling suggestion, this indicates the table does not participate in a classic hub-and-satellite pattern through the documented foreign-key structure; it is better treated as a static reference or a link-style association between project roles and control codes rather than a transactional hub. The documented physical schema lists nine columns and a unique index, PA_ROLE_CONTROLS_U1, over PROJECT_ROLE_ID, ROLE_CONTROL_CODE, and ZD_EDITION_NAME.

Key Information Stored

The most significant columns are the two business-key attributes and the standard EBS audit and edition columns:

  • PROJECT_ROLE_ID — Identifier of the project role to which the control applies. It is part of the composite primary key and the first business-key candidate in PA_ROLE_CONTROLS_U1.
  • ROLE_CONTROL_CODE — Code identifying the individual control granted or restricted on the role. It is the second component of the primary key and of the unique index.
  • ZD_EDITION_NAME — Edition discriminator used by the EBS editioning framework; its inclusion in PA_ROLE_CONTROLS_U1 makes the role-control pairing unique per edition.
  • RECORD_VERSION_NUMBER — Optimistic locking counter that increments on each update.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when the control assignment was created and by which user.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification, the responsible user, and the login context.

The surrogate-style composite key (PROJECT_ROLE_ID, ROLE_CONTROL_CODE) is distinct from the business-key candidate captured by the unique index, which additionally qualifies the pair with ZD_EDITION_NAME. No descriptive control definition columns are documented within this table; the control semantics are resolved through the code rather than stored inline.

Common Use Cases and Queries

Typical uses revolve around role provisioning, security review, and audit reporting. A common pattern enumerates all controls assigned to a given role:

  • SELECT project_role_id, role_control_code FROM pa_role_controls WHERE project_role_id = :role_id;
  • Reverse lookup to find every role that carries a specific control: SELECT project_role_id FROM pa_role_controls WHERE role_control_code = :control_code;
  • Audit trail reporting using creation and update columns: SELECT project_role_id, role_control_code, creation_date, created_by, last_update_date, last_updated_by FROM pa_role_controls ORDER BY last_update_date DESC;
  • Edition-scoped reconciliation against PA_ROLE_CONTROLS_U1 to detect duplicate or stale role-control assignments.

Because controls drive role behaviour, these queries are frequently embedded in access-certification reports, segregation-of-duties checks, and configuration comparison scripts between environments.

Related Objects

The strongest documented relationship is through the composite key columns, which reference the project role definition and the control definition respectively. The most significant related objects are:

  • PA_PROJECT_ROLES — Joined on PROJECT_ROLE_ID; provides the role definition and descriptive attributes.
  • Control lookup table — Resolves ROLE_CONTROL_CODE to the control description and category.
  • PA_ROLE_CONTROLS_PK — The primary key constraint enforcing uniqueness of the role-control pair.
  • PA_ROLE_CONTROLS_U1 — The unique index qualifying the pair by ZD_EDITION_NAME.
  • PA project security and role-assignment views — Depend on this table when presenting effective role capabilities.
  • PA role setup and configuration APIs — Insert, update, or delete rows here when roles are provisioned or modified.

As the metadata records a standalone Data Vault classification, no additional documented foreign-key links extend beyond these role and control associations.