Search Results bne_layout_cols_pk




Overview

BNE_LAYOUT_COLS is a table in the BNE schema (BNE — Web Applications Desktop Integrator) that stores the definition of individual columns within a Layout Block. In Oracle EBS 12.1.1 and 12.2.2, this object is central to the Web ADI (Web Applications Desktop Integulator) framework, which allows users to design spreadsheet-based layouts that map to Oracle EBS interfaces for data entry and upload. Each row in BNE_LAYOUT_COLS represents a single column that appears inside a layout block, capturing its display properties, sequencing, and the interface column it is bound to.

From a Data Vault modeling perspective, the FK structure mined from the metadata suggests classifying BNE_LAYOUT_COLS as a link table. It sits between BNE_LAYOUT_BLOCKS_B (the block definition) and BNE_INTERFACE_COLS_B (the underlying interface column definition), associating block-level layout structure with interface-level column metadata. This link classification is a heuristic modeling suggestion, not a formal Oracle designation.

Key Information Stored

The primary key, BNE_LAYOUT_COLS_PK, is a composite surrogate key comprising APPLICATION_ID, BLOCK_ID, LAYOUT_CODE, and SEQUENCE_NUM. A business-key unique index, BNE_LAYOUT_COLS_UK1, extends this with ZD_EDITION_NAME, supporting the editioning and multi-tenant characteristics introduced in EBS 12.2.2.

Common Use Cases and Queries

Typical scenarios involve inspecting or troubleshooting Web ADI layout definitions, validating which interface columns a layout exposes, and reporting on layout structure for governance. A frequent query retrieves all columns for a given block:

SELECT lc.SEQUENCE_NUM, lc.INTERFACE_CODE, lc.DISPLAY_WIDTH, lc.READ_ONLY_FLAG
FROM BNE_LAYOUT_COLS lc
WHERE lc.APPLICATION_ID = :app_id
AND lc.BLOCK_ID = :block_id
AND lc.LAYOUT_CODE = :layout_code
ORDER BY lc.SEQUENCE_NUM;

Investigators also join to BNE_INTERFACE_COLS_B to confirm the target interface mapping, and to BNE_LAYOUT_BLOCKS_B to enumerate blocks per layout. Reporting use cases include export of layout-to-interface mappings for migration, auditing read-only or defaulted columns, and diagnosing mismatches that cause upload failures.

Related Objects

  • BNE_LAYOUT_BLOCKS_B — Parent table; joined on APPLICATION_ID, BLOCK_ID, LAYOUT_CODE.
  • BNE_INTERFACE_COLS_B — Referenced interface column definition; joined on INTERFACE_APP_ID, INTERFACE_CODE, INTERFACE_SEQ_NUM.
  • BNE_LAYOUTS_B — Defines the layout header owning the layout code.
  • BNE_INTERFACES_B — Defines the interface to which columns ultimately map.
  • BNE_LAYOUT_COLS_PK / BNE_LAYOUT_COLS_UK1 — Primary and unique indexes enforcing integrity.