Search Results okc_condition_lines_tl




Overview
Explore in AI Chat

Overview

The OKC_CONDITION_LINES_TL table resides in the OKC schema and belongs to the Contracts Core (OKC) product family within Oracle E-Business Suite. It stores the translatable (Multi-Lingual Support, or MLS) attributes corresponding to rows held in the base table OKC_CONDITION_LINES_B. Each row in the base table that carries language-dependent descriptive text is represented here once per installed language, allowing contract condition line descriptions to be presented in the appropriate session language without duplicating the structural, non-translatable data maintained in the _B table. This split follows the standard Oracle MLS architectural convention of pairing a "_B" base table with a "_TL" translation table.

From a data modeling perspective, the ETRM heuristic that classifies this object as standalone is best understood as a suggestion derived purely from the mined foreign-key structure rather than a definitive design mandate. Strictly speaking, in a Data Vault treatment, OKC_CONDITION_LINES_TL behaves as a satellite attached to the OKC_CONDITION_LINES_B hub, since it carries descriptive and audit attributes keyed by the base entity's identifier and language. The metadata records no foreign key to the base table, which is why the heuristic treats it as standalone; implementers planning a Data Vault layer should nonetheless model it as a satellite of the condition line hub.

Key Information Stored

The table contains twelve documented columns. The most important are:

  • ID — Surrogate identifier inherited from the base condition line; forms part of the composite primary key and joins back to OKC_CONDITION_LINES_B.
  • LANGUAGE — The MLS language code; together with ID, it constitutes the primary key OKC_CONDITION_LINES_TL_PK, uniquely identifying a translated row.
  • SOURCE_LANG — Indicates the language from which the translated values were sourced, supporting MLS language-derivation logic.
  • SFWT_FLAG — The "Subset of Fields Wait Translation" flag, used by the MLS translation-subsetting mechanism to mark rows pending or excluded from translation.
  • DESCRIPTION — The translatable business text describing the condition line; this is the primary language-dependent payload of the table.
  • ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching (Edition-Based Redefinition), also part of the unique business-key index OKC_CONDITION_LINES_TL_U1 (ID, LANGUAGE, ZD_EDITION_NAME).
  • SECURITY_GROUP_ID — References FND_SECURITY_GROUPS and enforces the security-group partitioning model used by Contracts.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording row creation and modification metadata.

The surrogate primary key is (ID, LANGUAGE). The unique index OKC_CONDITION_LINES_TL_U1 (ID, LANGUAGE, ZD_EDITION_NAME) acts as the documented business-key candidate, adding the editioning discriminator required under online patching.

Common Use Cases and Queries

Typical usage resolves the translated description for a condition line joined to its base row while filtering to the runtime language. Oracle EBS applications obtain the session language through FND_GLOBAL or the MLS views (for example, the generated _VL view). A representative query is:

  • Database-column query: SELECT b.id, t.description FROM okc_condition_lines_b b, okc_condition_lines_tl t WHERE b.id = t.id AND t.language = USERENV('LANG').
  • Applications commonly query the MLS view (OKC_CONDITION_LINES_VL style) so that the language predicate is applied automatically, avoiding duplicate rows when multiple translations exist.
  • Reporting and extraction use cases filter by SOURCE_LANG and SFWT_FLAG for translation status dashboards, and by SECURITY_GROUP_ID where multi-org or security-group-restricted visibility is required.

Because the language column is part of the key, queries must constrain LANGUAGE; otherwise a single condition line returns one row per installed translation.

Related Objects

The following objects are most significant in relation to OKC_CONDITION_LINES_TL:

  • OKC_CONDITION_LINES_B — The base table holding non-translatable condition line data; joined on ID.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, supplying the security-group definition.
  • OKC_CONDITION_HEADERS — The parent condition header entity to which condition lines belong.
  • OKC_CONDITION_LINES_VL / _V — MLS views that expose the translated description for the session language.
  • FND_LANGUAGES — Provides the language codes referenced by the LANGUAGE and SOURCE_LANG columns.
  • OKC_CONTRACT_CONDITIONS — Higher-level contract structure that aggregates condition headers and lines.

These relationships establish OKC_CONDITION_LINES_TL as the language-dependent companion to the condition line base data within Contracts Core.