Results for “jtf_sources_u1”

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

Overview

JTF.JTF_SOURCES_ALL is a seed data table in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment that stores the identity of each Oracle Applications module (source) that participates in the Oracle Territory Manager (Territories) infrastructure. Its primary purpose is to register the lookup-driven "source" identifiers — such as Oracle Sales, Oracle Service, Oracle TeleSales, and other modules — that can own, qualify, or use territory definitions. Each row represents one enabled source module together with the lookup semantics, display meaning, validity dates, and the organization context in which it is available.

Because the table is seeded and rarely extended, it functions as a reference (master) entity rather than a transactional or high-volume table. In Data Vault modeling terms, the heuristic classification from the documented foreign-key structure is hub-leaning: SOURCE_ID behaves as a durable business key that is referenced by downstream usage tables, making JTF_SOURCES_ALL a natural hub candidate. The ORG_ID column introduces a multi-org dimension, and the unique index JTF_SOURCES_U1 (SOURCE_ID, ORG_ID) supports the same hub-style key pattern.

Key Information Stored

The most important columns are:

• SOURCE_ID — surrogate primary key (JTF_SOURCES_ALL_PK) populated from an Oracle Sequence; the durable business key inherited by all dependent usage tables.
• ORG_ID — organization identifier supporting multi-org access; combined with SOURCE_ID in the unique index JTF_SOURCES_U1.
• LOOKUP_CODE — the lookup code (foreign key to FND_LOOKUPS) that identifies the source module.
• LOOKUP_TYPE — the lookup type that groups the source codes; also an FND_LOOKUPS foreign key.
• MEANING — the user-visible description displayed in QuickCode pop-ups when the code is hidden.
• ENABLED_FLAG — indicates whether the source is currently active.
• DESCRIPTION — up to 240 characters describing the source.
• START_DATE_ACTIVE / END_DATE_ACTIVE — activation window for the source record.
• SECURITY_GROUP_ID — hosting-development security group reference (foreign key to FND_SECURITY_GROUPS).
• RELATED_ID1 through RELATED_ID5 — optional relationship columns between sources, used to link related source definitions.
• RSC_LOV_SQL, RSC_COL_NAME, ROLE_COL_NAME, GROUP_COL_NAME, RSC_ACCESS_LKUP — configuration columns that drive the resource LOV and access routing behavior for the source.
• DENORM_VALUE_TABLE_NAME, DENORM_DEA_VALUE_TABLE_NAME — denormalized value table names used by territory assignment.
• Standard WHO audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

The documented physical schema in 12.2.2 lists 28 columns and identifies the unique business-key candidate as JTF_SOURCES_U1 (SOURCE_ID, ORG_ID, ZD_EDITION_NAME), which extends the earlier 12.1.1 (SOURCE_ID, ORG_ID) layout.

Common Use Cases and Queries

Typical uses include resolving the human-readable meaning of a territory source, building lookups for setup forms, and joining usage tables back to their source module for reporting.

• Resolve source identity: join JTF_SOURCES_ALL to FND_LOOKUPS on LOOKUP_CODE/LOOKUP_TYPE to return MEANING for display.
• Filter active sources: query WHERE ENABLED_FLAG = 'Y' AND SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE).
• Multi-org reporting: constrain by ORG_ID to scope results to the operating unit.
• Usage analysis: join JTF_TERR_USGS_ALL, JTF_TERR_TYPE_USGS_ALL, and JTF_QUAL_TYPE_USGS_ALL on SOURCE_ID to measure how many territory definitions rely on each source.

Example: SELECT s.SOURCE_ID, s.MEANING, COUNT(t.TERR_ID) FROM JTF.JTF_SOURCES_ALL s LEFT JOIN JTF.JTF_TERR_USGS_ALL t ON t.SOURCE_ID = s.SOURCE_ID WHERE s.ENABLED_FLAG = 'Y' GROUP BY s.SOURCE_ID, s.MEANING;

Related Objects

• JTF.JTF_TERR_USGS_ALL — references SOURCE_ID; records territory usage per source.
• JTF.JTF_TERR_TYPE_USGS_ALL — references SOURCE_ID; territory type usage.
• JTF.JTF_QUAL_TYPE_USGS_ALL — references SOURCE_ID; qualifier type usage.
• FND_LOOKUPS — parent of LOOKUP_CODE and LOOKUP_TYPE.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• FND_USER — WHO columns CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.

Together these relationships establish JTF_SOURCES_ALL as the central source registry for the Territory Manager data model.