Search Results fnd_form_functions_tl

Overview

The FND_FORM_FUNCTIONS_TL table is a core Application Object Library table within Oracle E-Business Suite (EBS) that stores translated user-facing text for form functions. A form function, defined in the base FND_FORM_FUNCTIONS table, represents a navigable entry point to an application's functionality, such as a menu item or a responsibility-specific task. The primary role of the _TL (Translation) table is to enable the multilingual support of the EBS interface by holding the translated names and descriptions of these functions for each installed language. This separation of base data from its translated text is a standard design pattern in Oracle Applications, allowing for the simultaneous deployment and use of the system across diverse linguistic regions without modifying core application logic.

Key Information Stored

The table's structure is designed to map a single form function to multiple language-specific text entries. Its critical columns, as indicated by the primary keys, are FUNCTION_ID and LANGUAGE. The FUNCTION_ID is a foreign key to the FND_FORM_FUNCTIONS table, uniquely identifying the base function. The LANGUAGE column holds the language code (e.g., 'US' for American English, 'D' for German). The primary user-facing data is stored in the USER_FUNCTION_NAME and DESCRIPTION columns, which contain the translated text for the function's display name and its explanatory description, respectively. The table also includes standard translation table columns such as SOURCE_LANG, which records the original language of the data.

Common Use Cases and Queries

This table is central to any reporting or troubleshooting involving the EBS navigational menu structure in a multilingual environment. A common use case is identifying or verifying the display text for a specific function across different languages. Developers and functional consultants often query this table to resolve issues where menu items appear incorrectly or are missing for specific responsibilities. A typical query joins FND_FORM_FUNCTIONS_TL with its base table to retrieve all translations for a known function.

Sample Query:
SELECT ff.function_name, fftl.language, fftl.user_function_name, fftl.description FROM fnd_form_functions ff, fnd_form_functions_tl fftl WHERE ff.function_id = fftl.function_id AND ff.function_name = 'MY_CUSTOM_FUNCTION';

Another critical use case is during the development of custom reports or integrations that must present function names in the user's session language, requiring a join on LANGUAGE = USERENV('LANG').

Related Objects

The FND_FORM_FUNCTIONS_TL table has a direct and essential relationship with several key EBS objects:

• FND_FORM_FUNCTIONS: This is the base table. The _TL table references it via the foreign key on FUNCTION_ID. All translatable functions must first exist here.
• FND_MENU_ENTRIES: Menu structures reference form functions. The translated name from FND_FORM_FUNCTIONS_TL is what ultimately displays in the application's menus.
• FND_RESP_FUNCTIONS: This table maps functions to responsibilities, controlling security. The user-facing name for the secured function is pulled from the _TL table.
• Standard Translation Views: Oracle provides language-specific views (suffixed with _VL) that automatically filter _TL tables based on the current session language, which applications typically use instead of querying the _TL table directly.