Results for “rsc_resource_type”

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

Overview

JTF_TTY_GEO_TERR_RSC is a transactional table in the JTF schema (CRM Foundation product) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the assignment of sales persons — referred to as resources — to geography-based territories. Each row represents a single resource-to-territory assignment, making the table the operational bridge between the territory definition layer and the resource layer used by Oracle Territory Manager (formerly Territory Assignment Manager) and downstream modules such as Oracle Sales, Oracle TeleSales, and Oracle Field Service.

The resource layer records which sales, telesales, or service representatives are responsible for a given geographic territory. Territory Manager evaluates territory rules and writes the qualifying resources into this table, which other applications then query to determine ownership, routing, and access. Because the table carries assignment-status and role/group attributes alongside its foreign key to the territory, it behaves as a junction that links two otherwise independent entities: the territory and the resource.

The ETRM metadata classifies this object heuristically as satellite-leaning under Data Vault modeling conventions. That characterization should be treated as a modeling suggestion rather than a mandatory design: the table function's as a link between JTF_TTY_GEO_TERR and the resource registry, but its descriptive columns (assignment flag, role code, resource type, version tracking) give it satellite-like attributes as well.

Key Information Stored

The table contains 13 documented columns in the 12.2.2 physical schema. The most significant include:

• GEO_TERR_RESOURCE_ID — the surrogate primary key, backed by index JTF_TTY_GEO_TERR_RSC_PK, uniquely identifying each assignment row. It is also the single-column unique index JTF_TTY_GEO_TERR_RSC_U1, the documented business-key candidate.
• GEO_TERRITORY_ID — foreign key to JTF_TTY_GEO_TERR, identifying the geography territory to which the resource is assigned.
• RESOURCE_ID — the assigned sales person or resource. This is the operational payload of the row.
• RSC_GROUP_ID and RSC_ROLE_CODE — the resource group and the role the resource plays within the territory (for example, primary or backup representative).
• RSC_RESOURCE_TYPE — distinguishes the kind of resource being assigned.
• ASSIGNED_FLAG — indicates whether the assignment is currently active, supporting soft-deactivation without deleting history.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF-based Territory Manager UI.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns, satisfied by the WHO columns for concurrency and traceability.

The distinction between the surrogate key (GEO_TERR_RESOURCE_ID) and business-key candidates is important: application logic should treat the surrogate as the row identity, while the unique index enforces the one-assignment-per-resource constraint at the physical level.

Common Use Cases and Queries

Typical scenarios include resolving which sales representatives own a given territory, listing all territories assigned to a representative, and verifying that Territory Manager has populated assignments after a rule run. Reporting on inactive assignments is common during territory realignment or workforce changes.

A representative join resolves resources to their territories:

SELECT r.GEO_TERR_RESOURCE_ID, r.RESOURCE_ID, r.RSC_ROLE_CODE,
       t.GEO_TERRITORY_ID
FROM   JTF.JTF_TTY_GEO_TERR_RSC r,
       JTF.JTF_TTY_GEO_TERR t
WHERE  r.GEO_TERRITORY_ID = t.GEO_TERRITORY_ID
AND    r.ASSIGNED_FLAG = 'Y';

To list territories for a specific resource, filter on RESOURCE_ID; to audit recent changes, filter on LAST_UPDATE_DATE or CREATED_BY. Because assignment rows are version-locked, concurrent updates through the Territory Manager UI rely on OBJECT_VERSION_NUMBER, so direct DML should preserve it.

Related Objects

• JTF_TTY_GEO_TERR — the parent geography-territory definition table; joined via JTF_TTY_GEO_TERR_RSC.GEO_TERRITORY_ID. This is the documented foreign key relationship.
• JTF_TTY_GEO_TERR_RSC_PK / _U1 — the primary key and unique indexes on GEO_TERR_RESOURCE_ID that enforce integrity.
• JTF_RS_RESOURCE_EXTNS and the JTF_RS resource registry objects — resolve RESOURCE_ID into resource names and attributes for reporting.
• JTF_TTY_GEO_TERR_RSC_VL (and related views) — the Territory Manager UI layer that presents assignment data.
• Other JTF_TTY_*_RSC assignment tables — parallel tables for non-geographic territory types (for example, customer or product territories) that follow the same resource-assignment pattern.

Together these objects form the territory-assignment model that Oracle CRM modules consume when determining service ownership and routing.