Results for “executable_id”

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

Overview

FND_EXECUTABLES_TL is the translation table for FND_EXECUTABLES, the Application Object Library (FND) base table that defines executable programs and concurrent program registrations in Oracle E-Business Suite. It resides in the APPLSYS schema and is available in both 12.1.1 and 12.2.2. Its purpose is to hold language-specific, user-facing text attributes of executables — most importantly the translated executable name and description — enabling multilingual concurrent program listings, Request Group and Request Set definitions, and SRS run-time forms (such as Run Concurrent Program and Submit Requests) to render program names and descriptions in the session language.

From a Data Vault modeling perspective, the metadata suggests FND_EXECUTABLES_TL behaves as a link entity: it resolves the association between a language and the descriptive attributes belonging to FND_EXECUTABLES, rather than acting as a pure descriptive satellite. The classification is heuristic — mined from the foreign key structure, which pairs LANGUAGE (and SOURCE_LANG) with the executable identity columns — and should be treated as a design suggestion, not a hard schema rule.

Key Information Stored

The table is narrow (12 columns) and its content is best understood as a language-keyed projection of master executable attributes:

• APPLICATION_ID and EXECUTABLE_ID — the composite identifier of the parent executable row in FND_EXECUTABLES, and the FK anchor to that table.
• LANGUAGE — the installed language of the translation row; part of both unique indexes and the FK to FND_LANGUAGES.
• SOURCE_LANG — the base language from which the translation was derived; also FK to FND_LANGUAGES.
• USER_EXECUTABLE_NAME — the translatable, user-visible executable name. This is a business-key candidate, appearing in the unique index FND_EXECUTABLES_TL_U1 alongside APPLICATION_ID, LANGUAGE, and ZD_EDITION_NAME.
• DESCRIPTION — the translated description of the executable shown in program listings and concurrent manager reports.
• ZD_EDITION_NAME — the editioning column used by EBS 12.2 online patching; it participates in the unique indexes and separates editions of a row.
• Audit/ownership columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — FK to FND_USER and FND_LOGINS respectively.

The surrogate/business keys differ: FND_EXECUTABLE_TL_PK uses (APPLICATION_ID, EXECUTABLE_ID, LANGUAGE), while FND_EXECUTABLES_TL_UK1 uses (APPLICATION_ID, LANGUAGE, USER_EXECUTABLE_NAME) — the latter is the human-readable business key. Physical indexes U1 and U2 add ZD_EDITION_NAME to support editioned lookups.

Common Use Cases and Queries

Typical reporting usage retrieves the translated program name and description for a session language, or audits which languages a given executable is translated into. A representative join pattern is:

• Translated program listing: SELECT e.EXECUTABLE_ID, t.USER_EXECUTABLE_NAME, t.DESCRIPTION FROM APPS.FND_EXECUTABLES e, APPS.FND_EXECUTABLES_TL t WHERE e.APPLICATION_ID = t.APPLICATION_ID AND e.EXECUTABLE_ID = t.EXECUTABLE_ID AND t.LANGUAGE = USERENV('LANG');
• Language coverage audit: count of distinct LANGUAGE values per EXECUTABLE_ID, useful before a rollout or translation patch.
• Reverse lookup by business key: find an executable via USER_EXECUTABLE_NAME and LANGUAGE when only the display name is known.
• Reconciliation with FND_EXECUTABLES to detect executables missing translated rows for the base language.

Because the table is a translation table, querying it directly returns the internal LANGUAGE code (e.g., 'US'); transforming via FND_LANGUAGES yields the display name.

Related Objects

• FND_EXECUTABLES — the parent/master table; joined on APPLICATION_ID and EXECUTABLE_ID.
• FND_LANGUAGES — referenced twice through LANGUAGE and SOURCE_LANG, providing language names.
• FND_USER — referenced via CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS — referenced via LAST_UPDATE_LOGIN.
• FND_CONCURRENT_PROGRAMS — the concurrent program definition that consumes the executable and displays translated names.
• FND_REQUEST_GROUPS / FND_REQUEST_SET_PROGRAMS — deliver and submit executables by display name to users.

These relationships are documented FKs, and the strong dependence on FND_EXECUTABLES makes the pair FND_EXECUTABLES / FND_EXECUTABLES_TL the authoritative source for program-name rendering across FND reporting surfaces.