Search Results okc_k_articles_tl_u1




Overview

OKC.OKC_K_ARTICLES_TL is the translation (TL) table for contract articles in Oracle E-Business Suite, owned by the OKC (Contracts Core) schema. In the Oracle Contracts architecture, articles represent the reusable textual clauses and terms that are assembled into contract templates and contract documents. The base table OKC_K_ARTICLES holds the language-independent article definition, while OKC_K_ARTICLES_TL stores the language-specific attributes — the article name, descriptive text, comments, and variation description — for each installed language. This design follows the standard Oracle Multi-Lingual Support (MLS) pattern, in which translatable columns are held in a companion _TL table keyed by both the entity identifier and a LANGUAGE code.

Within Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID, resides in the APPS_TS_TX_DATA tablespace, and is classified for Data Vault modeling purposes as a standalone satellite: it carries descriptive, versioned attributes about an article entity, has a composite primary key rather than a pure business key, and has no dependent downstream tables. This classification is a heuristic modeling suggestion derived from the foreign-key structure, which shows only a single inbound reference from FND_SECURITY_GROUPS (SECURITY_GROUP_ID). Oracle marks the object as internal use only; direct DML should be performed exclusively through supported Contracts APIs and concurrent programs.

Key Information Stored

The table contains 16 documented columns. The most significant are:

  • ID (NUMBER, mandatory) — Surrogate primary key for the article. The documented comment states it is generated using the sys_guid() database function. It joins back to the base OKC_K_ARTICLES table.
  • LANGUAGE (VARCHAR2(12), mandatory) — Standard MLS column identifying the language of the row. Together with ID it forms the primary key OKC_K_ARTICLES_TL_PK (ID, LANGUAGE).
  • SOURCE_LANG (VARCHAR2(12)) — Standard MLS column recording the language from which the row was originally derived.
  • SFWT_FLAG (VARCHAR2) — Indicates that a value was changed in another language; the metadata notes this is not fully implemented in 11i.
  • OBJECT_VERSION_NUMBER (NUMBER) — Sequential number set to 1 on insert and incremented on update, used by APIs to detect concurrent modification through optimistic locking.
  • NAME (VARCHAR2(150)) — The article name, used for non-standard articles.
  • TEXT (CLOB(4000)) — The article body text, used for non-standard articles. Stored as a LOB with its own unique LOB index (SYS_IL0000085276C00009$$).
  • COMMENTS (VARCHAR2(1995)) — User-entered comment associated with the article.
  • VARIATION_DESCRIPTION (VARCHAR2(240)) — Standard description of the article variation.
  • SAV_SAV_RELEASE (VARCHAR2(150)) — Version or release of the article; indexed by the non-unique index OKC_K_ARTICLES_TL_N1.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns capturing audit and accountability information.
  • SECURITY_GROUP_ID (NUMBER) — Used in hosted environments; references FND_SECURITY_GROUPS.

The unique index OKC_K_ARTICLES_TL_U1 (ID, LANGUAGE) is the business-key candidate for this table, mirroring the primary key definition.

Common Use Cases and Queries

Typical reporting scenarios include retrieving the translated article name and text for a given language, auditing article versions, and investigating API update conflicts via OBJECT_VERSION_NUMBER. A representative query returning translation rows for a specific language follows:

  • SELECT id, language, name, variation_description, sav_sav_release FROM okc.okc_k_articles_tl WHERE language = USERENV('LANG') AND sav_sav_release = :release;
  • To find all translations for one article: SELECT language, name FROM okc.okc_k_articles_tl WHERE id = :article_id ORDER BY language;
  • To detect rows modified since a point in time for auditing: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • To fetch full article text for non-standard articles, select the TEXT CLOB for the appropriate LANGUAGE row.

Because this is an MLS table, care must be exercised to filter on LANGUAGE; failing to do so returns one row per installed language.

Related Objects

  • OKC.OKC_K_ARTICLES — Base, language-independent article table; join on OKC_K_ARTICLES.ID = OKC_K_ARTICLES_TL.ID.
  • OKC.OKC_K_ARTICLE_VERSIONS — Version history associated with articles, keyed by the article ID.
  • OKC.OKC_ARTICLES — Related article definition object used elsewhere in the Contracts data model.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for hosted-environment security grouping.
  • OKC_K_ARTICLES_TL_U1 — Unique index on (ID, LANGUAGE) enforcing the business-key candidate.
  • OKC_K_ARTICLES_TL_N1 — Non-unique index on SAV_SAV_RELEASE, supporting release-based lookups.
  • Standard Contracts APIs (for example, article definition and template APIs) serve as the supported access path for inserting and updating rows in this table.