Search Results bne_interfaces_tl




Overview
Explore in AI Chat

Overview

BNE_INTERFACES_TL is the translation (language-specific) table that accompanies BNE_INTERFACES_B in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It resides in the BNE schema, which supports the Web Applications Desktop Integrator (Web ADI) product family. Web ADI enables users to create, upload, and manage desktop-integrated spreadsheet interfaces that communicate with EBS forms and concurrent programs. BNE_INTERFACES_B holds the base-language definitions of these interfaces, while BNE_INTERFACES_TL stores the translated display names, descriptions, and user-facing text for each registered interface across the languages installed in the instance.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is standalone. This suggests it functions as an independent descriptive entity rather than a classic hub, link, or satellite. It carries its own composite business key and descriptive language attributes without documented foreign-key dependencies to external tables.

Key Information Stored

The table is keyed by a composite primary key named BNE_INTERFACES_TL_PK, defined over APPLICATION_ID, INTERFACE_CODE, and LANGUAGE. The documented columns and their roles are:

  • APPLICATION_ID — Identifies the owning EBS application; part of the primary key.
  • INTERFACE_CODE — The internal code uniquely identifying the Web ADI interface within the application; part of the primary key.
  • LANGUAGE — The language code for the translated row; part of the primary key.
  • SOURCE_LANG — The base language from which the translation was derived, used to track translation provenance.
  • USER_NAME — The translated, user-facing name of the interface presented in the desktop integrator UI.
  • ZD_EDITION_NAME — The editioning column supporting Online Patching in Release 12.2.x; appears in the unique index BNE_INTERFACES_TL_UK1 alongside APPLICATION_ID, INTERFACE_CODE, and LANGUAGE.

The remaining columns are standard WHO audit attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. The unique index BNE_INTERFACES_TL_UK1 is a business-key candidate, reinforcing that a given interface may have one translated row per language and edition.

Common Use Cases and Queries

Typical reporting and diagnostic queries join the translation table to its base table to retrieve user-friendly interface names. A common pattern retrieves all interfaces for a language:

  • SELECT b.application_id, b.interface_code, t.user_name FROM bne_interfaces_b b, bne_interfaces_tl t WHERE b.application_id = t.application_id AND b.interface_code = t.interface_code AND t.language = USERENV('LANG').
  • Auditing translation completeness by comparing counts between BNE_INTERFACES_B and BNE_INTERFACES_TL grouped by LANGUAGE.
  • Multilingual deployment validation in 12.2.x, filtering on ZD_EDITION_NAME to isolate the active edition.

Related Objects

The primary dependency is its base table, BNE_INTERFACES_B, joined on APPLICATION_ID and INTERFACE_CODE. Surrounding Web ADI objects that reference interface metadata include BNE_INTERFACE_PARAMETERS, BNE_INTERFACE_ATTRIBUTES, BNE_INTERFACE_GROUPS, and the Web ADI API packages (such as BNE_INTEGRATOR_UTIL) that resolve interface definitions at runtime. Because the table is standalone with no documented foreign keys, relationships to these objects are logical rather than enforced by database constraints.