Search Results okl_invc_line_types_tl




Overview
Explore in AI Chat

Overview

OKL_INVC_LINE_TYPES_TL is the translation (TL) table for lease and finance invoice line types within the OKL schema, which belongs to the Oracle Lease and Finance Management module. Its documented purpose is to hold the translatable columns of OKL_INVC_LINE_TYPES_B, following Oracle's Multi-Language Support (MLS) standards. In the context of Oracle EBS 12.1.1 and 12.2.2, this means the table stores one row per language for each invoice line type defined in the base table, enabling multilingual descriptive text while keeping language-independent attributes in the base.

The metadata classifies the object as a standalone entity under a heuristic Data Vault model, meaning no foreign keys were mined that would attach it to another documented hub or link. As a modeling suggestion, an MLS translation table is most naturally treated as a satellite: its grain is the base entity key plus LANGUAGE, and it carries descriptive, language-dependent attributes that change over time. The surrogate primary key OKL_INVC_LINE_TYPES_TL_PK is composed of ID and LANGUAGE, and the unique index OKL_INVC_LINE_TYPES_TL_U1 on the same two columns reinforces that combination as the business-key candidate.

Key Information Stored

The table is documented with eleven columns. The most significant are:

  • ID — the surrogate identifier shared with the base table; part of both the primary key and the unique index.
  • LANGUAGE — the language code for the translation row; the second component of the primary key and unique index.
  • SOURCE_LANG — the language from which the translated text was derived, indicating whether the row is the source or a derived translation.
  • NAME — the translated name of the invoice line type, the principal user-facing value.
  • DESCRIPTION — the translated long description of the line type.
  • SFWT_FLAG — the standard MLS "seed from which text" flag used to indicate translation provenance and maintenance behavior.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO-column audit set recording who created and last modified each row and when.

The surrogate primary key (ID, LANGUAGE) differs from the business-key candidate only in that both documented unique constraints cover the same column pair; no single-column business key exists in the translation table. Because translation text must never be joined by name, all joins to related data flow through ID.

Common Use Cases and Queries

The primary use case is retrieving invoice line type descriptions in the session or reporting language. A typical query joins the translation table to the base table and filters by language:

  • SELECT b.id, t.name, t.description FROM okl.okl_invc_line_types_b b, okl.okl_invc_line_types_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
  • Verifying that every base row has a translation for a required language, to detect missing MLS rows before go-live or after a language patch.
  • Reporting on translation completeness using SOURCE_LANG and SFWT_FLAG to identify rows still carrying untranslated source text.
  • Auditing changes to line type descriptions over time through CREATION_DATE and LAST_UPDATE_DATE.
  • Building multilingual lease invoice or billing reports where line type labels must render in each user's language.

Queries should always constrain LANGUAGE, since an unconstrained join returns one row per installed language.

Related Objects

The most significant related objects follow from the MLS pattern and the invoice line type domain:

  • OKL_INVC_LINE_TYPES_B — the base table holding language-independent columns; joined on ID and the true parent of this translation table.
  • OKL_INVC_LINE_TYPES_TL_PK / OKL_INVC_LINE_TYPES_TL_U1 — the primary key and unique index enforcing the (ID, LANGUAGE) grain.
  • OKL_INVOICES — the lease invoice header domain that consumes invoice line types.
  • OKL_INVOICE_LINES — invoice lines whose type references the base line type definitions translated here.
  • Oracle Lease and Finance Management invoice and billing concurrent programs and APIs that read line type descriptions through the base table's translated views.

Note that the mined relationship data shows no foreign keys, so joins to OKL_INVC_LINE_TYPES_B and other OKL invoice objects are enforced by application logic rather than by database constraints.