Search Results jtf_auth_maps_sources_uk1

Overview

JTF_AUTH_MAPS_SOURCES is a CRM Foundation (JTF) application table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the origin, or source, information behind user-to-role assignments. Its documented purpose is to record where a given role assignment originated: because a single role can be granted to a user through more than one originating source, the authorization model separates the principal mapping itself from the set of sources that justify it. The table's description states that one row in JTF_AUTH_PRINCIPAL_MAPS may correspond to one or more rows in JTF_AUTH_MAPS_SOURCES, making this a dependent detail table rather than the primary mapping table.

Under the heuristic Data Vault classification mined from its foreign key structure, the table is tagged as standalone. In Data Vault modeling terms this suggests it behaves primarily as a satellite-like detail store attached to a parent mapping, though the absence of a strongly modeled parent link in the mined classification means it should be treated as an independent descriptive table until the surrounding authorization model is mapped. Either way, it holds descriptive and historical attribution data around a core authorization relationship.

Key Information Stored

The documented physical schema for 12.2.2 shows 13 columns owned by JTF. The most significant are:

• JTF_AUTH_MAPS_SOURCE_ID — surrogate identifier for the source row and part of the unique index JTF_AUTH_MAPS_SOURCES_U1 (with ZD_EDITION_NAME). This is the technical primary key.
• JTF_AUTH_PRINCIPAL_MAPPING_ID — the foreign reference back to the parent user-role mapping in JTF_AUTH_PRINCIPAL_MAPS. It anchors each source record to its authorization assignment.
• OWNERTABLE_NAME — the name of the owning entity table from which the source originates; a business-key component.
• OWNERTABLE_KEY — the primary key value of the owning entity row, identifying the specific source record; also a business-key component.
• APPLICATION_ID — the Oracle Applications application that owns or produced the source row, used for multi-application scoping.
• SECURITY_GROUP_ID — the security group context; documented as a foreign key referencing FND_SECURITY_GROUPS, controlling data visibility across operating units or groups.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last changed the row.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• ZD_EDITION_NAME — the editioning column introduced with EBS 12.2 online patching (Edition-Based Redefinition), participating in both unique indexes.

The documented business-key candidate is the unique index JTF_AUTH_MAPS_SOURCES_UK1, composed of OWNERTABLE_NAME, OWNERTABLE_KEY, and JTF_AUTH_PRINCIPAL_MAPPING_ID. A second unique index, U2, extends that triple with ZD_EDITION_NAME for the 12.2 editioning model. Distinguishing the surrogate JTF_AUTH_MAPS_SOURCE_ID from these business-key candidates is important when writing idempotent data loads.

Common Use Cases and Queries

Typical use cases center on authorization auditing and diagnostics: determining how a user acquired a role (direct grant versus an owning entity such as an HR assignment or a functional administrator task), and reporting the provenance distribution of role grants across an enterprise. A representative join resolves the parent mapping while filtering by source table:

SELECT m.jtf_auth_principal_mapping_id,
       s.ownertable_name,
       s.ownertable_key,
       s.application_id
FROM   jtf_auth_principal_maps  m,
       jtf_auth_maps_sources    s
WHERE  m.jtf_auth_principal_mapping_id = s.jtf_auth_principal_mapping_id
AND    s.ownertable_name = :owner_table;

Aggregate queries grouping by OWNERTABLE_NAME and APPLICATION_ID reveal which mechanisms are granting roles most frequently, useful during security reviews. Because SECURITY_GROUP_ID references FND_SECURITY_GROUPS, reporting can be scoped to a security group to respect multi-org visibility. Auditors frequently filter on CREATION_DATE and LAST_UPDATED_BY to track when and by whom a source attribution changed.

Related Objects

• JTF_AUTH_PRINCIPAL_MAPS — the parent user-role mapping table; joined on JTF_AUTH_PRINCIPAL_MAPPING_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, governing data visibility.
• OWNERTABLE_NAME / OWNERTABLE_KEY targets — dynamic references to the actual source entity tables identified by name and key at runtime; these vary by implementation.
• JTF_AUTH_* authorization family — the broader JTF authorization tables that share the principal mapping model.
• FND_USER / FND_USER_ROLES — user and role derivation objects that consume the resulting authorization data.

Oracle Proprietary and Confidential Information.