Search Results fnd_territories

Overview

The FND_TERRITORIES table is a core reference table within the Oracle E-Business Suite (EBS) Application Object Library (FND). It serves as the master repository for country or territory codes, which are fundamental to the application's global operations. This table provides the standardized list of geopolitical entities used throughout the EBS modules for localization, address validation, tax calculations, legal reporting, and financial processing. Its central role is evidenced by its extensive network of foreign key relationships across numerous product modules, from Financials to Supply Chain and Customer Relationship Management. Maintaining data integrity in FND_TERRITORIES is critical, as it underpins consistent geographical data across the entire application suite.

Key Information Stored

The table's primary key is the TERRITORY_CODE, a short, unique identifier for each country (e.g., 'US', 'GB', 'FR'). While the provided metadata does not list all columns, based on its standard implementation, the table typically stores descriptive and administrative information for each territory. Common columns include TERRITORY_SHORT_NAME, DESCRIPTION, NATIONALITY, ISO_TERRITORY_CODE (aligning with ISO 3166 standards), and ENABLED_FLAG to control active status. The table is complemented by the translated table FND_TERRITORIES_TL, which holds the territory names in different installed languages, enabling multilingual support. The foreign key from FND_CURRENCIES to FND_TERRITORIES links currencies to their respective issuing territories.

Common Use Cases and Queries

This table is primarily used for validation, reporting, and data enrichment. A common use case is populating country list of values (LOVs) in forms across EBS, such as in supplier, customer, or bank account entry. For reporting, it is frequently joined to transaction tables to group data by country. Given the user's search for "iby_payment_reasons_b", a relevant query would involve joining these tables to list payment reasons valid for a specific territory. For instance, to find all active payment reasons for the United Kingdom, one might use:

• SELECT pr.payment_reason_code, pr.name, t.territory_short_name
• FROM iby_payment_reasons_b pr, fnd_territories t
• WHERE pr.territory_code = t.territory_code
• AND t.territory_code = 'GB'
• AND pr.enabled_flag = 'Y';

Another critical use case is data migration, where external country data must be mapped to the standardized codes in FND_TERRITORIES to ensure system compatibility.

Related Objects

As the metadata indicates, FND_TERRITORIES is a hub table with numerous foreign key dependencies. Key related objects include its translation table, FND_TERRITORIES_TL. Within the Oracle Payments module (IBY), it is directly referenced by IBY_PAYMENT_REASONS_B, IBY_BANK_INSTRUCTIONS_B, IBY_DOCUMENTS_PAYABLE_H, and IBY_PAYMENTS_H, linking financial transactions to their relevant country context. In Trading Community Architecture (HZ), tables like HZ_LOCATIONS, HZ_PARTIES, and HZ_GEOGRAPHIES use it to validate country data. Other significant references come from AP_POL_LOCATIONS_B (Procurement), MTL_COUNTRY_ASSIGNMENTS (Inventory), and various Oracle Contracts (OKL) and Human Resources (PA) tables. This wide integration underscores its foundational role in the EBS data model.