Search Results jtf_terr_type_usgs_all




Overview
Explore in AI Chat

Overview

The JTF_TERR_TYPE_USGS_ALL table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module. Its primary function is to maintain the mapping between defined territory types and the specific Oracle Application modules that are configured to utilize them. This association is critical for enabling territory-based data access and assignment rules across different EBS products, such as Order Management, Service, or Sales. The table ensures that territory definitions are correctly scoped and enforced only within the relevant application contexts, thereby supporting the modular architecture of Oracle EBS.

Key Information Stored

The table's structure is designed to store the essential linkage between a territory type and its consuming application module. The primary columns include the surrogate key TERR_TYPE_USG_ID, which uniquely identifies each association record. The TERR_TYPE_ID column is a foreign key referencing the JTF_TERR_TYPES_ALL table, linking to the specific territory type. The SOURCE_ID column is a foreign key referencing the JTF_SOURCES_ALL table, which contains the registered application modules within Oracle EBS (e.g., 'ONT' for Order Management). Together, these columns define which module (SOURCE_ID) is permitted to use a given territory definition (TERR_TYPE_ID).

Common Use Cases and Queries

A primary use case is validating and auditing territory type assignments during application setup or upgrade. System administrators or functional consultants may query this table to verify which modules are enabled for a specific territory management style. A common reporting query would join to the related tables to produce a human-readable list:

  • Identifying all modules using a specific territory type: SELECT source.source_name FROM jtf_terr_type_usgs_all usg, jtf_sources_all source WHERE usg.source_id = source.source_id AND usg.terr_type_id = :p_terr_type_id;
  • Checking for any territory types not assigned to any module, which may indicate orphaned setup data.
  • During data migration or patching, scripts may reference this table to ensure territory usage rules are consistently applied.

Related Objects

This table sits at the intersection of two key setup entities. It is directly dependent on the JTF_TERR_TYPES_ALL table, which stores the master definition of territory types (e.g., 'Sales Territory', 'Service Coverage'). It also depends on the JTF_SOURCES_ALL table, the central repository for application module codes. The table's primary key constraint is JTF_TERR_TYPE_USGS_ALL_PK on TERR_TYPE_USG_ID. Its logical relationships mean it is often accessed in conjunction with views or APIs that manage territory assignment engines or the Territory Manager user interface within the CRM Foundation.