Results for “okl_trx_quotes_tl”

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

Overview

OKL_TRX_QUOTES_TL is the translation (multi-language support, or MLS) table that stores the translatable descriptive columns associated with lease and finance quote transactions in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL schema, which is owned by the Lease and Finance Management product (Oracle Lease Management, or OKL). As stated in the ETRM documentation, this table holds "translatable columns from OKL_TRX_QUOTES_B, per MLS standards." Within Oracle Applications, the _TL suffix convention denotes a translation table that carries one row per installed language for each base-language row in the corresponding _B (base) table. This permits the same quote to be displayed with language-specific comments while preserving a single business entity in the base table.

From a Data Vault modeling perspective, the mined FK structure classifies OKL_TRX_QUOTES_TL as a standalone entity. This is a heuristic suggestion: because no foreign key relationships were identified, the table behaves neither strictly as a hub nor as a link. Conceptually it functions as a satellite carrying descriptive, language-dependent attributes keyed to the combination of the quote identifier and the language code, and it should be modeled accordingly when reverse-engineering the lease quote subject area.

Key Information Stored

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

• ID — The quote identifier inherited from the base table OKL_TRX_QUOTES_B; together with LANGUAGE it forms the primary key OKL_TRX_QUOTES_TL_PK.
• LANGUAGE — The language code for the translated row, part of both the primary key and the unique index OKL_TRX_QUOTES_TL_U1.
• SOURCE_LANG — The base language from which the translation originates.
• SFWT_FLAG — The "translated or not" indicator used by the MLS framework to signal whether the row has been actively translated.
• COMMENTS — The principal translatable business attribute: free-form text associated with the quote, rendered per language.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle who-columns auditing the row's lifecycle.

The surrogate primary key is the composite (ID, LANGUAGE). The unique index OKL_TRX_QUOTES_TL_U1 is documented over the same two columns, making (ID, LANGUAGE) the effective business-key candidate as well. The translation itself does not introduce new business identifiers; it depends entirely on the ID value of the parent base row.

Common Use Cases and Queries

Reporting and integration scenarios frequently join the translation to its base table to retrieve language-appropriate descriptions. A typical query joins on ID and constrains by LANGUAGE:

• SELECT b.ID, t.COMMENTS FROM OKL_TRX_QUOTES_B b, OKL_TRX_QUOTES_TL t WHERE b.ID = t.ID AND t.LANGUAGE = USERENV('LANG');
• Listing all installed translations for a single quote (SELECT LANGUAGE, COMMENTS WHERE ID = :quote_id) to verify completeness.
• Detecting untranslated records by filtering on SFWT_FLAG or comparing SOURCE_LANG with LANGUAGE.
• Auditing translation currency using LAST_UPDATE_DATE against the base row's timestamp.

These patterns support multilingual lease-quote reports, translation completeness dashboards, and data-conversion validation during upgrades.

Related Objects

The most significant related objects revolve around the base quote entity and the shared MLS framework:

• OKL_TRX_QUOTES_B — The base table; joined on ID. The translation row exists only for a corresponding base row.
• OKL_TRX_QUOTES_V / _TL views — MLS views that union base and translated columns for user-facing access.
• FND_LANGUAGES — Provides the valid values for LANGUAGE and SOURCE_LANG.
• OKL_TRX_QUOTES_H / associated history tables — Retain change history for the quote entity.
• OKL_TRX_QUOTES_TP — Where present, holds translation tables for related quote attribute groups.

Because the FK classification is standalone, no enforced foreign-key dependents were documented; joins to OKL_TRX_QUOTES_B are convention-driven rather than constraint-driven, and consumers should enforce the ID relationship in application or integration logic.