Search Results layout_code




Overview
Explore in AI Chat

Overview

BNE_LAYOUTS_TL is the translation table for BNE_LAYOUTS_B within the BNE (Web Applications Desktop Integrator) product in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific, user-facing text associated with Web ADI layout definitions, allowing the same underlying layout object to be rendered in multiple installed languages. Each row represents one language translation of a layout identified in the base table by APPLICATION_ID and LAYOUT_CODE.

The table resides in the BNE schema and is classified as VALID in the ETRM object registry, with an 11-column physical schema documented for release 12.2.2. From a Data Vault modeling perspective, the metadata heuristic classifies BNE_LAYOUTS_TL as a standalone object, meaning it exhibits no mined foreign key relationships. In practice, however, it functions as a descriptive satellite of the base layout hub, carrying translatable attributes keyed by the parent layout identifier plus LANGUAGE.

Key Information Stored

The table's primary key is enforced through BNE_LAYOUTS_TL_PK on the composite of APPLICATION_ID, LAYOUT_CODE, and LANGUAGE. A secondary unique index, BNE_LAYOUTS_TL_UK1, extends the business key with ZD_EDITION_NAME (APPLICATION_ID, LAYOUT_CODE, LANGUAGE, ZD_EDITION_NAME), indicating edition-aware uniqueness for the layout translation.

  • APPLICATION_ID — identifies the owning application, part of both the primary key and the unique business key.
  • LAYOUT_CODE — the layout identifier; the primary business attribute searched by users.
  • LANGUAGE — the language code of the translation row; completes the translation key.
  • SOURCE_LANG — the source language from which the translation originated, used for translation tracking.
  • USER_NAME — the user associated with the translation record.
  • CREATED_BY, CREATION_DATE — standard audit columns capturing row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the last modification.
  • ZD_EDITION_NAME — editioning attribute supporting EBS 12.2 online patching and edition-based redefinition.

Common Use Cases and Queries

The most frequent access pattern is resolving a layout by its code for a given language, typically to display or export layout metadata in reports and Desktop Integrator integrations. A representative query joins the translation table to the base table:

  • SELECT b.layout_code, t.language FROM bne.bne_layouts_b b, bne.bne_layouts_tl t WHERE b.application_id = t.application_id AND b.layout_code = t.layout_code AND t.language = USERENV('LANG');
  • Reporting on translation completeness by comparing languages present per layout_code.
  • Auditing translation changes using LAST_UPDATED_BY and LAST_UPDATE_DATE for compliance and change-tracking.
  • Extracting multilingual layout descriptions for data migration or interface configuration.

Related Objects

Because the mined relationship classification is standalone, the following associations are drawn from the documented key structure and BNE product context rather than enforced foreign keys:

  • BNE_LAYOUTS_B — the base layout table; joined on APPLICATION_ID and LAYOUT_CODE.
  • BNE_LAYOUTS_TL_PK — the primary key constraint spanning APPLICATION_ID, LAYOUT_CODE, and LANGUAGE.
  • BNE_LAYOUTS_TL_UK1 — the unique business-key index adding ZD_EDITION_NAME.
  • BNE_LAYOUT_FIELDS / BNE layout component tables — layout field definitions that reference the same layout_code.
  • FND_APPLICATION — resolves APPLICATION_ID to an application name.
  • FND_LANGUAGES — resolves LANGUAGE to an installed language description.