Results for “okl_parameters_tl”

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

Overview

OKL_PARAMETERS_TL is the translation (MLS) table for the OKL_PARAMETERS_B base table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. Following Oracle's Multi-Lingual Support (MLS) architecture, OKL_PARAMETERS_B stores language-independent parameter data, while OKL_PARAMETERS_TL stores the translatable attribute values — specifically the DESCRIPTION column — keyed by language. This separation permits the same parameter definition to present localized descriptive text per installed language without duplicating the base configuration. In EBS 12.1.1 and 12.2.2 the table resides in the OKL schema and is marked VALID.

From a Data Vault modeling perspective, the mined metadata suggests a satellite classification. OKL_PARAMETERS_TL does not carry independent business identity of its own; it hangs off the base entity identified by ID and LANGUAGE, describing attributes of that entity. This heuristic classification is a modeling suggestion only and reflects the FK structure rather than a formally implemented Data Vault design. The companion base table OKL_PARAMETERS_B would occupy the hub (or hub plus satellite) role.

Key Information Stored

The documented physical schema exposes 11 columns. The most significant are:

• ID — Surrogate identifier linking the translation row to its parent base record in OKL_PARAMETERS_B. Part of the composite primary key.
• LANGUAGE — The installed language code (for example, US, DE, FR) identifying which locale the row translates. The second component of the primary key.
• SOURCE_LANG — The language of the source text, used by MLS tooling to track translation origin.
• SFWT_FLAG — The "Seed/Foundation, Translatable" indicator used by Oracle's translation synchronization utilities to govern how the row participates in language patching.
• DESCRIPTION — The translatable descriptive text for the parameter. This is the primary payload of the table and the reason for its existence.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit "WHO" columns capturing row creation and modification metadata.
• ZD_EDITION_NAME — The editioning column introduced in EBS 12.2 online patching, also part of the unique index.

The primary key is OKL_PARAMETERS_TL_PK over (ID, LANGUAGE). A unique index, OKL_PARAMETERS_TL_U1, spans (ID, LANGUAGE, ZD_EDITION_NAME), making this combination the documented business-key candidate.

Common Use Cases and Queries

Typical usage centers on retrieving localized parameter descriptions for reporting, user-interface rendering, and configuration review. A standard join pattern retrieves a translated description alongside the base parameter:

SELECT b.id, b.parameter_code, t.description
FROM   okl.okl_parameters_b b,
       okl.okl_parameters_tl t
WHERE  b.id = t.id
AND    t.language = USERENV('LANG')

Reporting queries that must resolve descriptions across all active languages select on LANGUAGE explicitly. Administrators verifying translation coverage can compare row counts in OKL_PARAMETERS_TL per LANGUAGE against the base table to detect missing translations. Diagnostics involving the ZD_EDITION_NAME column are relevant on 12.2.2 for online-patching edition validation.

Related Objects

• OKL_PARAMETERS_B — The base table supplying the language-independent rows; joined on ID.
• OKL_PARAMETERS_TL_PK — Composite primary key constraint (ID, LANGUAGE).
• OKL_PARAMETERS_TL_U1 — Unique index (ID, LANGUAGE, ZD_EDITION_NAME).
• Other OKL_%_TL tables following the same MLS pattern (for example, translated lookup tables in the OKL schema) share identical structural conventions.

In practice, OKL_PARAMETERS_TL is almost never queried in isolation; it is consumed alongside its base table, and any application logic or concurrent program that resolves a parameter description transparently joins the two on ID with a language filter.