Search Results execution_method_code




Overview
Explore in AI Chat

Overview

FND_EXECUTABLES_FORM_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Application Object Library (FND). It is documented in ETRM for both 12.1.1 and 12.2.2 with the annotation "Retrofitted," and carries a VALID status. The view presents executable registration metadata — the definitions that tell Oracle EBS how a concurrent program is physically invoked — joined to the owning application name. Unlike FND_EXECUTABLES_VL, which is a translatable (VL) view keyed on the base FND_EXECUTABLES table, FND_EXECUTABLES_FORM_V is a convenience view intended for forms-driven lookups and ad hoc reporting where a denormalized application name is required alongside executable attributes.

The view is read-only by construction; it exposes no DML surface and is not itself a base table. Its practical role is to support queries that inspect how concurrent programs and other executables are defined, particularly the EXECUTION_METHOD_CODE value that determines invocation behavior.

Underlying Base Objects

Per the documented ETRM metadata, FND_EXECUTABLES_FORM_V is defined over exactly two referenced base objects:

  • FND_EXECUTABLES_VL (VIEW) — the translatable executable view over FND_EXECUTABLES, aliased E in the view text.
  • FND_APPLICATION_VL (VIEW) — the translatable application name view over FND_APPLICATION, aliased A in the view text.

The join condition is E.APPLICATION_ID = A.APPLICATION_ID, so every row returned corresponds to one executable that owns a valid application reference. Because the view draws from VL views rather than the base tables directly, it inherits language-dependent resolution of the DESCRIPTION and APPLICATION_NAME columns for the session's language.

Key Columns

The view projects select attributes from FND_EXECUTABLES_VL plus APPLICATION_NAME from FND_APPLICATION_VL. Documented columns include:

  • ROW_ID — row identifier for the executable record.
  • APPLICATION_ID / APPLICATION_NAME — the owning application's ID (join key) and its resolved display name.
  • EXECUTABLE_ID / EXECUTABLE_NAME — the unique identifier and user-facing name of the executable.
  • EXECUTION_METHOD_CODE — the invocation method that governs how the executable is run. This is the column the user searched for. Values such as H, I, J, K, L, P, and Q distinguish host (OS) executables, immediate/Java-based invocation, PL/SQL stored procedures, and similar mechanisms. It is the decisive attribute for interpreting the remaining file-related columns.
  • EXECUTION_FILE_NAME, EXECUTION_FILE_PATH, SUBROUTINE_NAME — the physical file, path, and entry-point identifier applicable per execution method. SUBROUTINE_NAME generally applies to PL/SQL or Java invocation, while EXECUTION_FILE_NAME and EXECUTION_FILE_PATH apply to host executables.
  • USER_EXECUTABLE_NAME — the executable name as presented to the end user.
  • DESCRIPTION — language-resolved description of the executable.
  • Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The primary use cases are auditing concurrent program definitions, inventorying executables by execution method, and troubleshooting invocation errors where the wrong EXECUTION_METHOD_CODE or mismatched file/path causes failures. The view is also convenient for reconciliation reports comparing host-based versus PL/SQL-based executables across applications.

List executables by method for a given application:

  • SELECT executable_name, user_executable_name, execution_method_code, execution_file_name, subroutine_name FROM fnd_executables_form_v WHERE application_name = 'Application Object Library' ORDER BY execution_method_code, executable_name;

Inventory host executables with their paths:

  • SELECT application_name, executable_name, execution_file_name, execution_file_path FROM fnd_executables_form_v WHERE execution_method_code = 'H' ORDER BY application_name, executable_name;

Count executables by method:

  • SELECT execution_method_code, COUNT(*) FROM fnd_executables_form_v GROUP BY execution_method_code ORDER BY 1;