Search Results user_form_name




Overview
Explore in AI Chat

Overview

FND_FORM_TL is the translation table for FND_FORM in the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. It resides in the APPLSYS schema and belongs to the FND — Application Object Library product. Its role is to hold the language-dependent attributes of an Oracle Forms-based form definition, most notably the user-visible form name, so that the same form can present different labels to users operating under different language settings. The base FND_FORM table stores language-independent registration details, while FND_FORM_TL stores one row per installed language.

The ETRM Data Vault classification for this object is satellite-leaning. Under that modeling heuristic, FND_FORM_TL can be treated as a satellite attached to the FND_FORM hub, since it carries descriptive, language-specific attributes keyed by the parent form identity rather than introducing a new independent business entity. This classification is a suggestion mined from the foreign-key structure, not a declarative property of the table.

Key Information Stored

The documented physical schema exposes 12 columns. The most significant of these are:

  • APPLICATION_ID — the application owning the form; part of the primary key and of the foreign key back to FND_FORM.
  • FORM_ID — the numeric identifier of the form; the second component of the primary key.
  • LANGUAGE — the NLS language code for the translated row; completes the primary key.
  • USER_FORM_NAME — the language-specific, user-facing form name shown on menus and navigator entries.
  • DESCRIPTION — a translated description of the form.
  • SOURCE_LANG — the language of the source text from which the translation was derived, used by the translation toolset.
  • ZD_EDITION_NAME — the edition identifier used by the 12.2 Online Patching (Edition-Based Redefinition) model.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each translation row.

The surrogate-style primary key is captured by the constraint FND_FORM_TL_PK, defined over APPLICATION_ID, FORM_ID, and LANGUAGE. Business-key candidates are documented through two unique indexes: FND_FORM_TL_U1 on APPLICATION_ID, FORM_ID, LANGUAGE, and ZD_EDITION_NAME, and FND_FORM_TL_U2 on USER_FORM_NAME, APPLICATION_ID, LANGUAGE, and ZD_EDITION_NAME. The second index demonstrates that a user form name must remain unique within an application and language, which matters when custom forms are registered alongside seeded ones.

Common Use Cases and Queries

The most frequent use of FND_FORM_TL is joining a form registration to its translated name for reporting and troubleshooting. A typical query resolves the displayed form name for a given language:

  • SELECT f.form_id, f.application_id, t.user_form_name FROM fnd_form f, fnd_form_tl t WHERE f.application_id = t.application_id AND f.form_id = t.form_id AND t.language = 'US';
  • Locating the form behind a menu entry, driven by USER_FORM_NAME, supports navigation troubleshooting in 12.1.1 and 12.2.2.
  • Auditing translations: identifying rows where LAST_UPDATED_BY or LAST_UPDATE_DATE indicates a non-seeded modification, which is useful during upgrade or patch validation.
  • Resolving duplicate or conflicting user form names through the FND_FORM_TL_U2 business key.
  • In 12.2.x, filtering by ZD_EDITION_NAME to read the correct edition during online patching.

Related Objects

FND_FORM_TL depends on and is referenced by several FND objects:

  • FND_FORM — the parent registration table; referenced via FND_FORM_TL.APPLICATION_ID and FND_FORM_TL.FORM_ID.
  • FND_FORM_FUNCTIONS — associates functions with forms, and commonly joined to obtain translated form names.
  • FND_APPLICATION / FND_APPLICATION_TL — provide the application name context for the form.
  • FND_MENUS / FND_MENU_ENTRIES — menu entries reference functions tied to forms, so they depend indirectly on the translated name.
  • FND_LANGUAGES — supplies the valid language codes used in the LANGUAGE column and the translation toolset.
  • FND_FORM_TL is populated and maintained by AD translation utilities and the Oracle Forms registration forms rather than by a public PL/SQL API.