Results for “bne_layout_blocks_vl”

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

Overview

BNE_LAYOUT_BLOCKS_VL is a standard Oracle E-Business Suite translation (MLS) view owned by the APPS schema and defined over the BNE_LAYOUT_BLOCKS entity. It belongs to the BNE product family — Web Applications Desktop Integrator (Web ADI) — which governs the definition, presentation, and rendering of desktop-integrated spreadsheet layouts within EBS 12.1.1 and 12.2.2. The view presents a single logical row per layout block, merging the language-independent definition held in the base table with the language-dependent prompts held in the translation table.

Its principal role is to expose the fully resolved, user-language version of layout block metadata: layout identity, structural hierarchy, sequencing, styling, display behavior, and prompt text. Because layout blocks control how Web ADI and related integrator content is rendered, this view is the canonical reporting and integration surface for layout configuration. Reports, concurrent programs, personalizations, and BI Publisher data sources that need to inspect or validate layout blocks query the _VL view rather than the underlying tables, ensuring that translated prompt text is returned for the session language.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• BNE_LAYOUT_BLOCKS_B — the language-independent base table, aliased as H. It supplies all structural, control, and styling columns keyed by APPLICATION_ID, LAYOUT_CODE, and BLOCK_ID.
• BNE_LAYOUT_BLOCKS_TL — the language-dependent translation table, aliased as T. It supplies USER_NAME and PROMPT_ABOVE.

The join is performed on APPLICATION_ID, LAYOUT_CODE, and BLOCK_ID, with the translated row restricted by T.LANGUAGE = USERENV('LANG'). This is the standard MLS pattern: one physical row per block in the _B table, one row per installed language in the _TL table, and a _VL view that filters to the caller's language so consumers see exactly one row per block. The view also exposes H.ROWID as ROW_ID, preserving row identity for downstream processing, and carries the standard WHO audit columns.

Key Columns

• ROW_ID, APPLICATION_ID, LAYOUT_CODE, BLOCK_ID — the row identity and the composite key that uniquely identifies a layout block.
• PARENT_ID, SEQUENCE_NUM, LAYOUT_ELEMENT — the hierarchical position and structural role of the block within its layout.
• PROMPT_STYLE_CLASS, PROMPT_STYLE — the style class and inline style applied to the prompt rendered for the block. These are the columns most relevant to searches for "prompt_style_class" and govern prompt typography, spacing, and visual treatment in the rendered layout.
• PROMPT_DISPLAYED_FLAG, PROMPT_COLSPAN, PROMPT_ABOVE — whether the prompt is shown, how many columns it spans, and whether it is positioned above the associated field.
• STYLE_CLASS, ROW_STYLE_CLASS, COL_STYLE_CLASS, HINT_STYLE_CLASS, SUMMARY_STYLE_CLASS, TITLE_STYLE_CLASS — the parallel styling attributes for the element itself, its row, its column, its hint, its summary, and its title. Each has a matching *_STYLE column for inline CSS.
• HINT_DISPLAYED_FLAG, HINT_COLSPAN, ORIENTATION, LAYOUT_CONTROL, DISPLAY_FLAG, BLOCKSIZE, MINSIZE, MAXSIZE — display and sizing behavior.
• USER_NAME — the user-facing name of the block, sourced from the translation table.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — concurrency control and audit columns.

Common Use Cases and Queries

Typical uses include auditing prompt and styling configuration across layouts, diagnosing rendering discrepancies caused by missing or inconsistent style classes, and extracting layout metadata for documentation or migration. The following query lists prompt styling for all blocks of a given layout in the current session language:

SELECT layout_code, block_id, parent_id, sequence_num, layout_element, user_name, prompt_displayed_flag, prompt_style_class, prompt_style, prompt_colspan, prompt_above FROM apps.bne_layout_blocks_vl WHERE application_id = :app_id AND layout_code = :layout_code ORDER BY sequence_num, block_id;

To find blocks where no prompt style class has been assigned — a common cause of inconsistent Web ADI presentation — filter on the relevant column:

SELECT layout_code, block_id, user_name, layout_element FROM apps.bne_layout_blocks_vl WHERE prompt_displayed_flag = 'Y' AND prompt_style_class IS NULL ORDER BY layout_code, sequence_num;

A similar pattern retrieves every block sharing a particular style class for impact analysis before a CSS or branding change:

SELECT layout_code, block_id, user_name, prompt_style_class, style_class FROM apps.bne_layout_blocks_vl WHERE prompt_style_class = :style_class_name ORDER BY layout_code, block_id;

Because the view resolves language at query time via USERENV('LANG'), results reflect the language of the connected session; multilingual environments should confirm NLS settings before comparing extracted prompt text across users or instances.