Results for “jtf_tty_terr_groups”

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

Overview

JTF_TTY_TERR_GROUPS is a CRM Foundation (JTF) table that stores territory group data within Oracle E-Business Suite 12.1.1 and 12.2.2. In the Oracle Territory Manager (Territory Management / ETRM) data model, a territory group acts as a logical container that clusters related territory definitions, hierarchy nodes, and assignment rules. It provides the grouping construct used to organize territories, associate them with parent territories, define matching rules for eligibility evaluation, and control how winners and catch-all resources are resolved during territory assignment processing.

The table is owned by the JTF schema and is documented as VALID in the E-Business Suite Technical Reference Manual (ETRM). It carries a documented physical schema of 21 columns in release 12.2.2 and serves as a central dependency for several subordinate territory entities, making it one of the more heavily referenced objects in the Territory Manager data model.

Based on the foreign key topology, the heuristic Data Vault classification for this object is hub-leaning. The single-column primary key (TERR_GROUP_ID), the presence of descriptive and lifecycle attributes such as TERR_GROUP_NAME, RANK, and the ACTIVE_FROM_DATE / ACTIVE_TO_DATE pair, and the fact that multiple child tables reference it, are all consistent with a hub-and-satellite modeling pattern in which territory group identity is the hub and its descriptive attributes form a satellite. This classification is offered as a modeling suggestion, not as a documented product feature.

Key Information Stored

The primary key of JTF_TTY_TERR_GROUPS is enforced by the constraint JTF_TTY_TERR_GROUPS_PK on the column TERR_GROUP_ID, which is an internally generated surrogate identifier for each territory group. The unique index JTF_TTY_TERR_GROUPS_U1 also covers TERR_GROUP_ID, confirming it as the sole documented business-key candidate; the table does not document a natural composite key, so TERR_GROUP_NAME operates as a descriptive identifier rather than as a uniqueness constraint.

The most significant columns are:

• TERR_GROUP_ID — surrogate primary key and the column joined by every dependent table.
• TERR_GROUP_NAME — the user-facing name of the territory group.
• RANK — ordinal ranking used to sequence territory groups during evaluation or display.
• ACTIVE_FROM_DATE / ACTIVE_TO_DATE — the effective date range during which the group is considered active.
• PARENT_TERR_ID — self-referencing foreign key into JTF_TERR_ALL that establishes the parent territory in the hierarchy.
• MATCHING_RULE_CODE — identifies the matching rule applied to qualify transactions against the group.
• WORKFLOW_ITEM_TYPE / WORKFLOW_PROCESS_NAME — the workflow metadata used when territory assignment invokes a workflow process.
• CATCH_ALL_RESOURCE_ID / CATCH_ALL_RESOURCE_TYPE — the fallback resource assigned when no other territory member qualifies.
• NUM_WINNERS — the maximum number of winning resources returned by the group's rules.
• GENERATE_CATCHALL_FLAG — controls whether a catch-all assignment is generated.
• SELF_SERVICE_TYPE — indicates the self-service context in which the group is exposed.
• DESCRIPTION — free-text business description.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework (OAF) and concurrent update protection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS who-columns used for auditing.

Common Use Cases and Queries

Territory administrators and CRM technical consultants query this table to audit the definition of territory groups, confirm effective dating, and inspect matching-rule configuration. A typical lookup by name or key uses:

• SELECT terr_group_id, terr_group_name, rank, active_from_date, active_to_date, matching_rule_code FROM jtf.jtf_tty_terr_groups WHERE terr_group_id = :p_terr_group_id;
• SELECT g.terr_group_id, g.terr_group_name FROM jtf.jtf_tty_terr_groups g WHERE g.active_from_date <= SYSDATE AND NVL(g.active_to_date, SYSDATE) >= SYSDATE;

A frequent reporting pattern joins the group to its parent territory in JTF_TERR_ALL to reconstruct the hierarchy, for example JOIN jtf.jtf_terr_all t ON t.terr_id = g.parent_terr_id. Because territory groups drive catch-all behavior, support investigations into "why was this resource assigned" frequently trace NUM_WINNERS, GENERATE_CATCHALL_FLAG, CATCH_ALL_RESOURCE_ID, and MATCHING_RULE_CODE together with the group's children in JTF_TTY_TERR_GRP_ROLES and JTF_TTY_TERR_GRP_OWNERS. Effective-dating queries are also common when troubleshooting assignments that appear on or after a specific date.

Related Objects

The referential topology of JTF_TTY_TERR_GROUPS links it to both parent and child entities in the Territory Manager schema. The most significant related objects are:

• JTF_TERR_ALL — both referenced and referencing; JTF_TTY_TERR_GROUPS.PARENT_TERR_ID points to JTF_TERR_ALL, and JTF_TERR_ALL.TERR_GROUP_ID in turn references this table, forming a bidirectional hierarchy relationship.
• JTF_TTY_GEO_TERR — geography territory detail, joined on TERR_GROUP_ID.
• JTF_TTY_TERR_GRP_ACCTS — account assignments for the territory group, joined on TERR_GROUP_ID.
• JTF_TTY_TERR_GRP_OWNERS — resource owners of the group, joined on TERR_GROUP_ID.
• JTF_TTY_TERR_GRP_ROLES — role definitions associated with the group, joined on TERR_GROUP_ID.
• JTF_TTY_ADMIN_BIN_SUMM — administrative bin summary records that reference the group via TERR_GROUP_ID.
• JTF_TTY_GEO_GRP_VALUES — geography group values that resolve against the group via TERR_GROUP_ID.

Collectively these dependent tables represent the account, owner, role, geography, and summary facets of a territory group, confirming JTF_TTY_TERR_GROUPS as the functional anchor of the Territory Manager grouping model.