Results for “jtf_auth_acct_role_maps”

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

Overview

JTF_AUTH_ACCT_ROLE_MAPS is a CRM Foundation (JTF) authorization mapping table in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the relationship between a type of user account, a security principal (role), and an authentication domain. In practice, the table answers the question: for a given account type within a given application domain, which principal (role) is granted? This makes it a core component of the JTF authorization model that underpins CRM applications and any module relying on JTF security principals and domains.

The ETRM metadata classifies this object, using a heuristic Data Vault classification mined from its foreign key structure, as a link table. This is a modeling suggestion rather than a physical implementation statement: the table does not carry its own descriptive business attributes of a role or domain, but instead resolves a many-to-many style association among account types, domains, and principals. Its primary key is JTF_AUTH_ACCT_ROLE_MAPS_PK, defined on the surrogate column JTF_AUTH_ACCT_ROLE_MAPS_ID.

Key Information Stored

The most significant columns in this table are the following, all drawn from the documented 12.2.2 physical schema (12 columns, owner JTF):

• JTF_AUTH_ACCT_ROLE_MAPS_ID — surrogate primary key; uniquely identifies each mapping row. Also secured by unique index JTF_AUTH_ACCT_ROLE_MAPS_U2.
• ACCOUNT_TYPE — the category of user to which the mapping applies; part of the business-key candidate unique index.
• JTF_AUTH_DOMAIN_ID — foreign key to JTF_AUTH_DOMAINS_B; identifies the authentication/application domain in which the mapping is valid.
• JTF_AUTH_PRINCIPAL_ID — foreign key to JTF_AUTH_PRINCIPALS_B; identifies the role or principal granted.
• STATUS_FLAG — indicates whether the mapping is currently active or inactive.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; supports multi-org / data security partitioning of the mapping row.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM layer to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit and provenance information.

The business-key candidate is unique index JTF_AUTH_ACCT_ROLE_MAPS_U1 over (ACCOUNT_TYPE, JTF_AUTH_DOMAIN_ID, JTF_AUTH_PRINCIPAL_ID), which means a given account type can be mapped to a specific principal only once per domain. This is the distinguishing structural fact of the table: the surrogate JTF_AUTH_ACCT_ROLE_MAPS_ID is the technical key, while the U1 combination is the logical uniqueness constraint.

Common Use Cases and Queries

Typical uses revolve around resolving role assignments for account types within domains, validating the security configuration, and reporting on authorization coverage. A representative query joins the mapping to its dimension tables:

• Resolve all principals for a given domain:

  SELECT m.ACCOUNT_TYPE, p.PRINCIPAL_NAME, d.DOMAIN_NAME, m.STATUS_FLAG
  FROM   JTF.JTF_AUTH_ACCT_ROLE_MAPS m,
         JTF.JTF_AUTH_PRINCIPALS_B  p,
         JTF.JTF_AUTH_DOMAINS_B     d
  WHERE  m.JTF_AUTH_PRINCIPAL_ID = p.JTF_AUTH_PRINCIPAL_ID
  AND    m.JTF_AUTH_DOMAIN_ID    = d.JTF_AUTH_DOMAIN_ID
  AND    m.STATUS_FLAG           = 'Y';
  

• Audit mapping uniqueness and detect duplicate account-type/domain/principal combinations against unique index U1.
• Trace which roles are reachable from a given account type across all domains.
• Filter by SECURITY_GROUP_ID when reporting within a specific operating unit or security group.

Because the table is a link, reporting is most useful when joined outward to the principal and domain entities rather than read in isolation.

Related Objects

The following related objects are documented through primary and foreign key relationships:

• JTF_AUTH_PRINCIPALS_B — referenced via JTF_AUTH_PRINCIPAL_ID; holds the principal/role definition.
• JTF_AUTH_DOMAINS_B — referenced via JTF_AUTH_DOMAIN_ID; holds the authentication domain definition.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs multi-org data security.
• JTF_AUTH_ACCT_ROLE_MAPS_PK — the primary key constraint on JTF_AUTH_ACCT_ROLE_MAPS_ID.
• JTF_AUTH_ACCT_ROLE_MAPS_U1 / _U2 — unique indexes enforcing the business key and surrogate key respectively.

Together these objects form the JTF authorization mapping chain: account type to principal, scoped by domain and secured by security group.