Search Results fnd_territories_tl

Overview

The FND_TERRITORIES_TL table is a core translation table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It stores translated, language-specific versions of the territory names defined in its base table, FND_TERRITORIES. This table is fundamental to the EBS Multi-Language Support (MLS) architecture, enabling the application to display country and territory names in the language of the user's session. Its role is to separate translatable descriptive data from the static, language-independent codes and attributes stored in the base table, thereby facilitating global deployments.

Key Information Stored

The table's structure is designed to support a one-to-many relationship between a territory and its translated names. The primary key is a composite of TERRITORY_CODE and LANGUAGE, ensuring a unique entry for each territory in each installed language. The TERRITORY_CODE is a foreign key that links to the FND_TERRITORIES base table. The LANGUAGE column holds the language code (e.g., 'US' for American English). The primary data columns are TERRITORY_SHORT_NAME and TERRITORY_NAME, which hold the translated versions of the territory's common name and its full official name, respectively. The TERRITORY_SHORT_NAME column is also part of a unique key constraint (FND_TERRITORIES_TL_UK1) in conjunction with the LANGUAGE column.

Common Use Cases and Queries

This table is primarily accessed by the application's runtime engine to resolve territory descriptions for forms, reports, and lists of values (LOVs). A common reporting use case is to generate a list of all installed territories with their names in a specific language for reference data validation. Developers and administrators frequently query this table to verify translation completeness or to troubleshoot display issues. A standard query pattern utilizes the NLS_LANGUAGE session parameter or a specified language code to retrieve the appropriate translations, often joining to the base table for additional attributes.

• Sample Query for Session Language: SELECT ft.TERRITORY_CODE, ftt.TERRITORY_NAME FROM FND_TERRITORIES ft, FND_TERRITORIES_TL ftt WHERE ft.TERRITORY_CODE = ftt.TERRITORY_CODE AND ftt.LANGUAGE = USERENV('LANG');
• Verifying Translations: SELECT TERRITORY_CODE, COUNT(LANGUAGE) FROM FND_TERRITORIES_TL GROUP BY TERRITORY_CODE HAVING COUNT(LANGUAGE) < (SELECT COUNT(*) FROM FND_LANGUAGES WHERE INSTALLED_FLAG = 'I');

Related Objects

The FND_TERRITORIES_TL table has a direct and essential relationship with its parent base table. It is designed to extend the data in FND_TERRITORIES for multilingual support.

• Primary Base Table (Foreign Key Relationship): The table FND_TERRITORIES_TL references the table FND_TERRITORIES via the foreign key column TERRITORY_CODE. This enforces referential integrity, ensuring every translated record corresponds to a valid territory code in the base table.
• Key Dependencies: The table's existence is predicated on FND_TERRITORIES. Applications, APIs, and views that display translated territory names (such as standard LOVs for countries) will inherently depend on the data in FND_TERRITORIES_TL, joining it to FND_TERRITORIES using the TERRITORY_CODE and LANGUAGE columns.