Search Results viewer_code




Overview
Explore in AI Chat

Overview

BNE_VIEWERS_TL is the translation (language-specific) table for BNE_VIEWERS_B, the base table that stores viewer definitions used by Oracle Web Applications Desktop Integrator (BNE) within Oracle E-Business Suite 12.1.1 and 12.2.2. In the EBS architecture, the "_TL" suffix denotes a table holding translatable descriptive columns keyed by LANGUAGE, while the companion "_B" table holds language-independent attributes. Together these tables implement Oracle's multi-language Applications Technology (MLS) pattern, allowing viewer names and related descriptive text to be presented in each installed language without duplicating the underlying configuration.

BNE_VIEWERS defines the desktop integration viewers available to users when they open or publish Web ADI documents to spreadsheet applications. The translation table therefore plays a supporting but essential role in localization: it ensures the viewer label and associated text appear in the session language of the user.

From a heuristic Data Vault modeling perspective — derived from the observed foreign key structure rather than an Oracle-declared classification — this object is classified as standalone: the mined relationship data shows no dependent hub or link references to other tables. In Data Vault terms it functions most naturally as a satellite attached to the BNE_VIEWERS_B hub, since it carries descriptive, language-qualified attributes rather than relationships between distinct business entities. This classification is a modeling suggestion and should not be treated as an Oracle-documented designation.

Key Information Stored

The documented physical schema for BNE_VIEWERS_TL comprises 11 columns. The columns most significant for querying and integration are:

  • APPLICATION_ID — Identifies the Oracle application (product) that owns the viewer definition; part of the composite business key.
  • VIEWER_CODE — The developer-facing viewer identifier; part of the composite business key and the principal join to the base table.
  • LANGUAGE — The language code for the translated row, expressed in Oracle's NLS language format; part of the composite business key.
  • ZD_EDITION_NAME — The editioning column introduced with EBS 12.2 online patching; included in the unique index to keep edition-scoped rows distinct.
  • USER_NAME — The translated, user-facing viewer name displayed in Desktop Integrator; the principal translatable attribute.
  • SOURCE_LANG — The language from which the row was originally created or seeded, used by MLS tooling to track translation provenance.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard EBS audit columns recording who created and last modified the row and when.

The surrogate primary key is BNE_VIEWERS_TL_PK, defined on (APPLICATION_ID, VIEWER_CODE, LANGUAGE). Two business-key candidates are documented: the primary key itself and the unique index BNE_VIEWERS_TL_UK1, defined on (APPLICATION_ID, VIEWER_CODE, LANGUAGE, ZD_EDITION_NAME). The inclusion of ZD_EDITION_NAME in the unique index reflects the 12.2 editioning model, under which the same logical translation may exist in multiple editions.

Common Use Cases and Queries

The principal use case is resolving the display name of a viewer for a given language, either for reporting or as a validation check on seeded translations. A typical query joins the translation table to the base table and filters by language:

SELECT b.viewer_code, t.user_name
FROM bne.bne_viewers_b b, bne.bne_viewers_tl t
WHERE b.application_id = t.application_id
AND b.viewer_code = t.viewer_code
AND t.language = USERENV('LANG');

Administrators responsible for localization frequently audit for missing or untranslated viewers by outer-joining the base table to the translation table and filtering on a null USER_NAME. Reporting teams building Web ADI inventory reports use the translation table to present viewer names in the reporting language rather than in the base-table developer identifiers. During patching and upgrades, queries restricted to a specific ZD_EDITION_NAME confirm that translation rows have been correctly copied into the run edition.

Related Objects

The following objects are most significant in relation to BNE_VIEWERS_TL:

  • BNE_VIEWERS_B — The base table holding language-independent viewer attributes; joined on APPLICATION_ID and VIEWER_CODE.
  • BNE_VIEWERS_VL — The MLS view that presents base and translated columns together for a given language.
  • BNE_VIEWERS_TL_PK — The composite primary key constraint on (APPLICATION_ID, VIEWER_CODE, LANGUAGE).
  • BNE_VIEWERS_TL_UK1 — The unique index on (APPLICATION_ID, VIEWER_CODE, LANGUAGE, ZD_EDITION_NAME) supporting 12.2 editioning.
  • FND_LANGUAGES — The language reference table, joined on LANGUAGE to validate installed languages and derive localized names.
  • FND_APPLICATION — Supplies the application short name for the APPLICATION_ID values stored in this table.

Because the ETRM metadata classifies this object as standalone with no dependent foreign keys, no additional link tables or dependent satellites are documented.