Results for “jtf_sources_all”

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

Overview

JTF_SOURCES_ALL is a CRM Foundation configuration table in the JTF schema that defines the source or origin values used throughout Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its columns describe how a source is displayed, translated, secured, and dynamically resolved: lookup code and meaning, enabled flag, effective start and end dates, Oracle record history and auditing columns, multi-org operating unit identifier (ORG_ID), security group identifier, generic RELATED_ID1 through RELATED_ID5 attributes, resource LOV SQL, resource and role column names, a group column name, resource access lookup, denormalized value table names, and ZD_EDITION_NAME. In CRM contexts this configuration drives qualification and territory usage records, where a source is attached to qualification types, territory types, and territories. Based on the documented foreign key structure, a Data Vault modeling heuristic suggests this object is hub-leaning: SOURCE_ID acts as a stable business key subject to many descriptive attributes, while the referencing usage tables behave more like link or satellite structures.

Key Information Stored

The primary key is enforced by the JTF_SOURCES_ALL_PK unique index on SOURCE_ID, the surrogate identifier for each source. A second unique index, JTF_SOURCES_U1, spans SOURCE_ID, ORG_ID, and ZD_EDITION_NAME, making this set the business-key candidate when operating-unit and edition context must be distinguished. The most significant columns are:

• SOURCE_ID — surrogate primary key identifying the source.
• ORG_ID — operating unit owning the source definition.
• ZD_EDITION_NAME — edition identifier supporting the multi-organization data model.
• LOOKUP_CODE and LOOKUP_TYPE — code and classification of the referenced lookup value.
• MEANING — user-facing display name of the source.
• DESCRIPTION — free-text description of the source.
• ENABLED_FLAG — indicates whether the source is active for use.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective date range controlling availability.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling security group scope.
• RELATED_ID1 through RELATED_ID5 — generic identifiers for related entities.
• RSC_LOV_SQL and RSC_ACCESS_LKUP — SQL and lookup used to resolve allowable resources.
• RSC_COL_NAME, ROLE_COL_NAME, and GROUP_COL_NAME — column names used in dynamic resource resolution.
• DENORM_VALUE_TABLE_NAME and DENORM_DEA_VALUE_TABLE_NAME — denormalized value tables used for source resolution.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard auditing columns.

Common Use Cases and Queries

Typical uses include validating active sources, listing what each source means, restricting sources by operating unit or security group, and joining source definitions to qualification-type or territory-usage tables. Reporting against denormalized value table names and resource column names supports dynamic source resolution. Example patterns:

• Active sources for the current organization: SELECT SOURCE_ID, MEANING FROM JTF.JTF_SOURCES_ALL WHERE ORG_ID = :org_id AND ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
• Source usage by qualification type: SELECT q.SOURCE_ID, s.MEANING FROM JTF.JTF_QUAL_TYPE_USGS_ALL q JOIN JTF.JTF_SOURCES_ALL s ON s.SOURCE_ID = q.SOURCE_ID;
• Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS; edition-aware reporting should consider ZD_EDITION_NAME in filters.

Related Objects

JTF_SOURCES_ALL participates in several foreign key relationships. It references FND_SECURITY_GROUPS through SECURITY_GROUP_ID. Three usage tables reference SOURCE_ID back to this table: JTF_QUAL_TYPE_USGS_ALL.SOURCE_ID, JTF_TERR_TYPE_USGS_ALL.SOURCE_ID, and JTF_TERR_USGS_ALL.SOURCE_ID. Join each on SOURCE_ID to report qualification type, territory type, and territory source usage. Because JTF_SOURCES_ALL is defined by the JTF_SOURCES_ALL_PK primary key, the SOURCE_ID column is the correct and only join key from all four related objects. These relationships make JTF_SOURCES_ALL the central hub supporting CRM Foundation qualification and territory source configuration in Oracle EBS 12.1.1 and 12.2.2.