Results for “jtf_auth_read_perms”

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

Overview

JTF_AUTH_READ_PERMS is a denormalized authorization mapping table residing in the JTF (CRM Foundation) schema of Oracle E-Business Suite. Its documented purpose is to map every user principal (JTF_AUTH_PRINCIPAL_NAME) to a permission (JTF_AUTH_PERMISSION_NAME) within a given authorization domain (JTF_AUTH_DOMAIN_NAME). It serves as a flattened, high-performance read layer for the CRM Foundation authorization model, allowing applications to resolve "who can read what" without traversing the fully normalized principal/permission/domain hierarchy stored in the companion _B tables.

From a Data Vault modeling perspective, the mined FK structure suggests this object behaves as a link table. It records relationships among three business entities — principals, permissions, and domains — rather than acting as a standalone hub (which typically holds a single business key) or a satellite (which stores descriptive attributes over time). This classification is a heuristic suggestion derived from the foreign key topology, not an enforced Oracle designation.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• JTF_AUTH_READ_PERMISSION_ID — surrogate primary key, enforced by JTF_AUTH_READ_PERMS_PK and supported by the unique index JTF_AUTH_PERMS_U1. This is the single-column business-key candidate documented for the table.
• JTF_AUTH_PRINCIPAL_NAME — denormalized user/principal identifier; the human-readable counterpart to the foreign key.
• JTF_AUTH_PRINCIPAL_ID — foreign key to JTF_AUTH_PRINCIPALS_B, uniquely identifying the principal.
• JTF_AUTH_PERMISSION_NAME — denormalized permission label granted to the principal.
• JTF_AUTH_PERMISSION_ID — foreign key to JTF_AUTH_PERMISSIONS_B.
• JTF_AUTH_DOMAIN_NAME — denormalized domain label scoping the grant.
• JTF_AUTH_DOMAIN_ID — foreign key to JTF_AUTH_DOMAINS_B.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org / row-level security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit lineage.

The dual presence of ID and NAME columns is deliberate: the IDs preserve referential integrity and join performance, while the NAME columns eliminate joins for the most common authorization lookups.

Common Use Cases and Queries

Typical reporting and diagnostic uses include auditing which principals hold a given permission, and listing all permissions held by a principal within a domain. Because the table is denormalized, name-based queries require no joins:

• Resolve a principal's permissions: SELECT JTF_AUTH_PERMISSION_NAME FROM JTF.JTF_AUTH_READ_PERMS WHERE JTF_AUTH_PRINCIPAL_NAME = :p AND JTF_AUTH_DOMAIN_NAME = :d.
• Audit permission holders: SELECT JTF_AUTH_PRINCIPAL_NAME FROM JTF.JTF_AUTH_READ_PERMS WHERE JTF_AUTH_PERMISSION_NAME = :perm AND SECURITY_GROUP_ID = :sg.
• Cross-check denormalized names against the _B tables to detect drift after bulk permission changes.

Because SECURITY_GROUP_ID governs row-level visibility, queries executed as a non-privileged user should honor the active security group, or the results may over-report grants across organizations.

Related Objects

• JTF_AUTH_PRINCIPALS_B — joined on JTF_AUTH_READ_PERMS.JTF_AUTH_PRINCIPAL_ID; source of principal definitions.
• JTF_AUTH_PERMISSIONS_B — joined on JTF_AUTH_READ_PERMS.JTF_AUTH_PERMISSION_ID; source of permission definitions.
• JTF_AUTH_DOMAINS_B — joined on JTF_AUTH_READ_PERMS.JTF_AUTH_DOMAIN_ID; defines the authorization domain.
• FND_SECURITY_GROUPS — joined on JTF_AUTH_READ_PERMS.SECURITY_GROUP_ID; enforces data partitioning.
• JTF_AUTH_READ_PERMS_PK / JTF_AUTH_PERMS_U1 — the primary key constraint and unique index defining row identity.