Search Results bne_layout_cols_v




Overview
Explore in AI Chat

Overview

BNE_LAYOUT_COLS_V is a business view owned by the APPS schema in Oracle E-Business Suite, defined within the BNE product module (Web Applications Desktop Integrator, sometimes referred to as Web ADI). It presents a consolidated, already-filtered representation of the interface columns that make up a Web ADI layout. The view joins the layout definition metadata against the interface column definitions, resolving for each layout the columns that a user will actually see and manipulate during an upload, download, or desktop integration session.

Because desktop integration depends on precise column-level control — prompts, validation rules, default values, display widths, and edit behavior — the view serves as the authoritative reference for tools, reports, and customizations that need to introspect how a given interface layout is constructed. Users searching for "edit_type" will find that column exposed directly by this view; it is inherited from the interface column definition and governs how an end user is permitted to interact with the column value.

Underlying Base Objects

The documented view metadata lists two referenced base objects: BNE_INTERFACE_COLS_VL (a view) and BNE_LAYOUT_COLS (a synonym). The documented view SQL joins these as BNE_LAYOUT_COLS L and BNE_INTERFACE_COLS_VL I on three keys — INTERFACE_APP_ID = APPLICATION_ID, INTERFACE_CODE, and INTERFACE_SEQ_NUM = SEQUENCE_NUM — and restricts the result set with I.DISPLAY_FLAG = 'Y'. This means the view returns only those interface columns that are flagged for display, effectively hiding layout-irrelevant columns from downstream consumers.

BNE_INTERFACE_COLS_VL is the translatable (VL) view over the interface column definitions, which is why prompt and hint text returned by BNE_LAYOUT_COLS_V can reflect language-specific values. BNE_LAYOUT_COLS carries the layout-specific overrides — styling, ordering, and optional attribute-level substitutions. The view resolves these two layers using DECODE and NVL expressions so that a layout value takes precedence when present, otherwise the interface default is used.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which columns appear in a layout, reviewing validation and edit behavior, troubleshooting default values or prompts, and building custom reports describing interface configuration. A representative query listing visible columns and their edit and read-only behavior follows:

  • SELECT layout_code, block_id, interface_col_name, edit_type, read_only_flag, required_flag, display_width FROM bne_layout_cols_v WHERE interface_code = :code AND layout_code = :layout ORDER BY block_id, sequence_num;
  • SELECT interface_col_name, val_type, lov_type, default_type, default_value FROM bne_layout_cols_v WHERE edit_type = :edit_type;

The first query drives layout inspection and column ordering; the second filters columns by a specific edit behavior — the exact scenario that motivated the search for "edit_type". Because the view enforces DISPLAY_FLAG = 'Y', results reflect only user-visible columns, making it suitable for direct use in reporting and validation tooling without additional filtering.