Search Results okl_ext_pay_invs_tl




Overview
Explore in AI Chat

Overview

OKL_EXT_PAY_INVS_TL is the translatable (TL) child table that stores the language-dependent descriptive columns for the Oracle EBS Leasing and Finance Management (OKL) extension payment invoice entity. Under the Oracle Multi-Language Support (MLS) architecture, a base table (suffix _B) holds language-independent data, while its companion _TL table holds translated text keyed by language. This table therefore does not exist in isolation; it depends directly on OKL_EXT_PAY_INVS_B, which owns the primary business entity rows, and it supplies the human-readable descriptive text rendered according to the session language of the EBS user.

In Data Vault modeling terms, the heuristic classification derived from the FK structure is standalone, with no external foreign-key dependencies documented beyond its parent base table. This suggests modeling the object as a satellite hanging off the OKL_EXT_PAY_INVS_B hub, where the natural parent key (ID) plus LANGUAGE forms the descriptive grain. Analysts building a warehouse should treat OKL_EXT_PAY_INVS_TL as the descriptive attribute satellite, joining back to the base entity on ID and LANGUAGE.

The object resides in the OKL schema and is documented as VALID in both ETRM 12.1.1 and 12.2.2 reference material, with a documented physical schema of 12 columns.

Key Information Stored

The table's descriptive content is anchored by three identifier and metadata columns that are most important for querying and joining:

  • ID — the surrogate identifier linking each translation row back to the parent base record in OKL_EXT_PAY_INVS_B. It is part of the composite primary key OKL_EXT_PAY_INVS_TL_PK.
  • LANGUAGE — the ISO language code identifying the translation target; together with ID it forms the business-key candidate captured by unique index OKL_EXT_PAY_INVS_TL_U1 (ID, LANGUAGE) and the primary key OKL_EXT_PAY_INVS_TL_PK (ID, LANGUAGE).
  • SOURCE_LANG — records the source language from which a translation was derived, supporting MLS maintenance workflows.
  • SFWT_FLAG — the standard MLS "Seed/Feed/Wholesale Translation" style flag used to indicate translation status.
  • DESCRIPTION — the principal translatable text attribute, carrying the user-facing description of the extension payment invoice.
  • SOURCE and STREAM_TYPE — descriptive/classifying attributes describing the origin and stream category of the invoice entry.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle WHO audit columns tracking insertion and last modification.

The surrogate-vs-business-key distinction is central: the database-level primary key is composite (ID, LANGUAGE), and the documented unique index OKL_EXT_PAY_INVS_TL_U1 reinforces that (ID, LANGUAGE) is the true business identifier, with no standalone surrogate column beyond ID itself.

Common Use Cases and Queries

The most frequent scenario is retrieving the description of an extension payment invoice in a specific language. A typical pattern joins the base and translation tables and filters by session language:

  • SELECT b.ID, t.DESCRIPTION, t.SOURCE, t.STREAM_TYPE FROM OKL_EXT_PAY_INVS_B b, OKL_EXT_PAY_INVS_TL t WHERE b.ID = t.ID AND t.LANGUAGE = USERENV('LANG');
  • Reporting extracts that require translated descriptions across multiple languages rely on the (ID, LANGUAGE) unique index for efficient lookup.
  • Data-quality checks compare row counts between _B and _TL to detect missing translations, using GROUP BY ID and HAVING COUNT(LANGUAGE) filters.
  • Audit reports use the WHO columns (CREATED_BY, LAST_UPDATE_DATE) to trace translation maintenance activity.

Related Objects

  • OKL_EXT_PAY_INVS_B — the mandatory parent base table joined on ID; supplies language-independent columns.
  • OKL_EXT_PAY_INVS_TL_PK — the composite primary key constraint on (ID, LANGUAGE).
  • OKL_EXT_PAY_INVS_TL_U1 — the unique index serving as the documented business-key candidate.
  • OKL extension payment invoice views and concurrent programs that render MLS text read from this table via the base table relationship.