Results for “fnd_application_tl”

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

Overview

FND_APPLICATION_TL is the translation (TL) table for FND_APPLICATION in the Oracle E-Business Suite Application Object Library (FND). It resides in the APPLSYS schema and stores the language-specific attributes of registered applications, most notably the translated display name and description. Where FND_APPLICATION holds the single-row, language-independent definition of each Oracle EBS application (its base application_id, short name, and flags), FND_APPLICATION_TL holds one row per application per installed language. In a multi-language EBS 12.1.1 or 12.2.2 instance, this separation allows application names to appear in the session language of each user without duplicating the core application record. The table is maintained internally by the application registration and language synchronization routines; direct DML is uncommon and typically performed only through supported patching or the applications registration APIs.

From a Data Vault modeling perspective, the FK structure suggests this object is satellite-leaning: its primary key includes the parent APPLICATION_ID plus a LANGUAGE discriminator, and it is wholly dependent on FND_APPLICATION, which behaves as the parent hub. The LANGUAGE column functions as the descriptive context driving each satellite row.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• APPLICATION_ID — Numeric surrogate identifier of the application; part of the primary key FND_APPLICATION_TL_PK and a foreign key to FND_APPLICATION.
• LANGUAGE — Language code for the translated row; the second component of the composite primary key.
• APPLICATION_NAME — Translated, user-facing name of the application; a business-key candidate, appearing in unique index FND_APPLICATION_TL_U2 alongside LANGUAGE and ZD_EDITION_NAME.
• DESCRIPTION — Translated description of the application's purpose.
• SOURCE_LANG — Language in which the source text was originally authored; supports the translation (MLS) framework.
• ZD_EDITION_NAME — Editioning/edition-based redefinition column present in 12.2.2; participates in the unique indexes U1 and U2.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording row creation and modification.

The surrogate primary key is (APPLICATION_ID, LANGUAGE). Business-key candidates are expressed by the unique index FND_APPLICATION_TL_U1 (APPLICATION_ID, LANGUAGE, ZD_EDITION_NAME) and FND_APPLICATION_TL_U2 (APPLICATION_NAME, LANGUAGE, ZD_EDITION_NAME).

Common Use Cases and Queries

The most frequent use is resolving an application's translated name for a given language, often within multilingual reporting or user-interface displays. A typical query joins the base table to its translation:

• Resolve a display name: SELECT t.application_name FROM fnd_application_tl t WHERE t.application_id = :app_id AND t.language = USERENV('LANG');
• List all applications in a language: SELECT application_id, application_name FROM fnd_application_tl WHERE language = 'US' ORDER BY application_name;
• Audit translations present per application: SELECT a.application_short_name, t.language, t.application_name FROM fnd_application_tl t JOIN fnd_application a ON t.application_id = a.application_id ORDER BY a.application_short_name, t.language;

Reporting scenarios include inventorying which applications have been translated into which languages, verifying translation coverage after a language patch, and populating lookup lists in custom concurrent programs or OAF pages that need language-appropriate application labels.

Related Objects

• FND_APPLICATION — Parent table; joined on APPLICATION_TL.APPLICATION_ID = FND_APPLICATION.APPLICATION_ID.
• FND_APPLICATION_TL_PK / FND_APPLICATION_TL_U1 / FND_APPLICATION_TL_U2 — Primary and unique indexes enforcing identity and business-key uniqueness, including ZD_EDITION_NAME in 12.2.2.
• FND_APPLICATION_VL — Convenience view overlaying FND_APPLICATION and its TL rows, commonly used in place of direct joins.
• FND_LANGUAGES and FND_LANGUAGE_TL — Provide the installed and installed-language context for the LANGUAGE column.
• FND_PRODUCT_INSTALLATIONS / FND_PRODUCT_GROUPS — Application registration metadata that references the same application identifiers.
• FND_APP_SERVERS / FND_NODES — Related registration objects keyed by application or server context used during application tier configuration.