Results for “jtf_auth_domains_b”

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

Overview

The JTF_AUTH_DOMAINS_B table resides in the JTF schema and belongs to the CRM Foundation product family (JTF) within Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the domains over which roles or permissions are granted to a principal. In the Oracle EBS authorization model, a domain acts as a scoping construct: a role or permission is not granted globally but for a specific domain, and domains may themselves roll up into a parent domain, forming a hierarchy. This table is therefore a foundational element of the CRM Foundation security framework that governs access to CRM objects and data.

From a Data Vault modeling perspective (a heuristic classification mined from the foreign key structure), JTF_AUTH_DOMAINS_B is best characterized as a hub. Its primary key JTF_AUTH_DOMAIN_ID serves as the business key, and multiple dependent tables reference it via foreign keys, which is the classic signature of a hub entity. It also carries a self-referencing foreign key, which supports the parent-child hierarchy of domains.

The table is edition-aware in 12.2.2, as evidenced by the ZD_EDITION_NAME column and its inclusion in both unique indexes. This reflects the Edition-Based Redefinition (EBR) architecture introduced in Release 12.2, which allows online patching of the underlying objects.

Key Information Stored

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

• JTF_AUTH_DOMAIN_ID — the surrogate primary key (JTF_AUTH_DOMAIN_PK) that uniquely identifies each authorization domain.
• DOMAIN_NAME — the human-readable name of the domain; this is a business-key candidate (unique index JTF_AUTH_DOMAINS_B_U2).
• PARENT_DOMAIN_ID — a self-referencing foreign key that designates the parent domain, enabling hierarchical grouping of domains.
• APPLICATION_ID — a foreign key to FND_APPLICATION that scopes the domain to a specific EBS application (for example, a CRM module).
• DOMAIN_DESC_ID — a foreign key to JTF_AUTH_DOMAINS_TL, linking to translated domain descriptions.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS that ties the domain to a security group context.
• OBJECT_VERSION_NUMBER — used for optimistic locking and concurrency control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns maintained by the Who columns framework.
• ZD_EDITION_NAME — the edition identifier supporting Edition-Based Redefinition in Release 12.2.

Both unique indexes — JTF_AUTH_DOMAINS_B_U1 (JTF_AUTH_DOMAIN_ID, ZD_EDITION_NAME) and JTF_AUTH_DOMAINS_B_U2 (DOMAIN_NAME, ZD_EDITION_NAME) — include the edition column, confirming that uniqueness is enforced per edition. Note that DOMAIN_NAME is not the primary key; the surrogate JTF_AUTH_DOMAIN_ID is, while DOMAIN_NAME is the documented alternate business key.

Common Use Cases and Queries

Typical uses involve determining which domain a role, permission, or principal mapping is scoped to, and resolving the domain hierarchy. A common query joins the domain table to the principal mapping table:

• Resolve domain for a principal mapping: SELECT d.DOMAIN_NAME, p.* FROM JTF_AUTH_PRINCIPAL_MAPS p, JTF_AUTH_DOMAINS_B d WHERE p.JTF_AUTH_DOMAIN_ID = d.JTF_AUTH_DOMAIN_ID;
• Retrieve the domain hierarchy: a self-join on PARENT_DOMAIN_ID returns parent and child domains: SELECT c.DOMAIN_NAME, p.DOMAIN_NAME AS PARENT FROM JTF_AUTH_DOMAINS_B c, JTF_AUTH_DOMAINS_B p WHERE c.PARENT_DOMAIN_ID = p.JTF_AUTH_DOMAIN_ID;
• Translation reporting: join to JTF_AUTH_DOMAINS_TL on DOMAIN_DESC_ID to display descriptions in the session language.
• Application-scoped reporting: join to FND_APPLICATION on APPLICATION_ID to list domains by application and understand which CRM modules are affected.
• Read-permission auditing: join to JTF_AUTH_READ_PERMS on JTF_AUTH_DOMAIN_ID to enumerate the read permissions attached to each domain.

These patterns support security reviews, access certification, and troubleshooting of CRM authorization errors.

Related Objects

The following objects reference or are referenced by JTF_AUTH_DOMAINS_B through documented foreign key relationships:

• FND_APPLICATION — referenced via APPLICATION_ID; identifies the owning application.
• JTF_AUTH_DOMAINS_TL — translation table joined on DOMAIN_DESC_ID; holds language-specific descriptions.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; provides the security group context.
• JTF_AUTH_ACCT_ROLE_MAPS — references this table via JTF_AUTH_DOMAIN_ID; maps accounts to roles within a domain.
• JTF_AUTH_PRINCIPAL_MAPS — references this table via JTF_AUTH_DOMAIN_ID; associates principals with domains.
• JTF_AUTH_READ_PERMS — references this table via JTF_AUTH_DOMAIN_ID; defines read permissions per domain.
• JTF_AUTH_DOMAINS_B (self) — referenced via PARENT_DOMAIN_ID; establishes the parent-child domain hierarchy.

These relationships confirm the table's central role as the hub of the CRM Foundation authorization model, with dependent mapping and permission tables radiating from it.