Search Results content_code




Overview
Explore in AI Chat

Overview

BNE_CONTENTS_TL is the translation (TL) table for the base table BNE_CONTENTS_B within the BNE schema, which underpins Oracle Web Applications Desktop Integrator. Its role in Oracle EBS 12.1.1 and 12.2.2 is to store language-specific, translatable attributes for each content definition row, enabling multilanguage support across integrated desktop tools such as Web ADI, spreadsheet integration, and the underlying content framework. In a multilingual EBS instance, the base table BNE_CONTENTS_B stores language-independent data while BNE_CONTENTS_TL holds the user-facing translated text keyed by language.

Applying a heuristic Data Vault classification, BNE_CONTENTS_TL is best modeled as a satellite: it depends on a parent business key (APPLICATION_ID, CONTENT_CODE) and carries descriptive, language-scoped attributes plus standard audit columns. The metadata classifies this object as "standalone" with no dependent child objects, consistent with a leaf-level descriptive satellite rather than a hub or link.

Key Information Stored

The table is keyed by a composite primary key constraint, BNE_CONTENTS_TL_PK, over APPLICATION_ID, CONTENT_CODE, and LANGUAGE. A second unique index, BNE_CONTENT_TL_UK1, extends this business key with ZD_EDITION_NAME (APPLICATION_ID, CONTENT_CODE, LANGUAGE, ZD_EDITION_NAME), reflecting the multitenant/editioning-aware uniqueness used in 12.2.x.

  • APPLICATION_ID — identifies the owning EBS application; part of both the primary key and the unique business key.
  • CONTENT_CODE — the business identifier for the content definition; the column most frequently searched, used to locate specific content records.
  • LANGUAGE — the language code of the translated row; completes the composite key.
  • SOURCE_LANG — the language from which the row was translated, supporting the standard EBS translation model.
  • ZD_EDITION_NAME — editioning column enabling Online Patching edition-based redefinition in 12.2.x; part of BNE_CONTENT_TL_UK1.
  • USER_NAME — the descriptive, translatable attribute associated with the content entry.
  • CREATED_BY / CREATION_DATE — standard who columns recording row creation.
  • LAST_UPDATED_BY / LAST_UPDATE_DATE — standard who columns recording the last modification.
  • LAST_UPDATE_LOGIN — the login ID under which the change was made, for audit traceability.

Common Use Cases and Queries

Typical usage centers on resolving translated content names for a given content code and language, and on auditing translation coverage.

  • Retrieve translated content for a specific code and language:

SELECT content_code, language, user_name FROM bne.bne_contents_tl WHERE application_id = :app_id AND content_code = :code AND language = USERENV('LANG');

  • List all languages available for a given content record.
  • Join to BNE_CONTENTS_B to report base attributes alongside translations.
  • Reconcile rows where LANGUAGE = SOURCE_LANG to identify untranslated source entries.
  • Audit LAST_UPDATE_DATE and LAST_UPDATED_BY for translation change tracking.

Because CONTENT_CODE is a business key shared with the base table, filtering by it is the most efficient access path when combined with APPLICATION_ID and LANGUAGE.

Related Objects

The table participates in the BNE content framework and is primarily related to its base object and translation infrastructure.

  • BNE_CONTENTS_B — the base table; join on APPLICATION_ID and CONTENT_CODE to combine translatable and non-translatable attributes.
  • BNE_CONTENTS_TL_PK — primary key constraint defining row uniqueness.
  • BNE_CONTENT_TL_UK1 — unique index providing the edition-aware business-key candidate.
  • FND_APPLICATION / FND_APPLICATION_TL — resolve APPLICATION_ID to application names.
  • FND_LANGUAGES / FND_LANGUAGES_TL — resolve LANGUAGE codes to installed language names.
  • FND_USER — resolve CREATED_BY and LAST_UPDATED_BY to user accounts for audit reporting.