Results for “fnd_application_vl”

50+ results




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

Overview

FND_APPLICATION_VL is a validation-level (VL) view in the APPS schema belonging to the FND — Application Object Library product. It is documented as a view of FND_APPLICATION and FND_APPLICATION_TL, combining the language-independent attributes of an Oracle E-Business Suite application with its translated (language-dependent) name and description. The "VL" designation indicates that the view presents translated columns resolved against the session language rather than storing them itself; the translation is driven by the predicate T.LANGUAGE = USERENV('LANG'). The view status is VALID and its definition is unchanged in substance between Oracle EBS 12.1.1 and 12.2.2, making it a stable, long-standing reporting and integration surface across both releases.

In practice, FND_APPLICATION_VL is the canonical reference for the registered applications in an EBS instance — the top-level product groupings such as General Ledger, Payables, Order Management, and the FND foundation itself. Because the registration of applications governs menu structures, responsibility assignments, profile options, and concurrent program ownership, this view appears widely in diagnostics, data-extraction routines, and custom reporting that must present human-readable application names.

Underlying Base Objects

The ETRM metadata documents the view as defined over two synonyms: FND_APPLICATION and FND_APPLICATION_TL.

The view text joins the two tables on APPLICATION_ID and filters FND_APPLICATION_TL to the current session language. It exposes the ROWID of the base FND_APPLICATION row as ROW_ID. This is the standard Oracle multi-language ("_VL") pattern, in which a single view transparently returns the correct translated text for the querying user's language while joining to the single underlying definition row.

Key Columns

  • ROW_ID — the ROWID of the FND_APPLICATION row, useful for direct base-table access.
  • APPLICATION_ID — numeric primary key uniquely identifying each registered application; the join key to responsibilities, menus, and concurrent programs.
  • APPLICATION_SHORT_NAME — the unique short identifier (for example, "SQLGL" for General Ledger) used in profile options and code references.
  • APPLICATION_NAME — the translated display name of the application.
  • DESCRIPTION — the translated descriptive text associated with the application.
  • PRODUCT_CODE — the product code associated with the application, used in various EBS lookup contexts.
  • BASEPATH — the base installation path for the application's product directory.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard "WHO" audit columns.

Common Use Cases and Queries

Typical use cases include converting APPLICATION_ID values stored in responsibility or profile tables into readable names, building lookup lists for custom concurrent programs, and auditing which applications are registered in an instance. A common query retrieving all registered applications is:

  • SELECT application_id, application_short_name, application_name FROM fnd_application_vl ORDER BY application_short_name;

A frequent pattern joins responsibilities to the view to display the owning application of each responsibility. Diagnostic scripts also query APPLICATIONS to confirm registration of a product before troubleshooting missing menus or profile options.