Search Results bne_layouts_vl




Overview
Explore in AI Chat

Overview

BNE_LAYOUTS_VL is a standard translatable (MLS) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the BNE product family — Web Applications Desktop Integrator (Web ADI) — which provides the Microsoft Excel and Word integration framework used across Oracle E-Business Suite modules. The view presents layout definitions maintained within Web ADI, exposing a user-facing translated name alongside the underlying configuration attributes that govern how integrators render their web-based content.

The object is reported as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its role is primarily that of a read-only reporting and lookup interface: because it is a "_VL" view (View, Logical/Language), it joins the base entity table to its translation table and filters the translated rows to the session language. Application code, diagnostics, and custom reports query this view rather than joining the base tables directly, ensuring that the correct language-specific layout name is returned for the current user session. As with other APPS-owned views, it should be treated as read-only; direct DML against it is not supported, and layout maintenance must flow through the supported Web ADI setup user interface or the underlying base tables.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, exposed in the APPS schema as synonyms:

  • BNE_LAYOUTS_B — the "base" table holding all language-independent attributes of a layout, including application context, layout code, stylesheet and integrator references, stylistic properties, and the standard WHO audit columns.
  • BNE_LAYOUTS_TL — the translation ("TL") table holding the language-dependent LAYOUT_CODE-to-name mapping, one row per installed language.

The view text confirms the join predicate: BNE_LAYOUTS_B.APPLICATION_ID = BNE_LAYOUTS_TL.APPLICATION_ID AND BNE_LAYOUTS_B.LAYOUT_CODE = BNE_LAYOUTS_TL.LAYOUT_CODE, restricted by BNE_LAYOUTS_TL.LANGUAGE = USERENV('LANG'). The composite key of APPLICATION_ID and LAYOUT_CODE therefore uniquely identifies a layout, and the USERENV('LANG') filter ensures each query returns exactly one translated row per layout — that of the user's current language setting. The view is a straightforward outer join of the two tables with no aggregation or filtering beyond the language predicate.

Key Columns

The view exposes the following columns, whose semantics are as follows:

Note that APPLICATION_ID and LAYOUT_CODE are repeated in the join, but because the "_VL" view projects only the base table's copy, each layout row carries a single authoritative set of key values.

Common Use Cases and Queries

BNE_LAYOUTS_VL is the preferred entry point for any inquiry that needs the layout's translated name together with its configuration. Typical scenarios include diagnosing which layout is attached to a given integrator, auditing stylesheet or reporting-interface assignments, and building custom reports over Web ADI setup metadata. A standard query pattern is:

  • List all layouts for an application, by name: SELECT layout_code, user_name, integrator_code, stylesheet_code FROM bne_layouts_vl WHERE application_id = :app_id ORDER BY user_name;
  • Find layouts associated with a specific integrator: SELECT layout_code, user_name FROM bne_layouts_vl WHERE integrator_app_id = :app_id AND integrator_code = 'MY_INTEGRATOR';
  • Identify reporting-enabled layouts: SELECT layout_code, user_name, reporting_interface_code FROM bne_layouts_vl WHERE reporting_flag = 'Y';
  • Audit recently modified layouts: SELECT layout_code, user_name, last_updated_by, last_update_date FROM bne_layouts_vl WHERE last_update_date > SYSDATE - 30 ORDER BY last_update_date DESC;

Because the language predicate is embedded in the view, query results automatically reflect the session language, and no additional LANGUAGE filter is required. To inspect alternate translations, the base translation table BNE_LAYOUTS_TL must be queried directly. As the object is a view, no ETRM setup or concurrent program is required to use it; it can be queried from any reporting tool with APPS schema access or via a suitable synonym grant.