Search Results bne_layouts_b_uk1

Overview

BNE.BNE_LAYOUTS_B is a core configuration table in the Oracle E-Business Suite ETRM (Enterprise Transaction Reporting Model) schema, owned by the BNE product. It stores the definition of a layout — a hierarchical structure composed of BNE_INTERFACE_COL columns that governs how a viewer renders interface data in a meaningful, business-friendly format. In Oracle EBS 12.1.1 and 12.2.2, layouts are the presentation layer metadata that binds an interface definition to a specific visual arrangement, including styling rules, integrator context, and reporting-versus-data-entry behavior. A layout therefore acts as the join between raw interfaced data and the user-facing report or form.

From a dimensional modeling perspective, the heuristic Data Vault classification for this table is satellite-leaning. It holds descriptive, versionable attributes (style, reporting flags, image references) attached to a stable business key, rather than acting as a pure hub or link. Modelers should treat the composite (APPLICATION_ID, LAYOUT_CODE) as the enduring business key, with the remaining descriptive columns as satellite attributes.

Key Information Stored

The primary key is documented as BNE_LAYOUTS_B_PK, defined on (LAYOUT_CODE, APPLICATION_ID). A parallel unique index, BNE_LAYOUTS_B_UK1 — the object the user searched for — is defined on (APPLICATION_ID, LAYOUT_CODE, ZD_EDITION_NAME) in APPS_TS_TX_IDX, extending the business key with the edition column used for EBS 12.2.2 online patching / editioning support. The most significant columns are:

• APPLICATION_ID — foreign key to FND_APPLICATIONS.APPLICATION_ID, scoping the layout to an application.
• LAYOUT_CODE — unique code identifying the entity for the given application.
• OBJECT_VERSION_NUMBER — standard optimistic-locking version column.
• STYLESHEET_APP_ID / STYLESHEET_CODE — the default stylesheet applied to the layout.
• INTEGRATOR_APP_ID / INTEGRATOR_CODE — the integrator the interface belongs to (join to BNE_INTEGRATORS_B); indexed by BNE_LAYOUTS_B_N1.
• STYLE / STYLE_CLASS — free-form style override text and style class name.
• REPORTING_FLAG — 'Y' for reporting layouts, 'N' for data-entry layouts.
• REPORTING_INTERFACE_APP_ID / REPORTING_INTERFACE_CODE — the reporting interface when REPORTING_FLAG = 'Y'.
• CREATE_DOC_LIST_APP_ID / CREATE_DOC_LIST_CODE — document-list configuration (indexed by BNE_LAYOUTS_B_N2).
• IMAGE_FILE_NAME — associated image asset.
• ZD_EDITION_NAME — editioning column supporting 12.2 online patching.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on resolving a layout to its interface and integrator context for reporting and troubleshooting. A common query identifies all reporting layouts for a given integrator:

• Select layouts by integrator: SELECT l.layout_code, l.reporting_flag, l.stylesheet_code FROM bne_layouts_b l WHERE l.integrator_app_id = :app_id AND l.integrator_code = :intg_code;
• List reporting layouts and their reporting interfaces: SELECT layout_code, reporting_interface_code FROM bne_layouts_b WHERE reporting_flag = 'Y' AND application_id = :app_id;
• Resolve style configuration: select STYLE, STYLE_CLASS for a layout to inspect presentation overrides.

Reporting use cases include auditing which layouts exist per application, tracing a displayed report back to its layout definition, and validating that reporting layouts correctly reference a reporting interface.

Related Objects

The following objects are most significant to BNE_LAYOUTS_B based on documented FK relationships:

• BNE.BNE_INTERFACES_B — referenced via REPORTING_INTERFACE_APP_ID / REPORTING_INTERFACE_CODE for reporting layouts.
• BNE.BNE_INTEGRATORS_B — referenced via INTEGRATOR_APP_ID / INTEGRATOR_CODE.
• BNE.BNE_LAYOUT_BLOCKS_B — references this table via APPLICATION_ID, defining the blocks that make up a layout's hierarchy.
• BNE.BNE_INTERFACE_COL — defines the interface columns composing the layout structure.
• FND_APPLICATIONS — source of APPLICATION_ID values.
• BNE_LAYOUTS_TL — the translated (TL) companion holding language-specific text, joined by LAYOUT_CODE and APPLICATION_ID.