Results for “comparison_operator”

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

Overview

JTF_TTY_GEO_GRP_VALUES is a CRM Foundation (JTF) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores Geography Territory Group Values, functioning as the intersection between geography definitions and territory groups used by the Territory Manager and related CRM components. Each row captures a geographic qualification rule, associating a territory group with a geography identifier and a comparison operator, which allows the territory engine to evaluate whether a given customer, site, or party location falls inside a designated geographic grouping.

Because the table holds qualifying attribute values that participate in territory evaluation rather than independent business entities, its heuristic Data Vault classification is satellite-leaning. This classification suggests the table is best modeled as a satellite attached to a parent territory-group hub and a geography hub, rather than as an independent hub or an associative link.

Key Information Stored

The table is documented with twelve physical columns. The most significant are summarized below.

• GEO_GRP_VALUES_ID — Surrogate primary key, enforced by JTF_TTY_GEO_GRP_VALUES_PK and additionally backed by the unique index JTF_TTY_GEO_GRP_VALUES_U1. This is the sole documented business-key candidate.
• TERR_GROUP_ID — Foreign key to JTF_TTY_TERR_GROUPS, identifying the territory group to which the geographic qualification belongs.
• GEO_ID_FROM — Foreign key to JTF_TTY_GEOGRAPHIES, defining the starting geography identifier in the qualification rule.
• GEO_ID_TO — Companion geography identifier supporting range-style geographic qualifications.
• GEO_TYPE — Classifies the geographic dimension being referenced (for example country, state, or city level).
• COMPARISON_OPERATOR — The operator used when evaluating the geography value during territory qualification.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF-based Territory Manager UI to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and last-modification metadata.

The pairing of GEO_ID_FROM with GEO_ID_TO and COMPARISON_OPERATOR gives each row its rule semantics; GEO_TYPE qualifies the level at which that rule operates.

Common Use Cases and Queries

Typical use cases include auditing the geography rules attached to a territory group, validating that no orphaned geography references exist after geography maintenance, and reporting the geographic coverage of a given territory model.

• List all geography values for a territory group: SELECT GEO_GRP_VALUES_ID, GEO_TYPE, GEO_ID_FROM, GEO_ID_TO, COMPARISON_OPERATOR FROM JTF.JTF_TTY_GEO_GRP_VALUES WHERE TERR_GROUP_ID = :p_terr_group_id;
• Join to the geography master to resolve descriptive names: SELECT g.TERR_GROUP_ID, geo.GEOGRAPHY_NAME FROM JTF.JTF_TTY_GEO_GRP_VALUES g, JTF.JTF_TTY_GEOGRAPHIES geo WHERE g.GEO_ID_FROM = geo.GEO_ID;
• Detect orphaned rows where the referenced geography no longer exists: a LEFT OUTER JOIN from this table to JTF_TTY_GEOGRAPHIES returning rows where the geography key is NULL.
• Track recent rule changes using LAST_UPDATE_DATE and LAST_UPDATED_BY for change-audit reporting on territory administration.

Because territory evaluation runs frequently, reports on this table should be restricted by TERR_GROUP_ID to avoid full scans of the intersection data.

Related Objects

The following objects are the most significant relationships documented for this table.

• JTF_TTY_GEOGRAPHIES — referenced via GEO_ID_FROM; supplies the geography definition for each qualification value.
• JTF_TTY_TERR_GROUPS — parent territory group referenced via TERR_GROUP_ID; each value row belongs to exactly one group.
• JTF_TTY_GEO_GRP_VALUES_PK and JTF_TTY_GEO_GRP_VALUES_U1 — the primary key constraint and unique index enforcing GEO_GRP_VALUES_ID.
• JTF_TTY_TERR_GROUPS and related territory hierarchy tables — consumed by the Territory Manager concurrent programs and OAF pages that resolve geographic qualifications.
• Territory qualification APIs and Territory Manager UI pages — read this table at runtime when evaluating whether a transaction party qualifies for a territory assignment.