Search Results jtf_tty_geo_terr_rsc




Overview
Explore in AI Chat

Overview

The JTF_TTY_GEO_TERR_RSC table is a core data object within the Oracle E-Business Suite CRM Foundation module (JTF). Its primary function is to manage the assignment of sales personnel, or resources, to specific geography-based territories. This table is essential for implementing and maintaining territory management structures within the application, enabling the alignment of sales teams with defined geographic regions for operational and reporting purposes. It serves as a critical junction table linking territory definitions with human resource assignments, forming the backbone of territory-based routing, quota management, and performance analytics in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's central purpose is to store the relationship between a territory and an assigned resource. Its primary key, GEO_TERR_RESOURCE_ID, uniquely identifies each assignment record. The most critical foreign key column is GEO_TERRITORY_ID, which references the JTF_TTY_GEO_TERR table to define the specific geographic territory. While the provided metadata does not list all columns, a typical implementation would include columns to identify the assigned resource (likely a PARTY_ID or RESOURCE_ID from the HR or JTF schemas), effective start and end dates for the assignment, and creation/modification audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE). The table may also include attributes to define the role or percentage allocation of the resource within that territory.

Common Use Cases and Queries

This table is central to territory management operations. Common use cases include generating territory rosters for sales managers, determining resource eligibility for opportunity or service request assignment based on geographic rules, and building reports on territory coverage. A fundamental query involves joining this table with the territory master and resource tables to list all assignments.

  • Sample Query: List all resources for a territory:
    SELECT rsc.GEO_TERR_RESOURCE_ID, terr.NAME TERRITORY_NAME, per.PARTY_NAME RESOURCE_NAME
    FROM JTF.JTF_TTY_GEO_TERR_RSC rsc,
    JTF.JTF_TTY_GEO_TERR terr,
    HZ_PARTIES per
    WHERE rsc.GEO_TERRITORY_ID = terr.GEO_TERRITORY_ID
    AND rsc.RESOURCE_ID = per.PARTY_ID
    AND SYSDATE BETWEEN rsc.START_DATE_ACTIVE AND NVL(rsc.END_DATE_ACTIVE, SYSDATE);
  • Reporting Use Case: Analyzing the number of resources per territory to assess sales capacity and coverage density.

Related Objects

The JTF_TTY_GEO_TERR_RSC table has defined dependencies within the CRM Foundation schema, primarily through its foreign key relationship. The documented relationship is:

  • Parent Table: JTF_TTY_GEO_TERR. This is the master table for geography territory definitions. The relationship is enforced by the foreign key where JTF_TTY_GEO_TERR_RSC.GEO_TERRITORY_ID references JTF_TTY_GEO_TERR. A territory must exist before resources can be assigned to it.

While not explicitly listed in the provided metadata, this table is also logically related to objects that store resource information, such as JTF_RS_RESOURCE_EXTNS or HZ_PARTIES, and is likely referenced by various Territory Management APIs and views that aggregate assignment data for the application's user interface.