Search Results jtf_auth_maps_sources_u1

Overview

JTF.JTF_AUTH_MAPS_SOURCES is a transactional table in the Oracle E-Business Suite application schema JTF (part of the CRM Foundation / JTF security infrastructure). It stores the source information associated with user-to-role mappings held in the parent table JTF_AUTH_PRINCIPAL_MAPS. In the Oracle EBS authorization model, a single role can be assigned to a user through more than one originating source — for example, directly, by user-type, or through another provisioning mechanism. Each entry in JTF_AUTH_PRINCIPAL_MAPS can therefore correspond to one or more rows in JTF_AUTH_MAPS_SOURCES, making this table the qualifying detail that records why and from where a given user-role mapping exists.

The table is classified as VALID and resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10. Under the heuristic Data Vault classification mined from its foreign-key structure, this object is modelled as a standalone table — it is neither a pure hub nor a pure link, although its business content behaves link-like, connecting a principal mapping to an owning source table record. When designing analytic or integration layers, treating JTF_AUTH_MAPS_SOURCES as a link/satellite construct between JTF_AUTH_PRINCIPAL_MAPS and arbitrary source tables is a reasonable modeling suggestion.

The object is documented in both release 12.1.1 and 12.2.2. In 12.2.2 the physical schema carries 13 columns and reflects the multi-tenant ZD_EDITION_NAME column, which participates in both unique indexes for edition-aware row filtering.

Key Information Stored

The most significant columns are the identifiers and source-locating attributes:

• JTF_AUTH_MAPS_SOURCE_ID (NUMBER 16) — the surrogate primary key of the row. It is the leading column of the unique index JTF_AUTH_MAPS_SOURCES_U1.
• JTF_AUTH_PRINCIPAL_MAPPING_ID (NUMBER 16) — foreign key pointing to the corresponding user-role mapping entry in JTF_AUTH_PRINCIPAL_MAPS. This is the principal business link between the two tables.
• OWNERTABLE_NAME (VARCHAR2 60) — the name of the source table from which the role assignment originates (for example, JTF_UM_USERTYPES_B when a role is derived from user-type). Any candidate table must appear in the JTF_AUTH_OWNERTABLE_NAME FND lookup.
• OWNERTABLE_KEY (VARCHAR2 60) — the primary key of the source table row that generated the mapping, tying the assignment back to a specific source record.
• ZD_EDITION_NAME — editioning discriminator present in 12.2.2, part of both unique indexes.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — capture audit and provenance.
• APPLICATION_ID, SECURITY_GROUP_ID, and OBJECT_VERSION_NUMBER — supporting multi-org/security and optimistic-locking attributes.

Two unique indexes serve as business-key candidates: JTF_AUTH_MAPS_SOURCES_U1 on JTF_AUTH_MAPS_SOURCE_ID and JTF_AUTH_MAPS_SOURCES_U2 on (OWNERTABLE_NAME, OWNERTABLE_KEY, JTF_AUTH_PRINCIPAL_MAPPING_ID), each augmented with ZD_EDITION_NAME in 12.2.2. The PK is additionally referenced as JTF_AUTH_MAPS_SOURCES_UK1 over the same business key set.

Common Use Cases and Queries

Typical uses involve auditing role assignments, tracing the origin of a user-role grant, and reporting on provisioning sources. A common pattern joins the source table to its parent mapping:

• List all sources for a specific principal mapping: SELECT s.OWNERTABLE_NAME, s.OWNERTABLE_KEY FROM JTF.JTF_AUTH_MAPS_SOURCES s WHERE s.JTF_AUTH_PRINCIPAL_MAPPING_ID = :mapping_id;
• Trace a role back to its originating user-type: filter by OWNERTABLE_NAME against the JTF_AUTH_OWNERTABLE_NAME lookup and join to the source table on the OWNERTABLE_KEY.
• Audit historical grants using the WHO columns (CREATED_BY, CREATION_DATE) to establish when a source-based assignment was introduced.
• Duplicate detection across sources using JTF_AUTH_MAPS_SOURCES_U2 to ensure a mapping is not associated with the same owner table/key more than once within an edition.

Related Objects

• JTF_AUTH_PRINCIPAL_MAPS — parent mapping table joined via JTF_AUTH_PRINCIPAL_MAPPING_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
• FND_USER — the basis for CREATED_BY / LAST_UPDATED_BY lookups.
• FND_LOGINS — related to LAST_UPDATE_LOGIN.
• JTF_AUTH_OWNERTABLE_NAME — FND lookup constraining valid OWNERTABLE_NAME values.
• JTF_UM_USERTYPES_B — a representative candidate source table referenced via OWNERTABLE_NAME/OWNERTABLE_KEY.
• FND_APPLICATION — resolves APPLICATION_ID.