Search Results address_validation

Overview

FND_TERRITORIES_VL is a multi-language (ML) view owned by the APPS schema in Oracle E-Business Suite. It is a component of the FND - Application Object Library product and is documented as VALID in both EBS 12.1.1 and 12.2.2. The view presents territory (country and territory) reference data by joining the base table FND_TERRITORIES with its translation table FND_TERRITORIES_TL, so that language-dependent attributes are returned in the session's current language. The purpose of the view is to provide a single, denormalized read-only source for both language-independent and translated territory information.

Within Oracle EBS, territory data drives country lists of values, address formatting and validation, bank information formatting and validation, ISO code mapping, and globalization features. Rather than querying the two base tables directly, reporting, forms, and integration logic reference FND_TERRITORIES_VL, which resolves the correct translated row automatically through the USERENV('LANG') session language. This makes the view the standard reporting interface for territory reference data within the APPS schema.

Underlying Base Objects

The documented view definition references two base objects through APPS synonyms: FND_TERRITORIES and FND_TERRITORIES_TL. FND_TERRITORIES holds the language-independent attributes of each territory, keyed by TERRITORY_CODE. FND_TERRITORIES_TL holds the translated attributes—TERRITORY_SHORT_NAME and DESCRIPTION—keyed by both TERRITORY_CODE and LANGUAGE.

The view is defined as a join between the translation table (aliased T) and the base table (aliased B) on TERRITORY_CODE, with the additional predicate T.LANGUAGE = USERENV('LANG'). This constraint restricts the result set to a single translation row per territory, matching the session language of the querying user. The view exposes ROW_ID derived from the base table ROWID (B.ROWID) alongside the columns from both tables. Where no translation exists for the session language, the corresponding territory row is not returned by the join.

Key Columns

• ROW_ID — the ROWID of the underlying FND_TERRITORIES row, exposed for row identification.
• TERRITORY_CODE — the primary business key identifying the territory.
• TERRITORY_SHORT_NAME — the translated short name of the territory, sourced from FND_TERRITORIES_TL and rendered in the session language.
• DESCRIPTION — the translated descriptive text for the territory.
• NLS_TERRITORY — the Oracle NLS territory identifier associated with the record.
• ISO_TERRITORY_CODE and ISO_NUMERIC_CODE — ISO-standard alphanumeric and numeric country codes used in external integration and data exchange.
• EU_CODE — the European Union code associated with the territory.
• ALTERNATE_TERRITORY_CODE — an alternate identifier for the territory.
• ADDRESS_STYLE and ADDRESS_VALIDATION — attributes governing address formatting and validation behavior for the territory.
• BANK_INFO_STYLE and BANK_INFO_VALIDATION — attributes governing bank information formatting and validation for the territory.
• OBSOLETE_FLAG — indicates whether the territory is obsolete and should be excluded from active selection lists.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes populating country lists of values, resolving ISO codes during data conversion, and validating address and bank configuration by territory. The following query returns the active territories in the session language, ordered by short name:

SELECT territory_code,
       territory_short_name,
       iso_territory_code,
       nls_territory
FROM   fnd_territories_vl
WHERE  obsolete_flag = 'N'
ORDER  BY territory_short_name;

For integration scenarios requiring ISO mapping, the numeric code can be retrieved directly:

SELECT territory_code,
       iso_territory_code,
       iso_numeric_code
FROM   fnd_territories_vl
WHERE  territory_code = :p_territory_code;

Because the view applies the USERENV('LANG') predicate, results are returned in the language of the querying session, and callers should not add their own language filter against FND_TERRITORIES_TL. Join FND_TERRITORIES_VL to address, location, or bank-related tables on TERRITORY_CODE to resolve descriptive territory names in reports and concurrent programs.