Search Results jtf_auth_domains_b

Overview

The JTF_AUTH_DOMAINS_B table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module, serving as the master definition table for authorization domains. It is central to the application's security and data access control framework. The table defines the specific context or scope—such as an organization, territory, or custom business area—for which a security role or permission is granted to a user or principal. Domains can be organized hierarchically, as a domain may belong to a parent domain, enabling the creation of complex, nested security structures that mirror organizational reporting lines or business hierarchies. This object is fundamental for implementing fine-grained, context-aware access control within the CRM and related EBS applications.

Key Information Stored

The table stores the structural and descriptive metadata for each security domain. Its primary columns, as indicated by the provided constraints, include the unique identifier JTF_AUTH_DOMAIN_ID (primary key) and the DOMAIN_NAME (unique key), which is the internal name for the domain. The DOMAIN_DESC_ID (unique key) is a foreign key to the corresponding translated description in the JTF_AUTH_DOMAINS_TL table, supporting multilingual implementations. The hierarchical relationship is managed via the PARENT_DOMAIN_ID column, which self-references the same table to point to a parent domain. Furthermore, the APPLICATION_ID column links the domain to a specific EBS application via the FND_APPLICATION table, scoping the domain's relevance.

Common Use Cases and Queries

This table is primarily accessed for security administration, auditing, and troubleshooting access issues. A common operational query is to list all domains within a specific hierarchy to understand security inheritance. For example, to find all child domains under a specific parent domain:

• SELECT child.DOMAIN_NAME FROM jtf_auth_domains_b child CONNECT BY PRIOR child.jtf_auth_domain_id = child.parent_domain_id START WITH child.parent_domain_id = <PARENT_ID>;

Another frequent use case is to identify all roles or principals assigned to a particular domain for review or cleanup, which involves joining to mapping tables like JTF_AUTH_ACCT_ROLE_MAPS. Administrators may also query the table to validate domain setup before deploying new security profiles or when diagnosing "Insufficient Privileges" errors by verifying the domain context of a user's assigned permissions.

Related Objects

The JTF_AUTH_DOMAINS_B table has integral relationships with several other security and foundation tables, as documented by its foreign key constraints:

• Self-Reference (Hierarchy): JTF_AUTH_DOMAINS_B.PARENT_DOMAIN_ID → JTF_AUTH_DOMAINS_B.JTF_AUTH_DOMAIN_ID
• Application Context: JTF_AUTH_DOMAINS_B.APPLICATION_ID → FND_APPLICATION.APPLICATION_ID
• Translated Descriptions: JTF_AUTH_DOMAINS_TL.DOMAIN_DESC_ID → JTF_AUTH_DOMAINS_B.DOMAIN_DESC_ID
• Role Assignments: JTF_AUTH_ACCT_ROLE_MAPS.JTF_AUTH_DOMAIN_ID → JTF_AUTH_DOMAINS_B.JTF_AUTH_DOMAIN_ID
• Principal Assignments: JTF_AUTH_PRINCIPAL_MAPS.JTF_AUTH_DOMAIN_ID → JTF_AUTH_DOMAINS_B.JTF_AUTH_DOMAIN_ID
• Read Permissions: JTF_AUTH_READ_PERMS.JTF_AUTH_DOMAIN_ID → JTF_AUTH_DOMAINS_B.JTF_AUTH_DOMAIN_ID

These relationships underscore the table's role as a central hub linking domains to the actual grants of roles, permissions, and principals within the authorization system.