Results for “okl_formulae_tl_u1”

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

Overview

The OKL.OKL_FORMULAE_TL table is the translation (MLS) table for Oracle Lease and Finance Management (OKL) formulae definitions. It stores language-specific, user-facing text for lease formulae maintained in the base table OKL_FORMULAE_B, following Oracle Applications multilingual standards. In Oracle EBS 12.1.1 and 12.2.2, translated views such as OKL_FORMULAE_TL# expose this data for runtime display, ensuring that formula descriptions appear in the session language of the user. The table resides in the APPS_TS_TX_DATA tablespace, with its unique index in APPS_TS_TX_IDX, and its FND design data is registered as OKL.OKL_FORMULAE_TL.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault modeling view. Because it carries descriptive, language-dependent attributes keyed to a parent entity, it is best modeled as a satellite attached to the OKL_FORMULAE_B hub rather than as a hub or link in its own right.

Key Information Stored

The table is narrow by design; it delegates substantive formula mechanics to OKL_FORMULAE_B and holds only translatable text plus MLS bookkeeping. Its primary key is OKL_FORMULAE_TL_PK (ID, LANGUAGE), where ID is the surrogate key carried from the base table and LANGUAGE identifies the translation language. The unique index OKL_FORMULAE_TL_U1 (ID, LANGUAGE, ZD_EDITION_NAME) is the documented business-key candidate and also serves as the object referenced by the search term "okl_formulae_tl_u1".

• ID — number; joins to the corresponding formula row in OKL_FORMULAE_B.
• LANGUAGE — varchar2(12); the language of this translated row.
• SOURCE_LANG — varchar2(12); the language from which the translation was derived.
• SFWT_FLAG — varchar2; flag used by the translation batch program.
• DESCRIPTION — varchar2(1995); the user-entered, language-specific description of the formula.
• ZD_EDITION_NAME — varchar2(30); editioning column used in 12.2 online patching (Edition-Based Redefinition).

Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE and LAST_UPDATE_LOGIN — provide audit and concurrency tracking.

Common Use Cases and Queries

Typical usage centers on retrieving the correct localized description for a lease formula and on auditing translation completeness.

• Look up a formula's description in a specific language:

  SELECT t.id, t.language, t.description
  FROM   okl.okl_formulae_tl t
  WHERE  t.id = :formula_id
  AND    t.language = USERENV('LANG');

• Detect formulae missing a translation for a target language by comparing against OKL_FORMULAE_B.
• Report the number of translated rows per language for governance or localization tracking.
• Join to the base table to display formula name alongside translated description in a concurrent program or OAF page.

Because the object is fully edition-enabled, queries in 12.2 should generally go through the translated view or explicitly filter on ZD_EDITION_NAME when inspecting editioned data.

Related Objects

The table's documented dependency direction is that it does not reference other objects, while OKL_FORMULAE_TL# references it. The most significant related objects are:

• OKL.OKL_FORMULAE_B — base table; join on ID. The authoritative source for non-translatable formula attributes.
• OKL.OKL_FORMULAE_TL# — the MLS view over this table used by applications.
• Translated formula views in the OKL schema exposing DESCRIPTION in the runtime language.
• Translation batch program — the concurrent process that maintains SFWT_FLAG, SOURCE_LANG and translated DESCRIPTION values.