Search Results okl_invoice_formats_tl




Overview
Explore in AI Chat

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

Overview

The OKL_INVOICE_FORMATS_TL table is a core metadata object within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It stores the multi-language translations of invoice format definitions used in lease and finance contracts. Per the documented description, this table holds "translatable columns from OKL_INVOICE_FORMATS_B, per MLS standards," meaning it is the translation layer of a standard Oracle Multi-Language Support (MLS) entity pair. In Oracle EBS, MLS entities are physically split into a base table (_B) that holds language-independent and non-translatable attributes, and a translation table (_TL) that holds language-dependent text such as names and descriptions. Invoice formats define the templates and layouts used when generating customer-facing lease invoices and billing documents, so this table is central to how OKL presents invoice layouts to users across different locales.

The heuristic Data Vault classification mined from the foreign key structure is standalone. As a modeling suggestion, this implies the table behaves more like a reference or lookup satellite than a hub or link: it carries descriptive attributes keyed by a composite identifier rather than participating in a network of referential relationships. Its role is largely subordinate to the parent base table.

Key Information Stored

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

  • ID — Surrogate identifier that links each translation row to its parent record in OKL_INVOICE_FORMATS_B. This is the primary join key back to the base entity.
  • LANGUAGE — The language code indicating which locale the translated values apply to, such as US or ES.
  • SOURCE_LANG — The language of the source record before translation was applied.
  • SFWT_FLAG — The "Seed/Foundation" or translation-status flag used by EBS MLS tooling to track the state of a translated row.
  • NAME — The translated, user-facing name of the invoice format.
  • DESCRIPTION — The translated descriptive text for the invoice format.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each row.

The surrogate primary key is OKL_INVOICE_FORMATS_TL_PK on the composite (ID, LANGUAGE). A unique business-key candidate is documented as OKL_INVOICE_FORMATS_TL_U1 on (ID, LANGUAGE), which preserves the invariant that only one translation exists per format per language.

Common Use Cases and Queries

Typical use cases include reporting on invoice format names in a user's session language, validating that all invoice formats have complete translations, and extracting format metadata for interface or migration work.

  • Resolving a format name for a given locale: 
    SELECT tl.id, tl.name, tl.description
FROM   okl_invoice_formats_tl tl
WHERE  tl.language = USERENV('LANG')
AND    tl.id = :p_format_id;
  • Detecting formats missing a translation in a target language: 
    SELECT b.id
FROM   okl_invoice_formats_b b
       LEFT JOIN okl_invoice_formats_tl tl
         ON b.id = tl.id AND tl.language = 'US'
WHERE  tl.id IS NULL;
  • Auditing translation currency using the audit columns and SFWT_FLAG.

These queries are commonly embedded in concurrent programs, BI Publisher reports, and OAF-based invoice format setup pages within the OKL module.

Related Objects

The most significant related objects and join columns are:

  • OKL_INVOICE_FORMATS_B — The base table; joined on ID = OKL_INVOICE_FORMATS_TL.ID. This is the primary parent entity.
  • OKL_INVOICE_FORMATS_TL_PK and OKL_INVOICE_FORMATS_TL_U1 — The primary and unique indexes enforcing the (ID, LANGUAGE) key.
  • FND_LANGUAGES — Referenced conceptually via LANGUAGE to resolve installed language names.
  • OKL invoice and billing generation tables that consume invoice format definitions for rendering lease invoices.
  • Standard MLS translation maintenance forms and the translation upload API used to populate this table.

Because the FK classification is standalone, no additional child tables depend on this object; it is a terminal translation satellite for its base entity.