Results for “okc_std_articles_tl”

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

Overview

OKC_STD_ARTICLES_TL is a translatable (TL) table within the OKC — Contracts Core product of Oracle E-Business Suite, present in both EBS 12.1.1 and 12.2.2. It stores the multi-language-support (MLS) translated values for the columns that are marked translatable in its base table, OKC_STD_ARTICLES_B, following Oracle's standard MLS design pattern. In practice, the TL table contains the language-dependent descriptive text — most notably the article NAME — for each standard articles record defined in the base table, while language-independent attributes remain in OKC_STD_ARTICLES_B.

The table belongs to the OKC schema and is a permanent, valid database object with 11 documented columns. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone; in Data Vault terms this suggests treating the table either as a hub-adjacent reference entity or, more appropriately, as a satellite holding descriptive/translatable attributes keyed to the base article record. This is a modeling suggestion rather than a formal classification, and any warehouse design should reconcile it with the base table relationship.

Key Information Stored

The table uses a composite primary key, OKC_STD_ARTICLES_TL_PK (ID, LANGUAGE), which combines the surrogate identifier inherited from the base table with the language code. The ID column is effectively a foreign-key-style link back to the corresponding row in OKC_STD_ARTICLES_B, while LANGUAGE discriminates the translation. The most significant columns are:

• ID — Identifier linking the translated row to its base-table parent record.
• LANGUAGE — The language code for the translated row; part of the composite primary key.
• SOURCE_LANG — The source language from which the translation was derived, per MLS conventions.
• SFWT_FLAG — Standard "Seed/Flag" indicator used by Oracle's MLS translation tooling to track translated versus seeded text.
• NAME — The translated name of the standard article; a documented business-key candidate through unique index OKC_STD_ARTICLES_TL_U2 (NAME, LANGUAGE).
• CREATED_BY, CREATION_DATE — Standard WHO-column audit stamps recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — WHO-column audit stamps for the most recent modification.
• LAST_UPDATE_LOGIN — The login/user session associated with the last update.
• SECURITY_GROUP_ID — The security grouping, which references FND_SECURITY_GROUPS.

Two unique indexes are documented: OKC_STD_ARTICLES_TL_U1 (ID, LANGUAGE), which mirrors the primary key, and OKC_STD_ARTICLES_TL_U2 (NAME, LANGUAGE), a business-key candidate enforcing uniqueness of the translated name per language.

Common Use Cases and Queries

Because this is an MLS table, the primary use case is retrieving display text in the user's session language. The common query pattern joins the base table to the TL table on the identifier column, filtering by language, typically via the FND_GLOBAL.LANGUAGE or a direct language literal.

SELECT b.id, t.name, t.language
FROM   okc_std_articles_b b,
       okc_std_articles_tl t
WHERE  b.id = t.id
AND    t.language = USERENV('LANG');

Reporting scenarios include producing multilingual catalogs of standard contract articles, auditing which articles have been translated into which languages, and validating translation completeness by comparing the base-table record count against the number of TL rows per language. Data-migration and localization projects use the SOURCE_LANG and SFWT_FLAG columns to identify untranslated or seeded content. Security-conscious reports join to FND_SECURITY_GROUPS through SECURITY_GROUP_ID to restrict results by operating unit or security group.

Related Objects

The following objects are the most significant dependencies and related entities:

• OKC_STD_ARTICLES_B — The base table; joined to the TL table on ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; used to enforce security-group-level access.
• FND_LANGUAGES — Defines the valid values for LANGUAGE.
• OKC_STD_ARTICLES_TL_PK — The composite primary key constraint on ID, LANGUAGE.
• OKC_STD_ARTICLES_TL_U1 / U2 — Unique indexes supporting business-key and name uniqueness.
• OKC_STD_ARTICLES_VL — The typical MLS view exposing both base and translated columns.
• Contract authoring and standard-article APIs in OKC that consume the translated article text.