Results for “jtf_auth_permissions_b”

50+ results




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

Overview

JTF_AUTH_PERMISSIONS_B is a core CRM Foundation table in the JTF schema that stores permission definitions used throughout the Oracle E-Business Suite authorization framework. Each row represents a single permission — expressed as a simple string identifier — associated with an authorization domain. The table is designed to partition permissions by APPLICATION_ID, allowing hosting providers to segregate permission data by application context. In Oracle EBS 12.1.1 and 12.2.2, this object underpins the role-based and permission-based access control model shared by CRM modules and other JTF-dependent applications.

The ETRM metadata classifies this object as hub-leaning under a heuristic Data Vault assessment. As a modeling suggestion, this indicates the table behaves primarily as a hub: a stable, business-key-driven registry of permission entities referenced by numerous dependent structures, rather than a transactional or descriptive satellite. Its role as a central reference point is consistent with the multiple inbound foreign keys from read, role, and DAC criterion tables.

Key Information Stored

The documented physical schema comprises 16 columns. The most significant are:

Common Use Cases and Queries

Typical scenarios include auditing the permission catalog for a given application, resolving role-to-permission grants, and diagnosing access failures. A common pattern joins the base table to its translation table:

  • Listing permissions for an application: SELECT p.permission_name, t.description FROM jtf_auth_permissions_b p, jtf_auth_permissions_tl t WHERE p.permission_desc_id = t.permission_desc_id AND p.application_id = :app_id AND t.language = USERENV('LANG');
  • Resolving roles to permissions: join JTF_AUTH_ROLE_PERMS to this table on JTF_AUTH_PERMISSION_ID to enumerate every permission granted to a role.
  • DAC evaluation: filter on IS_DAC_FLAG = 'Y' and join JTF_DAC_ROLE_PERM_CRIT for criteria-driven access decisions.
  • Security-group scoping: constrain results by SECURITY_GROUP_ID for multi-tenant reporting.
  • Lookup by business key: query on PERMISSION_NAME (the JTF_AUTH_PERMISSIONS_UK1 key) when integrating external authorization configurations.

Related Objects

  • JTF_AUTH_PERMISSIONS_TL — translation table joined via PERMISSION_DESC_ID.
  • FND_APPLICATION — referenced through APPLICATION_ID.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
  • JTF_AUTH_ROLE_PERMS — maps roles to permissions via JTF_AUTH_PERMISSION_ID.
  • JTF_AUTH_READ_PERMS — read-permission grants referencing JTF_AUTH_PERMISSION_ID.
  • JTF_DAC_ROLE_PERM_CRIT — DAC role-permission criteria referencing JTF_AUTH_PERMISSION_ID.