Search Results okc_k_articles_tl_pk




Overview

OKC_K_ARTICLES_TL is a translatable (TL) table in the OKC schema, the Contracts Core module of Oracle E-Business Suite. It stores the language-dependent, multi-lingual description columns corresponding to the base table OKC_K_ARTICLES_B, following Oracle's Multi-Lingual Support (MLS) architecture. Each row in the _TL table pairs with a single base-language row in OKC_K_ARTICLES_B, keyed by the parent entity ID and the LANGUAGE code.

The ETRM metadata for this object is explicit: the table is obsolete, obsoleted in release 11.5.10. Although the record still shows status VALID in the 12.1.1 / 12.2.2 data dictionary, the object exists for backward compatibility with pre-11.5.10 code paths and any dormant historical data. No functional Contracts application logic in a current 12.x instance is expected to write to or read from it for new business processing.

Following the Data Vault classification heuristic mined from the foreign key structure (the table is marked standalone with no inbound dependencies from other tables), OKC_K_ARTICLES_TL is best modeled as a satellite on the OKC_K_ARTICLES_B hub. Its role in that model is to hold the descriptive, context-sensitive attributes associated with a contract article key, rather than defining the key itself or connecting separate business concepts.

Key Information Stored

The physical schema documents 16 columns. The most significant include:

The primary key (ID, LANGUAGE) is the surrogate-plus-locale identity; the unique index OKC_K_ARTICLES_TL_U1 confirms the same pair as the documented business-key candidate. The ID column is the foreign-key bridge to the base table, but the metadata does not list any inbound foreign key on this table — it is a leaf satellite in the mined model.

Common Use Cases and Queries

Because the object was obsoleted in 11.5.10, practical use in a 12.1.1 or 12.2.2 environment is limited to three areas: migration validation, historical reporting, and impact analysis.

A typical pattern joins the TL satellite to the current base table by ID and LANGUAGE:

  • SELECT b.id, t.language, t.name, t.comments FROM okc_k_articles_b b, okc_k_articles_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
  • Row-count reconciliation between OKC_K_ARTICLES_B and OKC_K_ARTICLES_TL, grouped by LANGUAGE, to confirm whether residual translated rows remain after upgrade.
  • Orphan detection: rows in OKC_K_ARTICLES_TL whose ID has no match in OKC_K_ARTICLES_B, indicating historical artifacts.
  • SECURITY_GROUP_ID filtering to respect data-group boundaries in multi-org reporting.

New development should not target this table; use the current MLS structure exposed by the Contracts entity APIs instead.

Related Objects

  • OKC_K_ARTICLES_B — The base (non-translated) table; join on ID = ID. Primary structural parent.
  • OKC_K_ARTICLES_VL — The view that unions _B and _TL and is the primary consumer of this satellite.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, enforcing data-group security.
  • OKC_K_ARTICLES — Interface/API layer historically reading the translated rows.
  • FND_LANGUAGES — Supplies LANGUAGE values used in the ML join.
  • OKC_K_ARTICLE_VERSIONS (dormant) — Versioning constructs that consumed article text, including translated TEXT.

Given the obsolete status, no ETRM-documented inbound foreign keys exist; the only documented foreign key is from this table's SECURITY_GROUP_ID to FND_SECURITY_GROUPS.