Search Results okl_cnsld_ar_strms_tl




Overview
Explore in AI Chat

Overview

OKL_CNSLD_AR_STRMS_TL is a translatable (language-specific) table in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the translated attribute columns associated with OKL_CNSLD_AR_STRMS_B, its base table, following Oracle's Multi-Language Support (MLS) standards. In EBS MLS architecture, the "_B" suffix denotes the base table holding language-independent data, while the "_TL" suffix denotes the translation table holding user-facing descriptive text per installed language.

The object's relationship data classifies it heuristically as standalone under Data Vault conventions. In modeling terms, this reflects that the table does not participate in a hub, link, or satellite structure within the extracted FK topology — it functions as a dependent translation store keyed by ID and LANGUAGE rather than as an independently integrating entity. Treat this classification as a modeling suggestion rather than an enforced constraint.

Key Information Stored

The table's documented physical schema under ETRM 12.2.2 comprises nine columns. The most significant are:

  • ID — The surrogate identifier inherited from the base table OKL_CNSLD_AR_STRMS_B. It is the join key linking a translation row to its language-independent parent record.
  • LANGUAGE — The NLS language code identifying which installed language this translation row represents. Together with ID, it forms the composite primary key OKL_CNSLD_AR_STRMS_TL_PK.
  • SOURCE_LANG — The source language from which the translation was derived, used by the MLS framework to track translation lineage.
  • SFWT_FLAG — The "Seed/Fix Workflow Translation" flag indicating whether the row's translation text reflects seeded (delivered) content or customer-maintained content, governing whether patches may overwrite it.
  • CREATED_BY, CREATION_DATE — Standard WHO columns recording the user and timestamp of initial row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification identity, timestamp, and login context.

The documented unique index OKL_CNSLD_AR_STRMS_TL_U1 (ID, LANGUAGE) is the business-key candidate, duplicating the primary key composition and enforcing one translation row per record per language. The composite key should be distinguished from the bare surrogate ID, which alone is non-unique in this table because it repeats once per installed language.

Common Use Cases and Queries

Primary use cases center on multi-language reporting and translation maintenance for consolidated accounts receivable streams. A typical query joins the translation to its base table to retrieve the correct descriptive text for the session language:

  • Retrieve translated text for a specific record and language: SELECT t.* FROM okl.okl_cnsld_ar_strms_tl t WHERE t.id = :p_id AND t.language = USERENV('LANG');
  • Join to the base table: SELECT b.id, t.source_lang FROM okl.okl_cnsld_ar_strms_b b, okl.okl_cnsld_ar_strms_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
  • Audit translation coverage: SELECT language, COUNT(*) FROM okl.okl_cnsld_ar_strms_tl GROUP BY language;
  • Detect customer-maintained versus seeded rows: filter on sfwt_flag to determine which translations may be safely regenerated during patching.

Reporting scenarios include multi-language lease and finance dashboards, MLS compliance audits, and translation-completeness checks ahead of upgrades.

Related Objects

  • OKL_CNSLD_AR_STRMS_B — The base table supplying language-independent columns; join on ID.
  • OKL_CNSLD_AR_STRMS_TL_PK — Composite primary key index (ID, LANGUAGE) enforcing uniqueness.
  • OKL_CNSLD_AR_STRMS_TL_U1 — Unique index reinforcing the business key on (ID, LANGUAGE).
  • FND_LANGUAGES — Reference table validating the LANGUAGE code against installed languages.
  • FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user identities for audit reporting.

Because the object is standalone per the mined relationship data, no further FK-dependent tables are documented at this time.