Search Results jtf_auth_acct_role_maps




Overview
Explore in AI Chat

Overview

The JTF_AUTH_ACCT_ROLE_MAPS table is a core authorization mapping table within the Oracle E-Business Suite CRM Foundation (JTF) module. It functions as a central repository that defines the relationship between a type of user (principal), a specific security role, and an application domain. This mapping is fundamental to the role-based access control (RBAC) framework in EBS, enabling the system to determine the appropriate set of permissions and responsibilities assigned to different user classifications. Its existence is critical for enforcing data security and functional access across CRM applications in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to store unique mapping records, each identified by a system-generated surrogate key, JTF_AUTH_ACCT_ROLE_MAPS_ID. The essential foreign key columns define the specific relationship for each entry. The JTF_AUTH_PRINCIPAL_ID column references a user or account type defined in JTF_AUTH_PRINCIPALS_B. The ROLE_CODE (implied by the description and common naming conventions) identifies the specific security role being granted. Finally, the JTF_AUTH_DOMAIN_ID column, referencing JTF_AUTH_DOMAINS_B, scopes this role assignment to a particular application or functional domain, ensuring that authorizations are contextually relevant.

Common Use Cases and Queries

This table is primarily accessed for security administration and audit reporting. A common operational use case involves querying all role assignments for a specific user type or within a particular application domain to verify or troubleshoot access issues. For instance, administrators may run a query to list all roles mapped to a principal for audit purposes. Conversely, identifying all principals assigned a specific role is essential for understanding the security footprint before modifying that role's underlying permissions. Sample reporting SQL often joins this mapping table to its referenced principal and domain tables to produce human-readable reports.

  • List all role mappings for a specific principal ID: SELECT * FROM jtf_auth_acct_role_maps WHERE jtf_auth_principal_id = <PRINCIPAL_ID>;
  • Report on all mappings with descriptive names: SELECT prin.principal_name, maps.role_code, dom.domain_name FROM jtf_auth_acct_role_maps maps, jtf_auth_principals_b prin, jtf_auth_domains_b dom WHERE maps.jtf_auth_principal_id = prin.jtf_auth_principal_id AND maps.jtf_auth_domain_id = dom.jtf_auth_domain_id;

Related Objects

The JTF_AUTH_ACCT_ROLE_MAPS table maintains defined foreign key relationships with two other core authorization tables, forming a key part of the security data model. It references the JTF_AUTH_DOMAINS_B table via the JTF_AUTH_DOMAIN_ID column to link each mapping to a valid application domain. It also references the JTF_AUTH_PRINCIPALS_B table via the JTF_AUTH_PRINCIPAL_ID column to link each mapping to a defined user or account principal. The primary key constraint, JTF_AUTH_ACCT_ROLE_MAPS_PK, on the JTF_AUTH_ACCT_ROLE_MAPS_ID column ensures each mapping record is uniquely identifiable, which is referenced by other application logic and potentially by user-created role assignment APIs.