Search Results okl_trx_types_tl




Overview
Explore in AI Chat

Overview

OKL_TRX_TYPES_TL is the translation table for transaction types within the Oracle Lease and Finance Management (OKL) module. It stores the language-dependent, translatable columns associated with the base table OKL_TRX_TYPES_B, following Oracle's Multi-Language Support (MLS) standards. Where the base table holds language-independent attributes of a transaction type—such as its identifier and functional flags—the _TL table carries the textual descriptions that users see in their session language.

From a Data Vault modeling perspective, the metadata classifies this object as standalone (heuristic, mined from its foreign key structure). This suggests it is best modeled as an independent satellite-like entity rather than a hub or link, since it does not participate in foreign key relationships to other tables. It is keyed on the combination of ID and LANGUAGE, meaning each transaction type can have one translated row per installed language.

Key Information Stored

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

  • ID — Surrogate identifier linking the translated row to its parent transaction type in OKL_TRX_TYPES_B. It forms the first component of both the primary key and the unique index.
  • LANGUAGE — The NLS language code identifying which translation this row represents. It is the second component of the primary key and the unique index.
  • NAME — The translated display name of the transaction type, selected per the user's language. This is the business-key candidate referenced by the unique index OKL_TRX_TYPES_TL_UK.
  • DESCRIPTION — The translated long description providing business context for the transaction type.
  • SOURCE_LANG — The source language from which the translation was derived, per MLS conventions.
  • SFWT_FLAG — The standard "Seed/Force-Translate" indicator used by Oracle's translation framework to mark whether the row may be overwritten during language patching.
  • CONTRACT_HEADER_LINE_FLAG — A flag controlling whether the transaction type applies to contract header or line level processing.
  • TRANSACTION_HEADER_LINE_DETAIL — A translated attribute describing header, line, or detail-level transaction behavior.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification metadata.
  • ZD_EDITION_NAME — The editioning column that supports Oracle's Edition-Based Redefinition (EBR), enabling online patching typical of EBS 12.2.x.

The primary key OKL_TRX_TYPES_TL_PK is defined on (ID, LANGUAGE). An additional unique index, OKL_TRX_TYPES_TL_U1, is defined on (ID, LANGUAGE, ZD_EDITION_NAME), accommodating the editioning model. The business-key candidate OKL_TRX_TYPES_TL_UK covers (NAME, LANGUAGE).

Common Use Cases and Queries

Typical usage involves joining the base table to its translations to present transaction type names in the logged-in user's language. A standard pattern filters by the current NLS environment:

  • Reporting on active transaction types with translated names: SELECT b.ID, t.NAME, t.DESCRIPTION FROM OKL_TRX_TYPES_B b, OKL_TRX_TYPES_TL t WHERE b.ID = t.ID AND t.LANGUAGE = USERENV('LANG').
  • Validating translation completeness by identifying base rows lacking a translation for a given language.
  • Populating picklists or value sets in OKL forms and self-service pages using the translated NAME.
  • Auditing change history through CREATED_BY, LAST_UPDATED_BY, and the date columns.

Related Objects

  • OKL_TRX_TYPES_B — The base table holding language-independent transaction type data; joined on ID.
  • OKL_TRX_TYPES_VL — A view that automatically joins the base and translation tables for simplified access.
  • OKL_TRX_TYPES — The synonym or underlying object exposed to the application layer.
  • FND_LANGUAGES — The language repository referenced by the LANGUAGE column.
  • OKL_TRX_TYPES_TL_PK / OKL_TRX_TYPES_TL_UK — Constraint objects enforcing primary and business keys.

Because the entity is classified as standalone, no foreign key dependencies beyond the implicit linkage to OKL_TRX_TYPES_B and the MLS framework tables are documented.