Results for “okl_validation_results_tl”

50+ results




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

Overview

OKL_VALIDATION_RESULTS_TL is a translatable (TL) table in the OKL schema of Oracle E-Business Suite, belonging to the Lease and Finance Management (OKL) product family. It stores the language-dependent translation text for validation results produced by the leasing validation engine. Because OKL is deployed in multi-language installations, Oracle separates the language-independent attributes of a validation result into the base table OKL_VALIDATION_RESULTS_B while the user-facing descriptive text is held here, one row per installed language. The table is documented in ETRM 12.2.2 with ten columns and is classified as VALID in the OKL schema.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests the object functions most naturally as a reference or lookup satellite: it carries descriptive, language-specific payload (the validation text) keyed by an identifier and language rather than participating in parent-child foreign key relationships of its own. In a Data Vault model it would therefore typically be treated as a satellite hanging off a hub or link defined by the underlying validation-result entity, with LANGUAGE forming part of the natural composite key.

Key Information Stored

The primary key is OKL_VLRT_PK, a composite key defined over the columns ID and LANGUAGE. ID is the surrogate identifier inherited from the base validation-result record; LANGUAGE identifies the translation language of the row. Together they guarantee one text translation per language per validation result, which is the classic TL pattern used throughout EBS (for example, _TL tables paired with _B tables).

  • ID — surrogate identifier of the validation result; part of the composite primary key and the join back to the base table and to source validation logic.
  • LANGUAGE — the language code for this translated row; second component of OKL_VLRT_PK.
  • SOURCE_LANG — the language from which the translation was derived, used by the translation-maintenance framework to detect stale or missing translations.
  • VALIDATION_TEXT — the translated message or description displayed to the user when a leasing validation fails or returns information; this is the principal business payload of the table.
  • SFWT_FLAG — the "Seed/Force/Whatever/Translate" indicator used by Oracle's translation utilities to control whether this row's text is overwritten during language patching.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — record who created and last modified each translation row and when, supporting audit and troubleshooting.

Common Use Cases and Queries

The most common requirement is resolving a human-readable validation message for the current session language. A typical query joins the base table to this TL table on ID and LANGUAGE:

  • Join pattern: OKL_VALIDATION_RESULTS_B b, OKL_VALIDATION_RESULTS_TL t WHERE b.ID = t.ID AND t.LANGUAGE = USERENV('LANG') to return VALIDATION_TEXT in the user's language.
  • Translation completeness reporting: compare row counts per ID across LANGUAGE values to find validation results missing translations in a specific language — a frequent pre-upgrade or localization audit.
  • Message maintenance: extract all rows into a translation spreadsheet (ID, LANGUAGE, VALIDATION_TEXT, SFWT_FLAG) for bulk translation loading.
  • Diagnostics: query by ID and LAST_UPDATE_DATE to determine when a validation message was last changed and by whom, useful when a validation result behaves unexpectedly after a patch.

Related Objects

  • OKL_VALIDATION_RESULTS_B — the base (language-independent) table; joined on ID, and the parent of this TL row.
  • OKL_VALIDATION_RESULTS_VL — the MLS view over the _B and _TL tables, exposing VALIDATION_TEXT for the run-time language; most application code and reports should query this view rather than the TL table directly.
  • OKL_VALIDATION_RESULTS_TL sibling _TL tables in OKL (for example the translations for contracts, templates, and rule text) that follow the same PK (ID, LANGUAGE) pattern.
  • FND_LANGUAGES — the language definition table; LANGUAGE values in this table correspond to FND_LANGUAGES.LANGUAGE_CODE.
  • FND_LOOKUPS / FND_APPLICATION — used to identify the OKL application context when deriving the correct language set for a query.