Results for “okl_operands_tl”

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

Overview

OKL_OPERANDS_TL is the translatable (MLS) child table of OKL_OPERANDS_B in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) product family. Oracle Leasing and Finance Management uses operands to define the configurable building blocks — arithmetic expressions, variables, constants, and operators — that drive contract pricing, interest calculation, residual value computation, and rule evaluation within the lease origination and contract management flows. Because operand descriptions and labels must be presented in the user's session language, the descriptive attributes are held in this translation table rather than in the base table, following Oracle's Multi-Lingual Support (MLS) standard.

Physically, the table resides in the OKL schema and contains eleven documented columns in the 12.2.2 ETRM physical model. It is classified heuristically as a standalone object in Data Vault terms rather than as a hub, link, or satellite; in practice, its functional behavior is that of a language-specific satellite attached to the OKL_OPERANDS_B hub, keyed by the operand identifier and the language code. Treating it as a satellite in a Data Vault model is a reasonable modeling suggestion, since each row carries descriptive, non-key context that varies only by language and edition.

Key Information Stored

The primary key OKL_OPERANDS_TL_PK is composed of ID and LANGUAGE, the standard MLS composite that ties each translated row back to its parent operand record. The business-key candidate identified by the unique index OKL_OPERANDS_TL_U1 extends this to ID, LANGUAGE, and ZD_EDITION_NAME, reflecting the 12.2.2 editioning support introduced for online patching.

• ID — surrogate identifier of the parent operand in OKL_OPERANDS_B; the join key across the base and translation tables.
• LANGUAGE — the NLS language code for the translated row; combined with ID it forms the primary key.
• SOURCE_LANG — the language of the source row from which the translation was derived, used by the MLS seed/refresh process.
• DESCRIPTION — the translated descriptive text for the operand, the principal business-facing attribute of this table.
• ZD_EDITION_NAME — edition identifier supporting Edition-Based Redefinition in 12.2.x, part of the unique business-key index.
• SFWT_FLAG — the translated-flag indicator used by the MLS synchronization utilities to track whether the row has been translated.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO columns providing full auditability of insert and update activity.

Common Use Cases and Queries

Typical usage centers on multilingual reporting and user-interface rendering. To retrieve the description of an operand in the session language with fallback to the base language, a common pattern joins the base and translation tables:

• Listing operands with localized descriptions for a pricing rule maintenance screen.
• Auditing which operands have not yet been translated by filtering on SFWT_FLAG.
• Identifying duplicate or missing translations per language using the unique index OKL_OPERANDS_TL_U1 as the expected cardinality.

A representative query is: SELECT tl.language, tl.description FROM okl.okl_operands_tl tl WHERE tl.id = :operand_id AND tl.language = USERENV('LANG'); joined to OKL_OPERANDS_B on ID for the untranslated attributes. Extracts for data-warehouse loading typically select all languages and rely on ZD_EDITION_NAME to filter to the active edition.

Related Objects

• OKL_OPERANDS_B — the base table holding non-translatable operand columns; joined on ID.
• OKL_OPERANDS_VL — the MLS view exposing base and translated columns as a single logical entity.
• OKL_OPERANDS_TL_PK / OKL_OPERANDS_TL_U1 — the primary-key constraint and unique index enforcing uniqueness on (ID, LANGUAGE) and (ID, LANGUAGE, ZD_EDITION_NAME).
• OKL_RULES / OKL_RULES_B — rule definitions that reference operands in pricing expressions.
• FND_LANGUAGES — provides the language code list referenced by the LANGUAGE and SOURCE_LANG columns.
• FND_LOOKUPS — supplies related seeded lookup values used alongside operand definitions.

As a standalone MLS table, OKL_OPERANDS_TL is never the driver of joins; it is always accessed through its parent OKL_OPERANDS_B and the OKL_OPERANDS_VL view.