Search Results jtf_auth_permissions_uk1

Overview

The JTF_AUTH_PERMISSIONS_B table is a core repository within the Oracle E-Business Suite CRM Foundation (JTF) module, specifically designed for the Authorization (Auth) framework. It serves as the master definition table for all granular permissions across the system. A permission is a simple string identifier that represents a discrete right or action a user can be authorized to perform, such as accessing a specific function or modifying a particular type of data. The table's primary role is to provide a normalized, partitioned catalog of these permission identifiers, which are then associated with roles and users to build a comprehensive security model. Its design, partitioned by application ID, supports scalable, multi-application hosting environments within the EBS ecosystem.

Key Information Stored

The table stores the fundamental attributes that define a system permission. The primary surrogate key is the JTF_AUTH_PERMISSION_ID. The most critical business key is the PERMISSION_NAME column, which holds the unique string identifier for the permission (e.g., 'VIEW_CUSTOMER', 'APPROVE_ORDER'). This column is enforced by a unique constraint (JTF_AUTH_PERMISSIONS_UK1). The APPLICATION_ID column links the permission to a specific Oracle EBS application via the FND_APPLICATION table, enabling partitioning and logical segregation. The PERMISSION_DESC_ID is a foreign key to the corresponding translated description in the JTF_AUTH_PERMISSIONS_TL (Translation) table, supporting multilingual implementations.

Common Use Cases and Queries

This table is central to security administration and auditing. Common use cases include auditing all permissions defined for a specific application, troubleshooting role-based access issues, and generating security reports. A typical query involves joining with the translation table to retrieve human-readable descriptions. For example, to find all permissions for the CRM application (application_id=660), one might use:

• SELECT b.permission_name, tl.description FROM jtf_auth_permissions_b b, jtf_auth_permissions_tl tl WHERE b.application_id = 660 AND b.permission_desc_id = tl.permission_desc_id AND tl.language = USERENV('LANG');

Another critical pattern is identifying which roles grant a specific permission, which involves joining with the JTF_AUTH_ROLE_PERMS intersection table.

Related Objects

JTF_AUTH_PERMISSIONS_B is a central hub in the authorization schema with several key relationships, as documented by its foreign keys:

• FND_APPLICATION: Links via APPLICATION_ID to identify the owning application.
• JTF_AUTH_PERMISSIONS_TL: Links via PERMISSION_DESC_ID to retrieve translated descriptions.
• JTF_AUTH_READ_PERMS: Links via JTF_AUTH_PERMISSION_ID to define permissions for read-level access control.
• JTF_AUTH_ROLE_PERMS: Links via JTF_AUTH_PERMISSION_ID in this critical intersection table that assigns permissions to roles.
• JTF_DAC_ROLE_PERM_CRIT: Links via JTF_AUTH_PERMISSION_ID for defining Data Access Control (DAC) criteria attached to role-permission assignments.