Results for “fnd_territories_u1”

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

Overview

APPLSYS.FND_TERRITORIES is the Oracle E-Business Suite reference table that stores information for countries, also referred to as territories. It is a seed-data table residing in the APPS_TS_SEED tablespace and is registered in the FND Design Data repository as FND.FND_TERRITORIES. The table supplies the authoritative ISO 3166 two-letter territory codes and numeric codes used throughout the E-Business Suite, together with the address and bank number formatting and validation rules that Oracle Applications apply when processing party, supplier, customer, and payment data.

The object carries a heuristic Data Vault classification of hub-leaning, which suggests modeling it as a hub: the territory code is a stable, naturally occurring business key that is referenced by a large number of dependent tables. Because the table also carries descriptive formatting and validation attributes, a satellite structure would typically be attached to hold those attributes.

Key Information Stored

The primary key is documented as FND_TERRITORIES_PK, defined on TERRITORY_CODE. A separate unique index, FND_TERRITORIES_U1, covers TERRITORY_CODE together with ZD_EDITION_NAME in the 12.2.2 documented physical schema; the 12.1.1 documentation describes FND_TERRITORIES_U1 as a unique index on TERRITORY_CODE alone. ZD_EDITION_NAME reflects the editioning support introduced in later releases.

• TERRITORY_CODE — the two-letter upper case ISO 3166 entity name (for example, 'US'), and the primary business-key candidate.
• ISO_NUMERIC_CODE — the ISO numeric entity code associated with the territory.
• ALTERNATE_TERRITORY_CODE — an alternative code, used for the VAT member state code for countries within the European Economic Community.
• ADDRESS_STYLE and ADDRESS_VALIDATION — the style of address used in the country and the validation required for addresses in that country.
• BANK_INFO_STYLE and BANK_INFO_VALIDATION — the style and validation requirements for bank numbers in the country.
• NLS_TERRITORY — the Oracle internal territory code used for language and territory-dependent formatting; indexed by the nonunique FND_TERRITORIES_N1.
• EU_CODE — the European Union numeric entity code.
• OBSOLETE_FLAG — Y or N, indicating territories that are no longer in active use.
• ISO_TERRITORY_CODE — the ISO three-character territory code.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide the audit trail maintained by the Applications framework.

Common Use Cases and Queries

FND_TERRITORIES is most frequently accessed to translate a stored territory code into a user-facing country name by joining to the translation table, and to determine address and bank formatting rules for a given country. A typical lookup resolves the country name for a party or location:

• SELECT t.territory_code, t.iso_numeric_code, t.address_style FROM fnd_territories t WHERE t.obsolete_flag = 'N' — lists all active territories.
• Joining FND_TERRITORIES to FND_TERRITORIES_TL on TERRITORY_CODE to retrieve the translated territory name in a specific language.
• Filtering by NLS_TERRITORY using the FND_TERRITORIES_N1 index when resolving application-level territory defaults.
• Reporting on EU_CODE and ALTERNATE_TERRITORY_CODE for European VAT and Intrastat reporting.
• Validating address or bank information entry screens by reading ADDRESS_VALIDATION and BANK_INFO_VALIDATION for the country in question.

Related Objects

FND_TERRITORIES is referenced by a broad set of transactional and setup tables. The most significant relationships include:

• FND_TERRITORIES_TL — holds translated territory names, joined on TERRITORY_CODE.
• HZ_LOCATIONS — joined on COUNTRY = TERRITORY_CODE; the primary address reference for parties and sites.
• HZ_PARTIES and HZ_ORGANIZATION_PROFILES — joined on HOME_COUNTRY.
• HZ_GEOGRAPHIES — joined on GEOGRAPHY_CODE.
• FND_CURRENCIES — joined on ISSUING_TERRITORY_CODE.
• IBY_PAYMENTS_H and IBY_DOCUMENTS_PAYABLE_H — joined on COUNTRY for payment processing.
• ZX_REGIMES_B and ZX_PARTY_TAX_PROFILE — joined on COUNTRY_CODE for tax configuration.
• MTL_COUNTRY_ASSIGNMENTS and OKL_INS_POLICIES_B — joined on TERRITORY_CODE for inventory and leasing processing.