Search Results jtf_terr_usgs_all_pk

Overview

The JTF_TERR_USGS_ALL table is a core data object within the Oracle E-Business Suite (EBS) CRM Foundation module. It functions as a critical junction table that defines and stores the permissible associations between territory definitions and the specific Oracle Application modules that are authorized to utilize those territories. This table is essential for the territory management framework, enabling a single territory structure to be shared and leveraged across multiple EBS products, such as Order Management, Service, or Sales. Its role is to enforce and maintain the integrity of territory-module relationships, ensuring that territory-based data access and processing rules are correctly applied throughout the application suite.

Key Information Stored

The table primarily stores the linkage between a territory and an application source. Its key columns include the primary key TERR_USG_ID, which uniquely identifies each association record. The TERR_ID column holds the foreign key reference to a specific territory defined in the JTF_TERR_ALL table. The SOURCE_ID column holds the foreign key reference to an application module defined in the JTF_SOURCES_ALL table, which catalogs the various EBS products and sub-modules. Additional columns typically manage multi-organization (Multi-Org) access control (e.g., ORG_ID) and standard WHO columns for tracking creation and modification metadata, though these are not explicitly detailed in the provided excerpt.

Common Use Cases and Queries

A primary use case is validating whether a particular EBS module is permitted to access a given territory during runtime operations, such as assigning a sales opportunity or a service request. System administrators may query this table to audit or configure which modules are enabled for specific territories. A common reporting query involves joining to related tables to list all territories available to a module:

• SELECT t.NAME territory_name, s.SOURCE_NAME module_name FROM jtf_terr_usgs_all u, jtf_terr_all t, jtf_sources_all s WHERE u.terr_id = t.terr_id AND u.source_id = s.source_id AND s.SOURCE_NAME = 'ONT';

Conversely, to find all modules associated with a specific territory, one would filter on the TERR_ID. Data integrity checks often involve identifying orphaned records where either the TERR_ID or SOURCE_ID no longer exists in their respective parent tables.

Related Objects

The JTF_TERR_USGS_ALL table maintains documented foreign key relationships with two principal master tables, forming the core of its referential integrity.

• JTF_TERR_ALL: This is the master table for territory definitions. The relationship is established via the column JTF_TERR_USGS_ALL.TERR_ID, which references JTF_TERR_ALL.TERR_ID. This ensures every usage record points to a valid territory.
• JTF_SOURCES_ALL: This table lists all registered Oracle Application modules. The relationship is established via the column JTF_TERR_USGS_ALL.SOURCE_ID, which references JTF_SOURCES_ALL.SOURCE_ID. This ensures every usage record points to a valid application source.

The table's primary key constraint, JTF_TERR_USGS_ALL_PK on TERR_USG_ID, is referenced by any dependent objects or child tables not listed in the provided metadata.