Search Results okl_ext_sell_invs_tl




Overview
Explore in AI Chat

Overview

The table OKL_EXT_SELL_INVS_TL resides in the OKL schema, which supports Oracle Lease and Finance Management (OKL) within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the translation table (the _TL suffix) for the base table OKL_EXT_SELL_INVS_B, holding the multi-lingual columns required by Oracle's Multi-Lingual Support (MLS) standard. The base table stores language-independent attributes of external selling invoice records used in lease and finance contracts, while this translatable companion stores the human-readable, language-specific text for those records. In ETRM implementations, this table is therefore queried whenever invoice-related descriptive text — such as private-label formatting, invoice messages, or descriptions — must be rendered in a user's session language.

The metadata classifies this object heuristically, from its foreign-key structure, as a standalone Data Vault model — it has no mined parent/child FK links. In Data Vault terms this would suggest treating it as a satellite-like descriptive store, though its standalone status means it requires deliberate modeling rather than a natural hub-and-satellite decomposition. The presence of surrogate and unique keys nonetheless gives it the anchoring characteristics typical of a dimension-supporting translation entity.

Key Information Stored

The table contains 14 documented columns. The primary key OKL_EXT_SELL_INVS_TL_PK is defined on the composite of ID and LANGUAGE. A parallel unique index, OKL_EXT_SELL_INVS_TL_U1, is also defined on (ID, LANGUAGE), confirming this pair as the business-key candidate that uniquely identifies one translated row per invoice record per installed language.

The surrogate anchor is ID; the business-key candidate is the composite (ID, LANGUAGE).

Common Use Cases and Queries

Typical usage retrieves translated invoice text for reporting, printing, or UI display in the user's language. Because MLS tables store one row per language, queries must filter by LANGUAGE or join to a language-source view.

  • Retrieve localized invoice details for a specific record: 
    SELECT t.invoice_message, t.description, t.xtrx_private_label
FROM   okl.okl_ext_sell_invs_tl t
WHERE  t.id = :p_id
AND    t.language = USERENV('LANG');
  • Audit translation coverage using the MLS flag: 
    SELECT id, language, sfwt_flag
FROM   okl.okl_ext_sell_invs_tl
WHERE  sfwt_flag != 'Y';
  • Join to the base table for complete invoice reporting, linking on ID while constraining LANGUAGE to avoid duplicate rows.

Related Objects

The most significant dependency is its base table, with which it shares the ID join column. Related objects include:

  • OKL_EXT_SELL_INVS_B — Base (non-translatable) table; join on ID.
  • OKL_EXT_SELL_INVS_TL_PK — Primary-key constraint on (ID, LANGUAGE).
  • OKL_EXT_SELL_INVS_TL_U1 — Unique index on (ID, LANGUAGE).
  • OKL_EXT_SELL_INVS_VL — The typical MLS-language view exposing translated columns.
  • FND_LANGUAGES — Reference source for valid LANGUAGE codes.
  • FND_SESSION_LANGUAGES / USERENV('LANG') — Runtime language resolution used in queries.
  • OKL lease/contract invoice APIs — Consume translated invoice text for document generation.