Search Results fnd_objects_vl




Overview

FND_OBJECTS_VL is a reporting and integration view in the Oracle E-Business Suite Application Object Library (FND) product. It is owned by the APPS schema and carries a VALID status in both EBS 12.1.1 and 12.2.2. The "_VL" suffix indicates a "view language" object, meaning the view couples a base (non-translated) table with its translation table so that descriptive columns are returned in the session's current language. This makes FND_OBJECTS_VL the standard, language-aware access point for metadata about registered application objects, including those integrated with Oracle iRepository (IREP).

In EBS, FND_OBJECTS and its companion tables form part of the Application Object Library metadata repository. They describe objects such as tables, views, and other database entities that Oracle Applications recognizes, along with primary key definitions and iRepository packaging attributes. FND_OBJECTS_VL presents this information as a single logical source, which is why it appears in dictionary-driven reports, diagnostics, and integration queries that must respect the user's language setting.

Underlying Base Objects

Per the documented view text, FND_OBJECTS_VL is defined over two base objects, both referenced through synonyms in the APPS schema:

  • FND_OBJECTS — supplies the non-translated, structural columns, aliased as B in the view definition.
  • FND_OBJECTS_TL — supplies the translated descriptive columns, aliased as T.

The join condition is B.OBJECT_ID = T.OBJECT_ID AND T.LANGUAGE = USERENV('LANG'). The predicate on USERENV('LANG') restricts translation rows to the language of the current session, which is what differentiates this view from querying FND_OBJECTS directly. The ROW_ID column is derived from B.ROWID. The referenced objects are documented as SYNONYM entries, consistent with standard APPS-schema exposure of the underlying FND tables.

Key Columns

The view exposes a broad column set. Structural and identity columns include:

Translated columns are DISPLAY_NAME and DESCRIPTION, sourced from FND_OBJECTS_TL. Standard audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

A substantial block of IREP columns describes iRepository packaging metadata, including IREP_NAME, IREP_OBJECT_TYPE, IREP_PRODUCT, IREP_COMPATIBILITY, IREP_SCOPE, IREP_LIFECYCLE, IREP_SOURCE_FILE_PRODUCT, IREP_SOURCE_FILE_PATH, IREP_SOURCE_FILE_NAME, IREP_SOURCE_FILE_VERSION, IREP_DESCRIPTION, IREP_XML_DESCRIPTION, IREP_STANDARD, IREP_STANDARD_VERSION, IREP_STANDARD_SPEC, IREP_DEF_CLASS, IREP_CLASS_NAME, IREP_IS_FILTER, IREP_IS_EXPRESSION, IREP_LDR_PP_FLAG, and IREP_HIDE_SCHEMA. Load diagnostics are exposed through OPEN_INTERFACE_FLAG, LOAD_ERR, and LOAD_ERR_MSGS.

Common Use Cases and Queries

Typical scenarios include resolving an application object to its database name and primary key structure, extracting iRepository packaging attributes for integration or migration analysis, and producing language-aware object inventories. The view is also useful when diagnosing object load errors.

Query the translated name and description for a given object:

SELECT object_id, obj_name, display_name, description
FROM   fnd_objects_vl
WHERE  obj_name = :object_name;

List objects for an application with their database object names and primary key columns:

SELECT obj_name, database_object_name,
       pk1_column_name, pk2_column_name
FROM   fnd_objects_vl
WHERE  application_id = :app_id
ORDER  BY obj_name;

Inspect iRepository packaging details and load status:

SELECT obj_name, irep_name, irep_object_type, irep_product,
       irep_standard, irep_standard_version,
       open_interface_flag, load_err, load_err_msgs
FROM   fnd_objects_vl
WHERE  irep_name IS NOT NULL;

Because the translation join enforces LANGUAGE = USERENV('LANG'), results for DISPLAY_NAME and DESCRIPTION reflect the session language. Queries that require a specific language regardless of session settings should join FND_OBJECTS_TL directly rather than relying on this view.