Results for “variable_name”

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

Overview

The OKC_BUS_VARIABLES_TL table resides in the OKC schema and belongs to the Contracts Core (OKC) product family within Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is a translation ("_TL") table that stores the language-dependent descriptive attributes of business variables. Business variables are the reusable, semantically named values that can be embedded inside contract clauses; the base definition of each variable is held in OKC_BUS_VARIABLES_B, while the human-readable text that must vary by installed language is stored here. Every row therefore represents one language-specific rendering of a single business variable.

From a heuristic Data Vault perspective, the documented foreign key structure — VARIABLE_CODE pointing to OKC_BUS_VARIABLES_B and LANGUAGE pointing to FND_LANGUAGES — suggests classifying OKC_BUS_VARIABLES_TL as a link object, connecting the business-variable hub to the language reference. Because it also carries descriptive attributes (VARIABLE_NAME, DESCRIPTION), it behaves in practice as a combined link-and-satellite structure, capturing the translated descriptive context of each variable.

Key Information Stored

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

• VARIABLE_CODE — The business identifier of the parent variable in OKC_BUS_VARIABLES_B; together with LANGUAGE it forms part of the primary key and the unique index.
• LANGUAGE — The NLS language code (FK to FND_LANGUAGES) identifying which language this row's text is written in.
• SOURCE_LANG — The language from which this translation was derived, used by the translation/language-maintenance utilities.
• VARIABLE_NAME — The translated display name of the business variable shown to users when authoring clauses.
• DESCRIPTION — The translated explanatory text describing the variable's purpose and expected value.
• ZD_EDITION_NAME — The editioning column introduced under the 12.2 online patching architecture, governing which edition a row is visible to.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns tracking row ownership and change history.

The surrogate-style primary key is defined by OKC_BUS_VARIABLES_TL_PK1 on (VARIABLE_CODE, LANGUAGE). A separate unique index, OKC_BUS_VARIABLES_TL_U1 on (VARIABLE_CODE, LANGUAGE, ZD_EDITION_NAME), functions as the business-key candidate and enforces edition-aware uniqueness.

Common Use Cases and Queries

Typical usage centers on multilingual clause authoring and reporting. A common pattern joins this table to its base table to retrieve a variable's translated name for a specific language:

• Resolving a display name: SELECT v.variable_code, t.variable_name FROM okc_bus_variables_b v, okc_bus_variables_tl t WHERE v.variable_code = t.variable_code AND t.language = USERENV('LANG');
• Auditing which variables lack a translation in a supported language by comparing distinct LANGUAGE values against FND_LANGUAGES.
• Reporting on translated descriptions for documentation of clause libraries and contract templates.
• Verifying edition-specific visibility in 12.2 by filtering on ZD_EDITION_NAME.

Because translations are keyed by VARIABLE_CODE and LANGUAGE, queries should always constrain the language to avoid returning one row per installed language.

Related Objects

• OKC_BUS_VARIABLES_B — The base (non-translatable) table holding the variable definition; joined on VARIABLE_CODE.
• FND_LANGUAGES — The language reference table; joined on LANGUAGE.
• OKC_BUS_VARIABLES_VL — The standard MLS view that unions the base and translation tables to present a single logical row.
• OKC_CLAUSES / OKC_CLAUSE_VARIABLES — Clause definitions and their variable associations that ultimately consume these variables.
• OKC_BUS_VARIABLE_SOURCES — Related metadata describing where variable values originate.
• FND_TERRITORIES and FND_LANGUAGE_TL — Supporting NLS reference tables used alongside FND_LANGUAGES in translation reporting.

Together these objects support the end-to-end flow from variable definition, through translation, to clause authoring in the Oracle Contracts repository.