Search Results bne_integrators_tl




Overview
Explore in AI Chat

Overview

BNE_INTEGRATORS_TL is the translation table for BNE_INTEGRATORS_B, the base table that defines integrators within Oracle Web Applications Desktop Integrator (BNE) in Oracle E-Business Suite 12.1.1 and 12.2.2. An integrator is a registered desktop integration definition that governs how a specific EBS business flow — such as a journal import, a budget upload, or a requisition load — is presented and processed through the desktop Excel interface. Because integrator definitions carry user-facing display text (upload headers and title bars), that text must be maintained in multiple languages, which is precisely the role of this table.

The table is owned by the BNE schema and is documented as VALID in ETRM. It follows the standard EBS translatable-table pattern: the base table holds language-independent attributes keyed by APPLICATION_ID and INTEGRATOR_CODE, while BNE_INTEGRATORS_TL holds the language-dependent attributes keyed additionally by LANGUAGE. In context of 12.1.1 and 12.2.2, the structure is identical, with the 12.2.2 schema documenting thirteen columns and an additional ZD_EDITION_NAME attribute associated with edition-based support.

The heuristic Data Vault classification mined from the FK structure is standalone. As a modeling suggestion, this treats BNE_INTEGRATORS_TL as an independent structure rather than a dependent hub, link, or satellite, which is consistent with the fact that no foreign key relationships were detected in the documented relationship data. Practically, however, the table behaves as a translation satellite of the BNE_INTEGRATORS_B hub, joined logically on APPLICATION_ID and INTEGRATOR_CODE.

Key Information Stored

The primary key, BNE_INTEGRATORS_TL_PK, is a composite surrogate key over APPLICATION_ID, INTEGRATOR_CODE, and LANGUAGE. The unique index BNE_INTEGRATORS_TL_UK1 extends this with ZD_EDITION_NAME, making it the strongest business-key candidate documented for the object.

  • APPLICATION_ID — identifies the owning EBS application; part of the primary key and the join to the base table.
  • INTEGRATOR_CODE — the internal integrator identifier; part of the primary key and the business join to BNE_INTEGRATORS_B.
  • LANGUAGE — the NLS language code for the translated row; part of the primary key.
  • SOURCE_LANG — the language from which the translation was derived, used by the translation tooling.
  • USER_NAME — the display name of the integrator presented to the end user in the selected language.
  • UPLOAD_HEADER — the translated header text shown on the desktop upload interface.
  • UPLOAD_TITLE_BAR — the translated title bar text for the integrator's upload page.
  • ZD_EDITION_NAME — edition name associated with the row; part of the unique business key and relevant to edition-aware access in 12.2.2.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — the standard EBS who-column audit set recording row creation and last modification.

Common Use Cases and Queries

The most frequent access pattern is retrieving translated display text for an integrator in a specific language. A typical query joins the translation table to its base table:

  • SELECT b.integrator_code, t.user_name, t.upload_header, t.upload_title_bar FROM bne.bne_integrators_b b, bne.bne_integrators_tl t WHERE b.application_id = t.application_id AND b.integrator_code = t.integrator_code AND t.language = USERENV('LANG');
  • Reporting on which integrators lack a translation for a given language, by comparing base rows to TL rows with an outer join and filtering on a NULL user_name.
  • Auditing translation maintenance activity by filtering on LAST_UPDATED_BY and LAST_UPDATE_DATE to track recent changes.
  • Verifying NLS completeness across languages, grouping by INTEGRATOR_CODE and counting distinct LANGUAGE values.

Because the table is queried by desktop integration runtime components, its contents directly affect the labels users see in the Excel-based upload experience, making translation completeness an operational concern.

Related Objects

The principal relationship is to the base table, joined on the shared key columns. The following are the most significant dependencies:

  • BNE_INTEGRATORS_B — the base table holding language-independent integrator attributes; joined on APPLICATION_ID and INTEGRATOR_CODE.
  • BNE_INTEGRATORS_TL_PK — the primary key constraint enforcing uniqueness of APPLICATION_ID, INTEGRATOR_CODE, and LANGUAGE.
  • BNE_INTEGRATORS_TL_UK1 — the unique index over APPLICATION_ID, INTEGRATOR_CODE, LANGUAGE, and ZD_EDITION_NAME.
  • BNE_INTEGRATORS_VL — the standard EBS translation view that presents base and translated columns as a single logical entity for the current session language.
  • Other BNE desktop integration definition tables (such as those defining integrator parameters and content) that reference integrators by the same APPLICATION_ID and INTEGRATOR_CODE business key.

Consumers should query through the VL view where one exists, rather than joining the base and translation tables directly, to ensure correct language resolution and consistency with EBS NLS conventions.