Results for “bne_param_defns_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BNE_PARAM_DEFNS_TL is the translation (TL) table for BNE_PARAM_DEFNS_B, the base table that defines parameters for concurrent programs, request sets, and related executable components within the BNE – Web Applications Desktop Integrator product. In Oracle EBS 12.1.1 and 12.2.2, the BNE schema underpins the Web ADI framework, which allows users to create, upload, and download spreadsheet-based interfaces for Oracle applications. Parameter definitions describe the prompts, defaults, validation rules, and user tips associated with those parameters, and this TL table stores the language-specific, translated text for each definition.

Following Oracle's standard MLS (Multi-Lingual Support) architecture, the _B table holds language-independent attributes and a single row per entity, while the _TL table holds the translated prompt text, default descriptions, and user tips, keyed additionally by LANGUAGE. The ETRM metadata classifies this object heuristically as standalone in a Data Vault sense, meaning it has no foreign-key dependencies mined from its constraint structure. In Data Vault modeling terms, this is best treated as a satellite attached to the BNE_PARAM_DEFNS_B hub, carrying descriptive, language-dependent attributes on a per-language basis.

Key Information Stored

The table carries 17 documented columns. The distinguishing feature of a TL table is the LANGUAGE column, which is part of the primary key and the unique key. The most significant columns are:

• APPLICATION_ID – Identifies the owning Oracle application; part of the composite primary key and used to scope parameters to their application context.
• PARAM_DEFN_CODE – The parameter definition code, the principal business identifier linking each translation row back to its base definition.
• LANGUAGE – The NLS language code for which this translation row provides text.
• SOURCE_LANG – Indicates the source language from which the translation was derived, used by the MLS framework.
• USER_NAME – The translated user-facing name of the parameter.
• DEFAULT_STRING – The translated default value string presented to the user.
• DEFAULT_DESC – The translated description of the parameter default.
• PROMPT_LEFT and PROMPT_ABOVE – Translated prompt text rendered to the left of, or above, the parameter input field.
• USER_TIP – The translated tooltip or help text shown to the end user.
• ACCESS_KEY – An access/translation key value associated with the definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit who-columns recording creation and last modification.
• ZD_EDITION_NAME – The edition name supporting Online Patching (Editioning) in EBS 12.2.2.

The composite primary key BNE_PARAM_DEFNS_TL_PK comprises APPLICATION_ID, PARAM_DEFN_CODE, and LANGUAGE. The unique key BNE_PARAM_DEFNS_TL_UK1 extends this with ZD_EDITION_NAME, reflecting the edition-aware uniqueness introduced in 12.2.2. The primary key columns are the surrogate identifier for each translation row, while APPLICATION_ID and PARAM_DEFN_CODE act as the business-key candidate that links to the base table.

Common Use Cases and Queries

Typical uses include reporting on localized parameter prompts for Web ADI integrators, diagnosing missing translations where a base definition exists but no TL row is present for a required language, and auditing user-tip text changes over time.

A common query lists all translations for a given parameter definition across languages:

SELECT t.language, t.user_name, t.prompt_left,
       t.prompt_above, t.user_tip
FROM   bne_param_defns_tl t
WHERE  t.application_id    = :app_id
AND    t.param_defn_code   = :code
ORDER  BY t.language;

A missing-translation check compares base rows against TL rows:

SELECT b.application_id, b.param_defn_code
FROM   bne_param_defns_b b
WHERE  NOT EXISTS
       (SELECT 1 FROM bne_param_defns_tl t
        WHERE  t.application_id  = b.application_id
        AND    t.param_defn_code = b.param_defn_code
        AND    t.language        = USERENV('LANG'));

This pattern is frequently used before a localization rollout to confirm that every parameter has a Japanese or German prompt, preventing untranslated labels from appearing in Web ADI upload forms.

Related Objects

• BNE_PARAM_DEFNS_B – The base table for which this TL table provides translations; joined on APPLICATION_ID and PARAM_DEFN_CODE.
• BNE_PARAM_DEFNS_VL – The MLS view that joins _B and _TL to expose language-specific and base attributes transparently.
• BNE_PARAM_DEFNS_TL_PK / BNE_PARAM_DEFNS_TL_UK1 – The primary and unique constraints enforcing translation uniqueness.
• BNE_PARAM_VALUES – Parameter value storage that consumes translated prompts and defaults during runtime.
• FND_APPLICATION / FND_APPLICATION_TL – Provides the application name associated with APPLICATION_ID.
• FND_LANGUAGES / FND_LANGUAGES_TL – Supplies the language context referenced by the LANGUAGE column.
• FND_CONCURRENT_PROGRAMS – The program layer from which BNE parameter definitions are launched.

Because the ETRM metadata indicates a standalone classification with no mined FK relationships, joins to the base table and to FND lookup tables are based on shared business keys rather than declared foreign keys.