Results for “bne_layout_blocks_b”

50+ results




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

Overview

BNE_LAYOUT_BLOCKS_B is a table in the BNE schema (Web Applications Desktop Integrator, commonly branded as Oracle Web ADI) that stores the definition of sub-levels, or blocks, within a layout. In Oracle EBS 12.1.1 and 12.2.2, Web ADI layouts define the visual and structural arrangement of spreadsheet-based integrators used for data entry, upload, and download. Each layout is composed of one or more blocks, and each block may nest beneath a parent block, producing a hierarchical structure. This table is the repository for that hierarchy, together with the presentation attributes that govern how each block is rendered in the generated Microsoft Excel workbook. The table is a core configuration object: without rows in BNE_LAYOUT_BLOCKS_B, a layout has no content regions, and the Web ADI integrator cannot generate usable placeholders for columns, prompts, or hints.

The ETRM metadata classifies this object heuristically as satellite-leaning. In Data Vault modeling terms, this suggests BNE_LAYOUT_BLOCKS_B functions primarily as a descriptive satellite, carrying the mutable attributes (styles, orientation, display flags, and size limits) that surround a more stable business key. The self-referencing parent relationship reinforces the hierarchical, non-hub nature of the object.

Key Information Stored

The primary key BNE_LAYOUT_BLOCKS_B_PK is composed of APPLICATION_ID, LAYOUT_CODE, and BLOCK_ID. A unique index, BNE_LAYOUT_BLOCKS_B_UK1, extends this with ZD_EDITION_NAME, reflecting the 12.2.2 editioning mechanism. The most operationally significant columns include:

Common Use Cases and Queries

Developers and administrators query this table to understand layout composition, diagnose spreadsheet rendering problems, and trace parent-child block hierarchies. Typical patterns include retrieving all top-level blocks for a layout, or walking the recursion via PARENT_ID.

  • List blocks for a layout: SELECT BLOCK_ID, PARENT_ID, SEQUENCE_NUM, DISPLAY_FLAG FROM BNE_LAYOUT_BLOCKS_B WHERE APPLICATION_ID = :app AND LAYOUT_CODE = :code ORDER BY SEQUENCE_NUM;
  • Find nested children: SELECT * FROM BNE_LAYOUT_BLOCKS_B WHERE APPLICATION_ID = :app AND LAYOUT_CODE = :code AND PARENT_ID = :block;
  • Identify hidden blocks: SELECT BLOCK_ID FROM BNE_LAYOUT_BLOCKS_B WHERE DISPLAY_FLAG = 'N';
  • Join to columns via the documented FK from BNE_LAYOUT_COLS (APPLICATION_ID, LAYOUT_CODE, BLOCK_ID) to report the columns rendered in each block.
  • Style auditing to detect blocks missing presentation classes before publishing a layout.

Related Objects

The following objects are the most significant dependencies based on documented foreign-key relationships:

  • BNE_LAYOUTS_B – parent layout definition; joined on APPLICATION_ID and LAYOUT_CODE.
  • BNE_LAYOUT_BLOCKS_B (self-reference) – joined on APPLICATION_ID, LAYOUT_CODE, and PARENT_ID to traverse block hierarchies.
  • BNE_LAYOUT_COLS – column definitions; joined on APPLICATION_ID, LAYOUT_CODE, and BLOCK_ID.

Together these tables form the layout definition model used by Web ADI to generate spreadsheet integrators.