Search Results execution_file_name

Overview

FND_EXECUTABLES_VL is a view in the APPS schema of Oracle E-Business Suite, owned by the Application Object Library (FND) product. It is a "VL" (view-language) view, meaning it presents translated, language-specific descriptive columns joined to the base transactional data. Its principal purpose is to expose the definition of every registered concurrent program executable in the E-Business Suite in the language of the current session, determined by USERENV('LANG').

For users and integrators searching on execution_file_path, FND_EXECUTABLES_VL is significant because it is one of the few reporting views that surfaces the EXECUTION_FILE_PATH column directly, alongside the executable name, execution method, and the translated user-facing executable name. This makes it the primary dictionary-accessible source for determining how a concurrent program is physically invoked — whether as a Java class, PL/SQL stored procedure, host script, or Oracle Reports executable — and where the corresponding file resides on the application tier.

The view is marked VALID and is described in ETRM as having been retrofitted, reflecting its inclusion in the consolidated EBS documentation set for releases 12.1.1 and 12.2.2.

Underlying Base Objects

FND_EXECUTABLES_VL is defined over two documented base objects:

• FND_EXECUTABLES — the base table storing the non-translated (language-independent) attributes of each executable, including application, executable name, execution method, file name, subroutine name, and execution file path.
• FND_EXECUTABLES_TL — the translation table storing the language-specific columns, notably USER_EXECUTABLE_NAME and DESCRIPTION.

The view joins these two objects on APPLICATION_ID and EXECUTABLE_ID, with an additional filter constraining LANGUAGE to the session language. It also exposes the ROWID of the base FND_EXECUTABLES row as ROW_ID. Both underlying objects are referenced within the view definition as synonyms, consistent with standard EBS dictionary practice.

Key Columns

The view exposes the following columns:

• ROW_ID — the ROWID of the underlying FND_EXECUTABLES record.
• APPLICATION_ID — the application owning the executable.
• EXECUTABLE_ID — the unique identifier of the executable.
• EXECUTABLE_NAME — the internal (untranslated) name of the executable.
• EXECUTION_METHOD_CODE — the method of invocation, such as I (PL/SQL stored procedure), J (Java), H (host), or O (Oracle Reports).
• EXECUTION_FILE_NAME — the file or package referenced by the executable.
• EXECUTION_FILE_PATH — the physical path to the executable file on the application tier; this is the column directly relevant to the search term.
• SUBROUTINE_NAME — the specific subroutine or entry point invoked when applicable.
• USER_EXECUTABLE_NAME — the translated, user-facing name.
• DESCRIPTION — the translated description.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include auditing concurrent program definitions, diagnosing invocation failures, and migrating or documenting custom executables. To locate the file path for a specific executable:

SELECT executable_name, execution_method_code, execution_file_name, execution_file_path, user_executable_name FROM apps.fnd_executables_vl WHERE executable_name = 'FNDSCRMT';

To enumerate all host-type executables and their paths:

SELECT executable_name, execution_file_path FROM apps.fnd_executables_vl WHERE execution_method_code = 'H';

Because the view is bilingual by design, callers should set the session language appropriately to obtain the correct USER_EXECUTABLE_NAME and DESCRIPTION values.