Search Results fnd_form_tl_u1

Overview

APPLSYS.FND_FORM_TL is the translation (TL) table for Oracle E-Business Suite application forms registered in the Oracle Forms-based runtime environment. Every form definition stored in FND_FORM has one translation row per installed language, holding the language-specific form title and description presented to the user. Because Oracle EBS supports multilingual deployments, the base definition row lives in a non-translated table while FND_FORM_TL carries the display text keyed by LANGUAGE, with SOURCE_LANG indicating which language row acts as the source of truth for untranslated columns.

The table resides in the APPS_TS_SEED tablespace, which is reserved for seeded setup data that is delivered with the application and typically patched by Oracle rather than maintained by end users. Rows are created for each form in each application in each installed language, so the table grows as languages are enabled. XML Publisher, Oracle Forms runtime, and menu/navigation utilities all resolve the localized form title from this object.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. The composite primary key of (APPLICATION_ID, FORM_ID, LANGUAGE) functions as the hub anchor, while the translated descriptive attributes such as USER_FORM_NAME and DESCRIPTION behave as satellite payload. Note that in 12.2.2 an additional ZD_EDITION_NAME column participates in the unique indexes, indicating the edition-based redefinition pattern used for online patching in multi-tenant capable releases.

Key Information Stored

The primary key FND_FORM_TL_PK is the composite of APPLICATION_ID, FORM_ID, and LANGUAGE, which uniquely identifies a localized row. Two unique indexes serve as business-key candidates: FND_FORM_TL_U1 (APPLICATION_ID, FORM_ID, LANGUAGE, ZD_EDITION_NAME) reinforces uniqueness under editioning, and FND_FORM_TL_U2 (USER_FORM_NAME, APPLICATION_ID, LANGUAGE, ZD_EDITION_NAME) enforces uniqueness of the display title per application per language. The most significant columns are:

• APPLICATION_ID — identifier of the owning application; foreign key to FND_FORM.
• FORM_ID — identifier of the registered form within the application.
• LANGUAGE — the language in which the row's text is written.
• USER_FORM_NAME — the translated form title shown to end users (up to 80 characters).
• DESCRIPTION — a longer textual description of the form (up to 240 characters).
• SOURCE_LANG — the language whose text this row mirrors when translation is incomplete.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns for audit traceability.
• ZD_EDITION_NAME — the edition identifier used by 12.2 online patching.

Common Use Cases and Queries

Typical uses include generating a catalog of localized form titles, auditing missing translations, and joining to FND_FORM for base metadata. A query listing titles in a specific language using the U1 business key:

• SELECT application_id, form_id, language, user_form_name FROM applsys.fnd_form_tl WHERE language = 'US' ORDER BY user_form_name;
• Detect untranslated rows where source_lang is populated and the language differs: SELECT * FROM fnd_form_tl WHERE source_lang <> language;
• Join to the base form definition: SELECT f.form_name, t.user_form_name FROM fnd_form f JOIN fnd_form_tl t ON f.application_id = t.application_id AND f.form_id = t.form_id AND t.language = 'US';

Related Objects

The dominant relationship is to the base (non-translated) table FND_FORM, joined on APPLICATION_ID and FORM_ID. The view APPS.FND_FORM_TL provides an application-facing synonym wrapper referenced in the dependency metadata. Additional relevant objects include FND_FORM_TL_U1 and FND_FORM_TL_U2 indexes for lookup performance, FND_APPLICATION_TL for localized application names that combine with form titles in navigation trees, FND_MENUS and FND_MENU_ENTRIES which reference forms for menu-driven navigation, and FND_COMPILED_MENU_FUNCTIONS for runtime menu resolution. Administrator-facing forms such as the Form Registration form (FND_FNDFLUPD) write to FND_FORM and this translation table.