Results for “jtf_auth_role_perms”

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

Overview

JTF_AUTH_ROLE_PERMS is a CRM Foundation (JTF) authorization table in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a role-to-permission mapping table: each row groups a role (a specialized type of principal stored in JTF_AUTH_PRINCIPALS_B) to a permission (stored in JTF_AUTH_PERMISSIONS_B). Permissions assigned through this table may be positive or negative, determined by the POSITIVE_FLAG column. This design allows Oracle EBS to support both grants and explicit denials within the same authorization model, which is critical for role-based access control (RBAC) in CRM and shared JTF-based application flows.

From a Data Vault modeling perspective, the ETRM metadata classifies this object as a link table. This is a heuristic classification: the table primarily resolves many-to-many relationships between roles and permissions, rather than acting as a standalone hub of business entities or a descriptive satellite.

Key Information Stored

The table contains 14 documented columns. The most operationally significant columns are:

• JTF_AUTH_ROLE_PERMISSION_ID — the surrogate primary key, enforced by the JTF_AUTH_ROLE_PERMS_PK constraint. It also participates in the unique index JTF_AUTH_ROLE_PERMS_U1, along with ZD_EDITION_NAME, making it a business-key candidate for edition-aware lookups.
• JTF_AUTH_PRINCIPAL_ID — foreign key to JTF_AUTH_PRINCIPALS_B, identifying the role being granted or denied a permission.
• JTF_AUTH_PERMISSION_ID — foreign key to JTF_AUTH_PERMISSIONS_B, identifying the specific permission.
• APPLICATION_ID — foreign key to FND_APPLICATION, scoping the permission assignment to a specific EBS application.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-organization or security-group partitioning of the assignment.
• POSITIVE_FLAG — indicates whether the mapping represents a positive grant or a negative (denial) permission.
• OWNERBASED_FLAG — indicates whether the permission is owner-based, typically relevant to CRM record-level authorization.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each row.
• ZD_EDITION_NAME — supports edition-based redefinition (EBR) in 12.2.x online patching environments.

Common Use Cases and Queries

Typical scenarios include auditing role assignments, diagnosing authorization failures, and reporting on granted versus denied permissions. A common pattern joins the three core tables:

• Resolve roles and permissions for a principal: join JTF_AUTH_ROLE_PERMS to JTF_AUTH_PRINCIPALS_B on JTF_AUTH_PRINCIPAL_ID and to JTF_AUTH_PERMISSIONS_B on JTF_AUTH_PERMISSION_ID.
• Filter negative permissions: SELECT * FROM JTF.JTF_AUTH_ROLE_PERMS WHERE POSITIVE_FLAG = 'N';
• Scope by application: join to FND_APPLICATION on APPLICATION_ID to report permissions per EBS module.
• Partition by security group: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID.
• Edition-aware queries in 12.2.2 should account for ZD_EDITION_NAME when running during online patching cycles.

Reporting use cases include producing role entitlement matrices, identifying over-permissioned roles, and troubleshooting CRM access issues.

Related Objects

The most significant related objects, based on documented foreign keys, are:

• JTF_AUTH_PRINCIPALS_B — joined via JTF_AUTH_PRINCIPAL_ID; holds the role/principal definition.
• JTF_AUTH_PERMISSIONS_B — joined via JTF_AUTH_PERMISSION_ID; holds permission definitions.
• FND_APPLICATION — joined via APPLICATION_ID; scopes assignments to an EBS application.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; provides security-group partitioning.

These relationships make JTF_AUTH_ROLE_PERMS a central link within the JTF authorization model, connecting principals, permissions, applications, and security groups.