Search Results fnd_form_tl_pk

Overview

The FND_FORM_TL table is a core translation table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is owned by the APPLSYS schema and is responsible for storing translated versions of the user-facing names for forms registered within the system. This table enables the EBS application to present form titles and names in the language of the end-user, which is a fundamental requirement for global deployments. Its existence is critical for the application's multi-language support (MLS) and National Language Support (NLS) architecture, separating translatable text from the base definition data stored in its parent table, FND_FORM.

Key Information Stored

The table's structure is designed to support the unique identification of a translation for a specific form. The primary key (FND_FORM_TL_PK) consists of APPLICATION_ID, FORM_ID, and LANGUAGE, ensuring a unique translation entry per form per language. A unique key (FND_FORM_TL_UK1) on APPLICATION_ID, USER_FORM_NAME, and LANGUAGE enforces uniqueness of the translated name within an application and language. Key columns include:

• APPLICATION_ID and FORM_ID: Foreign key columns linking to the FND_FORM table to identify the specific form.
• LANGUAGE: The code (e.g., 'US', 'FR', 'DE') representing the language of the translated text.
• USER_FORM_NAME: The most critical translatable field, storing the form's display name as seen by the end-user in the specified language.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: Standard EBS audit columns tracking record history.

Common Use Cases and Queries

This table is primarily accessed for language-specific application setups, reporting, and troubleshooting. A common scenario is identifying or verifying the translated name of a form for a specific language, such as retrieving the French name for the General Ledger Superuser form. Developers and functional consultants often query this table to validate translation seed data or to generate reports of form names across multiple languages for documentation or upgrade analysis.

Sample SQL to retrieve translated form names for a known form ID:

SELECT f.form_id, tl.language, tl.user_form_name
FROM fnd_form f, fnd_form_tl tl
WHERE f.form_id = tl.form_id
AND f.application_id = tl.application_id
AND f.form_name = 'FNDSCAUS'
ORDER BY tl.language;

Another typical use case involves joining with FND_APPLICATION_TL to get a complete translated application and form listing for a user session's language (e.g., NLS_LANGUAGE).

Related Objects

The FND_FORM_TL table has a direct and essential relationship with its parent table, FND_FORM, which holds the base, non-translatable form definition. The foreign key constraint explicitly defines this dependency on FND_FORM's APPLICATION_ID and FORM_ID columns. In practice, it is also closely related to other TL tables for menus (FND_MENUS_TL) and functions (FND_FORM_FUNCTIONS_TL), which together provide a fully translated navigation path. The FND_APPLICATION_TL table provides the translated application name context. These tables are typically populated and maintained via the standard EBS translation seed data process or using the Oracle Translation Manager utility.