Results for “jtf_tty_geographies”

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

Overview

JTF_TTY_GEOGRAPHIES is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores source geography data. It functions as a foundational reference object for the Territory Management (TTY) subsystem, holding the normalized geographic definitions—countries, states, provinces, counties, cities, and postal codes—that territory and geography-group assignments draw upon. Rather than storing transaction or assignment records, the table persists the master set of geography entities against which downstream territory and grouping logic operates.

From a Data Vault modeling perspective, the metadata's heuristic classification of the object is hub-leaning. This reflects the presence of a single surrogate primary key (GEO_ID) with two outbound-referencing child tables, a pattern typical of a hub that anchors business keys. The suggestion is heuristic only; treating JTF_TTY_GEOGRAPHIES as a hub in a Data Vault design is a reasonable modeling choice, while the descriptive attributes (names, type, codes) would typically be split into an accompanying satellite.

Key Information Stored

The table is documented with 16 columns in the ETRM 12.2.2 schema. The most operationally significant are:

• GEO_ID — The surrogate primary key, enforced by JTF_TTY_GEOGRAPHIES_PK and also the single business-key candidate via unique index JTF_TTY_GEOGRAPHIES_U1. This is the column referenced by dependent territory and group tables.
• GEO_NAME — The display name of the geography entity.
• GEO_TYPE — The classification of the geography record, distinguishing the level or nature of the entry.
• GEO_CODE — The coded identifier for the geography.
• COUNTRY_CODE — The country component of the geography definition.
• STATE_CODE — The state component.
• PROVINCE_CODE — The province component.
• COUNTY_CODE — The county component.
• CITY_CODE — The city component.
• POSTAL_CODE — The postal code component.
• OBJECT_VERSION_NUMBER — Optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE — Standard audit columns for record creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns for the most recent modification and its originating session.

The geographic component columns (COUNTRY_CODE through POSTAL_CODE) collectively define the hierarchical address granularity a given GEO_ID represents, while GEO_TYPE and GEO_CODE support categorization and coded referencing.

Common Use Cases and Queries

Typical use cases center on resolving geography identifiers to human-readable labels and filtering territories by geographic hierarchy. A common reporting pattern joins the source geography to its territory value table:

• Listing geography names for a territory: SELECT g.GEO_NAME, t.GEO_ID FROM JTF_TTY_GEOGRAPHIES g, JTF_TTY_GEO_TERR_VALUES t WHERE g.GEO_ID = t.GEO_ID;
• Resolving geography-group membership: SELECT g.GEO_NAME, v.GEO_ID_FROM FROM JTF_TTY_GEOGRAPHIES g, JTF_TTY_GEO_GRP_VALUES v WHERE g.GEO_ID = v.GEO_ID_FROM;
• Filtering all geographies within a country: SELECT GEO_ID, GEO_NAME, GEO_TYPE FROM JTF_TTY_GEOGRAPHIES WHERE COUNTRY_CODE = :country;
• Auditing recently changed reference data using LAST_UPDATE_DATE and LAST_UPDATED_BY.

These queries support territory administration reports, geography-group validation, and CRM assignment diagnostics.

Related Objects

The documented foreign-key relationships identify the principal dependent objects:

• JTF_TTY_GEO_GRP_VALUES — References JTF_TTY_GEOGRAPHIES via the column GEO_ID_FROM, linking geography-group value rows to their source geography.
• JTF_TTY_GEO_TERR_VALUES — References JTF_TTY_GEOGRAPHIES via the column GEO_ID, associating territory value rows with the geography.
• JTF_TTY_GEOGRAPHIES_PK / _U1 — The primary key and unique index that anchor the object and enforce GEO_ID uniqueness.

Territory and geography-group configuration screens, territory assignment logic, and CRM reporting components are the primary consumers that depend on this table's integrity.