Search Results bne_mappings_tl_pk

Overview

BNE_MAPPINGS_TL is the translation table for BNE_MAPPINGS_B, the base table that stores mapping definitions used by Oracle Web Applications Desktop Integrator (BNE). In Oracle EBS 12.1.1 and 12.2.2 the BNE product governs the integration of desktop tools such as Microsoft Excel and Word with E-Business Suite forms, and mappings define how desktop worksheet columns, parameters, and content are linked to underlying application data. Because BNE is a multi-language product, user-facing text associated with a mapping — such as mapping names and descriptions — is held in the _TL table and resolved at runtime according to the session language.

BNE_MAPPINGS_TL is owned by the BNE schema in both 12.1.1 and 12.2.2. The ETRM documentation classifies the object as standalone through heuristic Data Vault analysis of its foreign key structure; from a modeling perspective, it is most naturally treated as a satellite table. It carries the descriptive, language-dependent attributes of the BNE_MAPPINGS_B hub, joined on the shared application and mapping business keys plus the language discriminator.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• APPLICATION_ID — identifies the owning EBS application; part of both the primary key and all unique keys.
• MAPPING_CODE — the business identifier of the mapping; combined with APPLICATION_ID it links each translation row to its parent row in BNE_MAPPINGS_B.
• LANGUAGE — the NLS language code for the translated content, typically sourced from FND_LANGUAGES.
• SOURCE_LANG — indicates the language of the source text from which the translation was derived.
• ZD_EDITION_NAME — the editioning column introduced by the EBS 12.2 online patching architecture. In 12.1.1 this column is absent or unused; in 12.2.2 it participates in the unique index BNE_MAPPINGS_TL_UK1 and is essential to Edition-Based Redefinition queries.
• USER_NAME — the application user attributed to the translation row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS WHO columns that record audit and concurrency information for each translation record.

The surrogate primary key is BNE_MAPPINGS_TL_PK, defined on (APPLICATION_ID, MAPPING_CODE, LANGUAGE). A separate unique index, BNE_MAPPINGS_TL_UK1, extends that key with ZD_EDITION_NAME, and in 12.2.2 it is this four-column combination that enforces business uniqueness across editions.

Common Use Cases and Queries

Typical queries retrieve the translated text for one or more mappings for a given language, or join the translation table to its base table to produce a bilingual report.

SELECT b.mapping_code, t.user_name
FROM   bne.bne_mappings_b b,
       bne.bne_mappings_tl t
WHERE  b.application_id = t.application_id
AND    b.mapping_code   = t.mapping_code
AND    t.language       = USERENV('LANG');

In 12.2.2 environments, queries against _TL and _B tables should filter or exclude editioned rows by referencing ZD_EDITION_NAME (or by using the standard editioning views) to avoid returning stale rows from prior editions. Reporting use cases include auditing which mappings lack translations for active languages, reconciling SOURCE_LANG against the installed language set, and migrating translation content between environments using FNDLOAD or the XLIFF translation utilities.

Related Objects

• BNE_MAPPINGS_B — the base table; joined on APPLICATION_ID and MAPPING_CODE.
• BNE_MAPPING_SETS — groups mappings for deployment; references MAPPING_CODE.
• BNE_PARAMETERS — defines parameters that reference a mapping.
• BNE_INTERFACE_TABLES — interface definitions that consume mapping metadata.
• FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG values.
• FND_APPLICATION — resolves APPLICATION_ID to an application short name.
• FND_LOOKUPS — provides related lookup values used by mapping definitions.