Search Results bne_layouts_b




Overview
Explore in AI Chat

Overview

BNE_LAYOUTS_B is a core configuration table in the Oracle E-Business Suite (EBS) Web Applications Desktop Integrator (BNE) module, present in releases 12.1.1 and 12.2.2. The table stores the definition of an instance of the display of an Integrator — in practical terms, it defines how a specific Integrator interface is rendered for a user, including its visual styling, reporting behaviour, and the associated WebADI document generation configuration. Each row represents a named "layout" that binds an Integrator, an optional reporting interface, a stylesheet, and a document list into a single displayable unit.

From a data-modelling perspective, the metadata classifies BNE_LAYOUTS_B as satellite-leaning. This is a heuristic suggestion rather than a formal Data Vault designation. The satellite-leaning classification is consistent with the table's structure: it carries descriptive and configuration attributes (style, flags, image references) that vary per layout, while its foreign keys point outward to the principal Integrator, Interface, and Layout Block entities that constitute the surrounding hub-and-link structure.

Key Information Stored

The table is uniquely identified by a composite primary key, BNE_LAYOUTS_B_PK, defined over (LAYOUT_CODE, APPLICATION_ID). LAYOUT_CODE is the business identifier of the layout, and APPLICATION_ID anchors it to the owning Oracle application. A secondary unique index, BNE_LAYOUTS_B_UK1, exists over (APPLICATION_ID, LAYOUT_CODE, ZD_EDITION_NAME); ZD_EDITION_NAME supports edition-based redefinition in 12.2.2, so the same logical layout can exist across multiple editions without collision.

The most significant columns include:

Common Use Cases and Queries

Typical usage centres on resolving which display layout applies to a given Integrator, and on tracing the stylesheet, reporting interface, and document list bound to that layout. A common query pattern joins the layout to its Integrator and Interface definitions:

  • List layouts for an Integrator: SELECT l.layout_code, l.stylesheet_code, l.reporting_interface_code FROM bne_layouts_b l WHERE l.integrator_code = :integrator_code AND l.application_id = :app_id;
  • Find the document list and image used by a layout: SELECT create_doc_list_code, image_file_name FROM bne_layouts_b WHERE layout_code = :code AND application_id = :app_id;
  • Join layouts to their constituent blocks via BNE_LAYOUT_BLOCKS_B to enumerate the display structure.

Reporting use cases include auditing which layouts reference a shared stylesheet, identifying layouts with reporting enabled (REPORTING_FLAG), and reconciling layout definitions across editions using ZD_EDITION_NAME.

Related Objects

The following objects are most significant to BNE_LAYOUTS_B, based on the documented foreign-key relationships:

  • BNE_INTEGRATORS_B — referenced via INTEGRATOR_APP_ID and INTEGRATOR_CODE; defines the Integrator the layout belongs to.
  • BNE_INTERFACES_B — referenced via REPORTING_INTERFACE_APP_ID and REPORTING_INTERFACE_CODE; supplies the reporting interface.
  • BNE_LAYOUT_BLOCKS_B — references BNE_LAYOUTS_B through (APPLICATION_ID, LAYOUT_CODE); holds the individual display blocks that make up a layout.
  • Stylesheet and document list definitions — referenced through STYLESHEET_CODE/STYLESHEET_APP_ID and CREATE_DOC_LIST_CODE/CREATE_DOC_LIST_APP_ID.

Together these relationships place BNE_LAYOUTS_B at the centre of WebADI layout configuration, binding Integrators, interfaces, blocks, stylesheets, and document lists into a coherent display definition.