Results for “bne_layout_blocks_b_uk1”

12 results




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

Overview

BNE.BNE_LAYOUT_BLOCKS_B is a core configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the BNE schema and registered in FND Design Data as BNE.BNE_LAYOUT_BLOCKS_B. It defines the logical grouping of columns held in BNE_INTERFACE_COLS within a given layout. Each block may have a parent block, may be oriented in different ways, and may be assigned a block size expressed as the number of rows to display. A block may additionally carry style definitions used for formatting at the block, row, column, prompt, hint, title, and summary levels.

The table resides in tablespace APPS_TS_TX_DATA with PCT Free 10, while its unique index is held in APPS_TS_TX_IDX. The primary key is BNE_LAYOUT_BLOCKS_B_PK, defined on (APPLICATION_ID, LAYOUT_CODE, BLOCK_ID). From a heuristic Data Vault modeling perspective, the table can be considered satellite-leaning, since it stores descriptive and formatting attributes keyed to a layout entity and carries a recursive parent reference rather than acting as a pure association hub.

Key Information Stored

The surrogate primary key is the composite of APPLICATION_ID, LAYOUT_CODE, and BLOCK_ID. A separate unique index, BNE_LAYOUT_BLOCKS_B_UK1 on (APPLICATION_ID, LAYOUT_CODE, BLOCK_ID, ZD_EDITION_NAME), functions as the business-key candidate and accommodates the ZD_EDITION_NAME column. The 38 documented columns include the following most significant items:

Common Use Cases and Queries

Typical usage centers on interrogating layout configuration for a given application, tracing parent-child block hierarchies, and reporting on style assignments. A basic lookup of all blocks for a layout can be written as:

  • SELECT BLOCK_ID, PARENT_ID, LAYOUT_ELEMENT, ORIENTATION, BLOCKSIZE FROM BNE_LAYOUT_BLOCKS_B WHERE APPLICATION_ID = :app_id AND LAYOUT_CODE = :layout_code ORDER BY SEQUENCE_NUM;
  • Recursive queries using CONNECT BY PRIOR BLOCK_ID = PARENT_ID allow reconstruction of nested block trees.
  • Reporting on display flags (DISPLAY_FLAG, PROMPT_DISPLAYED_FLAG, HINT_DISPLAYED_FLAG) supports auditing of what end users actually see.
  • The ZD_EDITION_NAME column supports editioning-aware queries in 12.2.x deployments.

Related Objects

The table participates in several referential relationships within the BNE schema:

  • BNE_LAYOUTS_B — referenced through APPLICATION_ID; provides the parent layout definition.
  • BNE_LAYOUT_BLOCKS_B (self-referencing) — PARENT_ID and APPLICATION_ID establish the recursive hierarchy of nested blocks.
  • BNE_LAYOUT_COLS — references this table through APPLICATION_ID, mapping interface columns into their owning blocks.

Together these objects form the metadata layer that drives the rendering of BNE interface layouts in Oracle EBS releases 12.1.1 and 12.2.2.