Results for “principal_name”

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

Overview

JTF_AUTH_PRINCIPALS_B is a core foundation table in the JTF (CRM Foundation) product module of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores authorization principals, where a principal is defined as either a user or a role. When the principal represents a user, the IS_USER_FLAG column is set to 1 and USER_ID points to a record in FND_USER. When the principal represents a role, no user reference is populated. The APPLICATION_ID column is retained so that data can later be striped by application for hosting purposes, reflecting the multi-tenant design considerations of the CRM Foundation layer.

In Data Vault modeling terms, the mined foreign key structure classifies this object heuristically as a hub. The table holds the durable business keys that identify each principal, while descriptive and mapping detail is distributed to surrounding link and satellite tables. This classification is a modeling suggestion derived from the FK topology, not an enforced schema constraint.

Key Information Stored

The documented physical schema contains 15 columns in the JTF schema. The most significant are:

• JTF_AUTH_PRINCIPAL_ID — the surrogate primary key, enforced by JTF_AUTH_PRINCIPAL_B_PK, uniquely identifying each principal record.
• PRINCIPAL_NAME — the human-readable name of the user or role; this is a business-key candidate and participates in the unique index JTF_AUTH_PRINCIPALS_B_U2 (PRINCIPAL_NAME, IS_USER_FLAG, ZD_EDITION_NAME) and in JTF_AUTH_PRINCIPAL_UK1.
• IS_USER_FLAG — discriminator indicating whether the principal is a user (1) or a role (0).
• USER_ID — populated only when IS_USER_FLAG equals 1; points to the corresponding record in FND_USER.
• PRINCIPAL_DESC_ID — foreign key to JTF_AUTH_PRINCIPALS_TL, holding the translatable description; this is the second business-key candidate via JTF_AUTH_PRINCIPAL_UK2.
• APPLICATION_ID — application context used to stripe data for hosting deployments.
• DAC_ROLE_FLAG — indicates whether the principal functions as a DAC (data access control) role.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row visibility.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework for concurrent update detection.
• ZD_EDITION_NAME — editioning column supporting the EBS 12.2 online patching (Edition-Based Redefinition) architecture; it participates in both unique indexes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on virtually all EBS transactional and setup tables.

Common Use Cases and Queries

Administrators and developers query this table to resolve authorization identities, list all roles assigned within the CRM Foundation security model, and join principal identities to their permission definitions. A typical lookup resolving a user principal to FND_USER is:

• SELECT j.jtf_auth_principal_id, j.principal_name, u.user_name FROM jtf.jtf_auth_principals_b j, applsys.fnd_user u WHERE j.is_user_flag = 1 AND j.user_id = u.user_id;
• Reporting on role-only principals: SELECT * FROM jtf.jtf_auth_principals_b WHERE is_user_flag = 0;
• Resolving translatable descriptions: join PRINCIPAL_DESC_ID to JTF_AUTH_PRINCIPALS_TL.

Because the table functions as a hub, reporting solutions frequently use it as the anchoring dimension and join outward to mapping and permission tables to reconstruct the effective authorization graph.

Related Objects

The FK topology shows extensive downstream dependency, confirming the table's hub role:

• JTF_AUTH_PRINCIPALS_TL — the translation/description satellite, joined via PRINCIPAL_DESC_ID to JTF_AUTH_PRINCIPAL_ID.
• JTF_AUTH_PRINCIPAL_MAPS — hierarchy mapping, joining both JTF_AUTH_PRINCIPAL_ID (child) and JTF_AUTH_PARENT_PRINCIPAL_ID (parent) back to this table.
• JTF_AUTH_ACCT_ROLE_MAPS — maps accounts to roles via JTF_AUTH_PRINCIPAL_ID.
• JTF_AUTH_READ_PERMS and JTF_AUTH_ROLE_PERMS — define read and role-level permissions keyed by JTF_AUTH_PRINCIPAL_ID.
• JTF_DAC_ROLE_PERM_CRIT — data access control role permission criteria.
• JTF_UM_SUBSCRIPTIONS_B, JTF_UM_SUBSCRIPTION_ROLE, and JTF_UM_USERTYPE_ROLE — user management subscription and role assignment objects linking via AUTH_DELEGATION_ROLE_ID or PRINCIPAL_NAME.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID to scope row-level access.