Results for “fnd_form_functions_tl”

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

Overview

FND_FORM_FUNCTIONS_TL is the translation (TL) table for FND_FORM_FUNCTIONS in Oracle E-Business Suite, owned by the APPLSYS schema and belonging to the FND — Application Object Library product. Every EBS function — whether an Oracle Forms-based function, a JSP/HTML function, or a non-form (subfunction) entry — is registered in FND_FORM_FUNCTIONS with a single functional definition, and the user-facing text for that function is stored in this translation table, one row per installed language. The table therefore holds the translatable attributes of a function, most notably its user function name and description, keyed to the base function row by FUNCTION_ID and to a specific language by LANGUAGE.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is best modeled as satellite-leaning. It extends FND_FORM_FUNCTIONS with descriptive, language-dependent context rather than representing an independent business entity (hub) or an association between two entities (link). In a Data Vault design, FND_FORM_FUNCTIONS would serve as the hub, FUNCTION_ID as the hub key, and this table as a multi-active satellite keyed by FUNCTION_ID and LANGUAGE.

Key Information Stored

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

• FUNCTION_ID — Surrogate identifier of the parent function; together with LANGUAGE it forms the primary key FND_FORM_FUNCTIONS_TL_PK.
• LANGUAGE — The installed language code for the translation row; the second component of the primary key and an essential discriminator in every query.
• USER_FUNCTION_NAME — The translated user function name displayed in the Navigator, menus, and forms. This is the primary business-key candidate: unique index FND_FORM_FUNCTIONS_TL_UK1 covers USER_FUNCTION_NAME and LANGUAGE, and the documented unique index FND_FORM_FUNCTIONS_TL_U1 covers FUNCTION_ID, LANGUAGE, and ZD_EDITION_NAME.
• DESCRIPTION — The translated description of the function, used in setup screens, reports, and diagnostic output.
• SOURCE_LANG — The language of the source text from which a translation was derived; used by the translation (NLS) utilities and the Translation Synchronization process.
• ZD_EDITION_NAME — Editioning column consistent with EBS 12.2 online patching and the Edition-Based Redefinition model; part of unique index U1.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording row creation and last modification.

Because FUNCTION_ID is both the primary-key component and the foreign key to FND_FORM_FUNCTIONS, the surrogate-to-business relationship is clear: FUNCTION_ID is the surrogate join key, while USER_FUNCTION_NAME plus LANGUAGE is the human-recognizable business key.

Common Use Cases and Queries

Typical uses include resolving a function's displayed name in a specific language, auditing which functions lack translations for a given language, and joining functions to menus and responsibilities for security reporting.

• Retrieve the user function name and description for a function identifier in a chosen language:

SELECT t.function_id, t.user_function_name, t.description
FROM   applsys.fnd_form_functions_tl t
WHERE  t.function_id = :function_id
AND    t.language = USERENV('LANG');

• Find functions missing a translation row for a target language (gap analysis after a patch or language install):

SELECT f.function_id
FROM   applsys.fnd_form_functions f
WHERE  f.function_id NOT IN
       (SELECT t.function_id
        FROM   applsys.fnd_form_functions_tl t
        WHERE  t.language = 'FR');

• Reporting on all translated names for a function across installed languages, useful when validating NLS patches or comparing source and translated text via SOURCE_LANG.
• Joining to FND_MENUS and FND_MENU_ENTRIES through FUNCTION_ID to produce responsibility/function access reports with readable names.

Related Objects

• FND_FORM_FUNCTIONS — Parent table; joined on FND_FORM_FUNCTIONS_TL.FUNCTION_ID = FND_FORM_FUNCTIONS.FUNCTION_ID. Provides the non-translatable function attributes.
• FND_MENU_ENTRIES — Menu entries reference FUNCTION_ID, so joining through this table yields menu-to-function hierarchies with translated names.
• FND_MENUS — Joined via menu identifiers to build navigator/security reports.
• FND_RESPONSIBILITY — Responsibilities determine which functions are executable; joined indirectly through menus.
• FND_APPLICATION — Identifies the owning application of each function for cross-application reporting.
• FND_COMPILED_MENU_FUNCTIONS — Materialized menu-function access data that resolves to this table for display names.
• FND_LANGUAGES — Reference table validating the LANGUAGE values present in this table.

In EBS 12.1.1 the table behaves as a standard TL table; in 12.2.2 the presence of ZD_EDITION_NAME and the U1 unique index reflects the editioning model introduced with online patching.