Results for “okx_countries_v”

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

Overview

OKX_COUNTRIES_V is a seeded Oracle EBS view owned by the APPS schema and classified under the OKX - Contracts Integration product. Its documented purpose is to expose territories, also known as countries, in a denormalized form suitable for reporting and integration consumption. The view carries a VALID status and is available in both Oracle EBS 12.1.1 and 12.2.2, where the underlying data model for territories is shared through the FND foundation tables.

The view presents a flattened, presentation-ready projection of territory data rather than a normalized entity. For every territory row, it supplies a single language-resolved territory code and description (via a translation join driven by the user's session language), a legacy numeric identifier column named ID1, a constant ID2 value of '#', a derived uppercase status of 'A', an effective start date defaulting to SYSDATE, and null placeholders for end date and primary unit of measure. This design makes the view behave like a reference or lookup source: it can be queried directly by concurrent programs, Forms LOVs, and interface staging logic without requiring the caller to understand the FND translation model.

The principal column of interest for the search term "iso_numeric_code" is ISO_NUMERIC_CODE, which is sourced directly from the base territory table and carries the international standard numeric country identifier. This makes the view the natural EBS access path when an integration or report must map an EBS territory to an external system that keys countries by ISO numeric value.

Underlying Base Objects

The documented base objects referenced by OKX_COUNTRIES_V are FND_TERRITORIES (accessed through a SYNONYM) and FND_TERRITORIES_TL (also accessed through a SYNONYM). These are Oracle Application Object Library foundation tables that store territory definitions and their translated (language-specific) descriptions respectively.

• FND_TERRITORIES — the master territory table, holding the non-translated attributes including TERRITORY_CODE and ISO_NUMERIC_CODE.
• FND_TERRITORIES_TL — the translation table, holding TERRITORY_SHORT_NAME and DESCRIPTION for each installed language.

The join between the two objects is on TERRITORY_CODE, and the translation row is restricted by TL.LANGUAGE = USERENV('LANG'), ensuring that only the current session language's short name and description are returned. Aliases in the view text are B for FND_TERRITORIES and TL for FND_TERRITORIES_TL. Because the view is defined over foundation tables, it inherits their seed data and is refreshed automatically as territories are maintained by Oracle or by localization patches.

Key Columns

• ID1 — populated with the base TERRITORY_CODE, providing a code-based identifier for the territory.
• ID2 — a literal '#' placeholder, present to satisfy a two-column identifier convention.
• NAME — the translated TERRITORY_SHORT_NAME, i.e., the short display name for the territory in the session language.
• DESCRIPTION — the translated territory description from FND_TERRITORIES_TL.
• ISO_NUMERIC_CODE — the ISO numeric country code sourced from FND_TERRITORIES; this is the column most relevant to interoperability with external systems and the term referenced in the user's search.
• STATUS — a constant 'A', indicating active.
• START_DATE_ACTIVE — set to SYSDATE at query time, giving a volatile effective start date.
• END_DATE_ACTIVE — always NULL.
• PRIMARY_UOM_CODE — always NULL.

Note that STATUS, START_DATE_ACTIVE, END_DATE_ACTIVE, and PRIMARY_UOM_CODE are derived or literal values rather than real territory attributes, so they should not be treated as authoritative for date-effective or unit-of-measure logic.

Common Use Cases and Queries

Typical usage is lookup validation, country mapping for contracts integration (OKX), and exposing ISO numeric codes to external feeds. A simple listing returns the code, name, and ISO numeric value:

• SELECT id1, name, description, iso_numeric_code FROM apps.okx_countries_v ORDER BY name;
• SELECT iso_numeric_code FROM apps.okx_countries_v WHERE id1 = :territory_code; — resolve an ISO numeric code from an EBS territory code.
• SELECT id1 FROM apps.okx_countries_v WHERE iso_numeric_code = :iso_num; — the reverse mapping for inbound interfaces.

Because translations are resolved with USERENV('LANG'), the NAME and DESCRIPTION returned depend on the session language, so callers requiring a fixed language should consider querying the base tables directly with an explicit LANGUAGE predicate rather than relying on the view.