Results for “fnd_executables”

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

Overview

FND_EXECUTABLES is a core Application Object Library (FND) table in Oracle E-Business Suite, owned by the APPLSYS schema. It stores the definition of concurrent program executables — the physical or logical units of code that Oracle EBS runs when a concurrent program, request set function, or stage function is submitted. Every runnable concurrent program must reference an executable row, which tells the concurrent manager how to launch the underlying process (for example, an Oracle Reports file, a PL/SQL package procedure, a Java class, a host script, or a spawned subrequest). The table is therefore foundational to the concurrent processing architecture in both EBS 12.1.1 and 12.2.2, and it participates directly in the definition of concurrent programs, request set stages, and stage function parameters.

From a dimensional modelling perspective, the ETRM metadata classifies FND_EXECUTABLES as hub-leaning. In Data Vault terms this suggests treating it as a hub: a durable, business-key-driven entity whose identity survives edition changes, with descriptive attributes (execution method, file name, subroutine) that could be modelled separately as satellites. The ZD_EDITION_NAME column present in the documented 12.2.2 schema reinforces this, since edition-based redefinition introduces versioning that naturally maps to satellite structures.

Key Information Stored

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

• APPLICATION_ID — identifies the owning application (for example, FND, GL, or INV) and forms part of the composite primary key and of the foreign key to FND_APPLICATION.
• EXECUTABLE_ID — the system-generated surrogate identifier for the executable; combined with APPLICATION_ID it constitutes the primary key FND_EXECUTABLES_PK.
• EXECUTABLE_NAME — the user-visible business name of the executable, unique within an application (FND_EXECUTABLES_UK1 / FND_EXECUTABLES_U2). This is the principal business-key candidate.
• EXECUTION_METHOD_CODE — the launch mechanism, distinguishing immediately-run executables ('I') from spawned ('S') and Oracle Reports ('R') style execution paths.
• EXECUTION_FILE_NAME — the report, package, or program file invoked at runtime.
• SUBROUTINE_NAME — the specific procedure or entry point inside the execution file, relevant for PL/SQL-based executables.
• EXECUTION_FILE_PATH — the directory or path qualifying the execution file, used mainly for host and Java executables.
• ICON_NAME — the icon associated with the executable for presentation purposes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last modified the row and when.
• ZD_EDITION_NAME — the edition discriminator supporting edition-based redefinition in 12.2.2.

Common Use Cases and Queries

The most frequent scenario is resolving which file or procedure a concurrent program actually runs. Because FND_CONCURRENT_PROGRAMS holds EXECUTABLE_APPLICATION_ID and EXECUTABLE_ID, the join is direct:

• Program-to-executable lookup: SELECT cp.concurrent_program_name, e.executable_name, e.execution_method_code, e.execution_file_name, e.subroutine_name FROM fnd_concurrent_programs cp, fnd_executables e WHERE cp.executable_application_id = e.application_id AND cp.executable_id = e.executable_id;
• Inventoring host and Java executables: filter on EXECUTION_METHOD_CODE to list programs whose EXECUTION_FILE_PATH points outside the database, useful for migration and patching impact assessments.
• Request set and stage function analysis: join FND_REQUEST_SET_STAGES on FUNCTION_APPLICATION_ID / FUNCTION_ID, or FND_STAGE_FN_PARAMETERS_TL on APPLICATION_ID / FUNCTION_ID, to trace which executables drive a request set's stage logic.
• Customisation audits: compare CREATED_BY and LAST_UPDATED_BY against standard seed data ranges to identify customer-defined executables before an upgrade.

Related Objects

• FND_APPLICATION — referenced via FND_EXECUTABLES.APPLICATION_ID, providing the application short name and description.
• FND_CONCURRENT_PROGRAMS — the primary consumer, joined through EXECUTABLE_APPLICATION_ID and EXECUTABLE_ID.
• FND_EXECUTABLES_TL — the translated (language) table, linked on APPLICATION_ID and EXECUTABLE_ID, holding the display name per language.
• FND_REQUEST_SET_STAGES — references executables through FUNCTION_APPLICATION_ID and FUNCTION_ID.
• FND_STAGE_FN_PARAMETERS_TL — references executables on APPLICATION_ID and FUNCTION_ID for stage function parameters.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — downstream runtime tables linking submitted requests back to their defining executable.