Search Results okc_statuses_tl




Overview
Explore in AI Chat

Overview

OKC_STATUSES_TL is the translatable (language-dependent) child table of OKC_STATUSES_B within the Oracle E-Business Suite Contracts Core (OKC) module. As stated in its documentation, it holds "translatable columns from OKC_STATUSES_B, as per MLS standards." In Oracle EBS, this table supplies the human-readable, localized text for contract status codes, enabling a single business record to be displayed in multiple installed languages. It is owned by the OKC schema and is classified as VALID across both 12.1.1 and 12.2.2.

The table forms part of the Multi-Lingual Support (MLS) pattern that Oracle applies to many code-and-meaning reference entities: OKC_STATUSES_B carries the language-independent structural attributes, while OKC_STATUSES_TL carries the language-dependent descriptive text keyed by CODE and LANGUAGE. From a Data Vault modeling perspective, the metadata's heuristic classification marks this object as a standalone entity. That classification is a modeling suggestion only; in practice the translation row is functionally a descriptive satellite, capturing the meaning and description associated with a contract status business key for a given language.

Key Information Stored

The documented schema exposes 13 physical columns. The most significant are:

  • CODE — the contract status identifier that links each translation row to its parent in OKC_STATUSES_B. It is part of the primary key and every unique index.
  • LANGUAGE — the installed Oracle language code for the translated text, also part of the primary key.
  • MEANING — the localized display name of the contract status, used throughout the Contracts user interface and in LOVs.
  • DESCRIPTION — the localized longer descriptive text for the status.
  • SOURCE_LANG — the language from which the current translation was derived.
  • SFWT_FLAG — the "Seed/Flex/Whatever Translation" flag used by the MLS framework to track translation provenance.
  • ZD_EDITION_NAME — the editioning column supporting Online Patching in EBS 12.2.2.
  • SECURITY_GROUP_ID — the security grouping that scopes the row, with a documented foreign key to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO audit columns.

The surrogate primary key is OKC_STATUSES_TL_PK on (CODE, LANGUAGE). Two documented unique indexes act as business-key candidates: OKC_STATUSES_TL_U1 on (CODE, LANGUAGE, ZD_EDITION_NAME) and OKC_STATUSES_TL_U2 on (MEANING, LANGUAGE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage centers on resolving a stored status code into a user-facing label for reports, concurrent programs, and BI Publisher layouts. A join to the base table is required to retrieve language-independent attributes:

  • Status lookup in a specific language: SELECT b.code, t.meaning, t.description FROM okc_statuses_b b, okc_statuses_tl t WHERE b.code = t.code AND t.language = USERENV('LANG').
  • All installed translations for one status: filter on t.code = :status_code to audit coverage across languages.
  • Missing-translation report: compare OKC_STATUSES_TL rows against the set of installed languages to detect statuses lacking localized MEANING text.
  • Change tracking: query LAST_UPDATED_BY / LAST_UPDATE_DATE on OKC_STATUSES_TL to review recent translation maintenance, particularly around patching cycles.

Note the editioning column ZD_EDITION_NAME in 12.2.2; report queries should include it or rely on the editioning views that surround these tables to avoid duplicate or stale rows.

Related Objects

  • OKC_STATUSES_B — the base (language-independent) table; join on CODE. This is the direct parent supplying the structural record.
  • FND_SECURITY_GROUPS — referenced via the documented foreign key on SECURITY_GROUP_ID, which governs row-level access to the translation.
  • OKC_STATUSES_VL — the MLS view that joins the _B and _TL tables into a single language-filtered row set; most application and reporting code queries this view rather than the base tables directly.
  • OKC_STATUSES_TL_PK / OKC_STATUSES_TL_U1 / OKC_STATUSES_TL_U2 — the primary key and unique indexes enforcing uniqueness of CODE+LANGUAGE and their editioning variants.
  • OKC_CONTRACTS / OKC_CONTRACTS_ALL — contract headers that carry status codes resolved through OKC_STATUSES_B and this translation table.
  • FND_LANGUAGES — supplies the installed LANGUAGE values and their native names used when presenting translations.
  • OKC_STATUSES_TL_S (sequence) or the _B table's key management — where documented, supports surrogate key generation for new status definitions.

Because the SECURITY_GROUP_ID linkage scopes access, any reporting solution should respect the security-group filter in conjunction with the language filter to produce results consistent with the Contracts application's own behavior.