Search Results fnd_executables_tl




Overview
Explore in AI Chat

Overview

The FND_EXECUTABLES_TL table is a core Application Object Library table within the Oracle E-Business Suite (EBS) architecture, specifically designed to support multilingual capabilities. It stores translated text for the names and descriptions of executables, which are program units defined in the FND_EXECUTABLES table. These executables represent concurrent programs, spawned functions, and other runnable entities within the system. The '_TL' suffix denotes it as a translation table, a standard EBS design pattern for enabling a single installation to support multiple languages. Its role is critical for ensuring that the user-facing names of concurrent programs and other executables are displayed correctly in the language selected by the end-user, thereby facilitating global deployment and usability.

Key Information Stored

The table's structure centers on pairing executable definitions with language codes to hold their localized representations. Its primary keys enforce uniqueness and data integrity: one on APPLICATION_ID, LANGUAGE, and USER_EXECUTABLE_NAME, and another on APPLICATION_ID, EXECUTABLE_ID, and LANGUAGE. Key columns include EXECUTABLE_ID (linking to FND_EXECUTABLES), APPLICATION_ID, and LANGUAGE (linking to FND_LANGUAGES), which together identify a unique translation row. The core translated data is held in USER_EXECUTABLE_NAME and DESCRIPTION. The SOURCE_LANG column records the original language of the translation seed data (typically 'US'), while standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track audit information, referencing FND_USER and FND_LOGINS.

Common Use Cases and Queries

This table is primarily accessed by the EBS framework to display translated concurrent program names in the Submit Requests form and various reports. Common technical and reporting use cases involve joining it with the base table to retrieve executable details for a specific language. A typical query pattern for developers and functional consultants is to identify the translated name of a concurrent program for troubleshooting or documentation.

  • Retrieve Translated Executable Details: SELECT e.EXECUTABLE_NAME, tl.USER_EXECUTABLE_NAME, tl.DESCRIPTION FROM fnd_executables e, fnd_executables_tl tl WHERE e.executable_id = tl.executable_id AND e.application_id = tl.application_id AND tl.language = USERENV('LANG') AND e.executable_name = 'MY_PROGRAM';
  • Audit Translations for an Application: SELECT tl.USER_EXECUTABLE_NAME, tl.LANGUAGE, tl.LAST_UPDATE_DATE FROM fnd_executables_tl tl WHERE tl.application_id = 275 ORDER BY tl.USER_EXECUTABLE_NAME, tl.LANGUAGE;

Related Objects

FND_EXECUTABLES_TL has integral relationships with several key Application Object Library tables. Its existence is dependent on the base definition table, FND_EXECUTABLES, via a foreign key relationship on the composite (APPLICATION_ID, EXECUTABLE_ID). It references FND_LANGUAGES twice: for the LANGUAGE of the translation row and for the SOURCE_LANG. For audit trail integrity, it maintains foreign keys to FND_USER (for CREATED_BY and LAST_UPDATED_BY) and FND_LOGINS (for LAST_UPDATE_LOGIN). From a functional perspective, this table is closely related to the FND_CONCURRENT_PROGRAMS table, as the executable's translated name stored here is what users see when submitting a concurrent request.