Search Results fnd_application_tl




Overview
Explore in AI Chat

Overview

The FND_APPLICATION_TL table is a core repository for translated text associated with registered applications within Oracle E-Business Suite (EBS). As a Translation Table (indicated by the '_TL' suffix), it is a fundamental component of the Application Object Library (FND) module, enabling the multi-language support (NLS) that is critical for global deployments. This table stores language-specific descriptions and names for each application defined in its parent table, FND_APPLICATION. Its role is to provide the correct application title and description to the user interface, reports, and other system components based on the user's session language, thereby facilitating a localized user experience.

Key Information Stored

The table's structure is designed to support a one-to-many relationship between a base application and its translations. The primary key is a composite of APPLICATION_ID and LANGUAGE, ensuring a unique entry per application per language. Key columns include APPLICATION_ID, which links to FND_APPLICATION.APPLICATION_ID; LANGUAGE, which holds the language code (e.g., 'US', 'FR', 'DE'); APPLICATION_NAME, which stores the translated name of the application; and DESCRIPTION, which holds the translated descriptive text. The table also includes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing and a SOURCE_LANG column to track the original language of the data.

Common Use Cases and Queries

A primary use case is retrieving the localized application name for display within forms or custom reports. Developers and system administrators frequently query this table to verify or audit translations, especially after patches or upgrades that may add new applications. A common query pattern involves joining with the base FND_APPLICATION table to get both the internal short name and its translated equivalent. For example, to find all French translations for active applications, one might use:

  • SELECT fa.APPLICATION_SHORT_NAME, fat.APPLICATION_NAME, fat.DESCRIPTION
  • FROM FND_APPLICATION fa, FND_APPLICATION_TL fat
  • WHERE fa.APPLICATION_ID = fat.APPLICATION_ID
  • AND fat.LANGUAGE = 'FR'
  • AND fa.APPLICATION_NAME LIKE '%Payables%';

Another critical use case is during data migration or setup, where scripts may need to reference an application by its internal ID, which remains constant across all languages, rather than its translated name.

Related Objects

The most direct and essential relationship is with the base table FND_APPLICATION, as defined by the foreign key FND_APPLICATION_TL.APPLICATION_ID referencing FND_APPLICATION.APPLICATION_ID. The FND_APPLICATION table stores the non-translatable attributes like APPLICATION_SHORT_NAME. This table is also referenced by various views and APIs that present application information to other modules and tools within EBS. For instance, the FND_APPLICATION_VL view is a common source for reporting as it combines base and translated data. Understanding this TL table is also crucial when working with the standard AD_ZD_SEEDED_DATA package and other utilities responsible for managing multi-lingual seed data.