Results for “territory_code”

14 results




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

Overview

FND_TERRITORIES_TL is the translation (language) table for FND_TERRITORIES in the Oracle E-Business Suite Application Object Library (FND) product family. It is owned by the APPLSYS schema and exists in both Oracle EBS 12.1.1 and 12.2.2. The base table FND_TERRITORIES stores territory (country and region) definition data, while FND_TERRITORIES_TL holds the language-specific, translated attributes for each territory — most notably the translated territory short name and description. Any territory shown in a user's session language, such as in country lists of values, address entry forms, or tax and shipping setups, resolves its display text through this table.

From a Data Vault modeling perspective, this object is heuristic classified as satellite-leaning. FND_TERRITORIES_TL does not carry its own independent business identity; its rows are functionally dependent on the parent territory record in FND_TERRITORIES. In a Data Vault construct, it is therefore more naturally modeled as a satellite keyed by the parent territory business key plus the language (culture) discriminator, rather than as a hub or a link.

Key Information Stored

The table comprises 11 documented columns. The most significant are:

  • TERRITORY_CODE — the territory identifier, inherited from the parent FND_TERRITORIES record and part of the primary key.
  • LANGUAGE — the language/culture code for the translation row; combined with TERRITORY_CODE, it forms part of the primary key.
  • TERRITORY_SHORT_NAME — the translated short name of the territory, the principal display value surfaced in forms and reports.
  • DESCRIPTION — the translated longer descriptive text for the territory.
  • SOURCE_LANG — identifies the source language of the row from which a translation was derived, used by the translation framework.
  • ZD_EDITION_NAME — the edition identifier introduced for edition-based redefinition (EBR) in 12.2, supporting online patching.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS "Who" audit columns tracking row creation and modification.

The surrogate primary key is FND_TERRITORIES_TL_PK (TERRITORY_CODE, LANGUAGE). Two unique indexes represent business-key candidates: FND_TERRITORIES_TL_U1 (TERRITORY_CODE, LANGUAGE, ZD_EDITION_NAME) and FND_TERRITORIES_TL_U2 (TERRITORY_SHORT_NAME, LANGUAGE, ZD_EDITION_NAME). In 12.2 these unique constraints include ZD_EDITION_NAME to comply with editioning.

Common Use Cases and Queries

Typical scenarios include building translated country lists of values, resolving the display name of a territory from a stored code, and validating that a translation exists for a given language. A common join retrieves the translated short name for a base territory:

  • SELECT t.territory_code, tl.territory_short_name, tl.description FROM fnd_territories t, fnd_territories_tl tl WHERE t.territory_code = tl.territory_code AND tl.language = USERENV('LANG');
  • Filtering by the session language, or by SOURCE_LANG, to audit translation coverage across territories.
  • Reporting on territories lacking a translation for a target language by comparing counts between FND_TERRITORIES and FND_TERRITORIES_TL.

Because the table is translation-driven, queries should always include a LANGUAGE predicate; omitting it returns one row per installed language.

Related Objects

The dominant relationship is the foreign key from FND_TERRITORIES_TL.TERRITORY_CODE to FND_TERRITORIES. Significant related objects include:

  • FND_TERRITORIES — parent table holding the base, untranslated territory definitions; joined on TERRITORY_CODE.
  • FND_LANGUAGES — the language repository resolved through the LANGUAGE column to obtain language names.
  • FND_TERRITORIES_VL — the translated view exposing base and translation columns together for forms and reports.
  • FND_TERRITORIES_TL_PK / _U1 / _U2 — the primary and unique constraints enforcing row identity.
  • HR_LOCATIONS_ALL and address-related tables that reference territory codes and rely on this table for display text.