Results for “article_language”

50+ results




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

Overview

OKC_ARTICLES_ALL is the core clause repository table within the Oracle EBS Contracts Core (OKC) module. It stores every clause (also called an "article" in the data model) available to an operating unit, spanning both standard clauses maintained in the enterprise clause library and non-standard, ad hoc clauses authored for a specific contract document or template. The table replaces the earlier OKC_ARTICLES object and is the authoritative source from which contract terms are assembled, versioned, and rendered. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the OKC schema, is fully valid, and exposes 38 documented columns.

From a Data Vault modeling perspective, the foreign-key topology suggests OKC_ARTICLES_ALL is hub-leaning: ARTICLE_ID is a durable, non-repeating business key, while descriptive and contextual attributes (titles, languages, status flags) behave satellite-like. Practitioners designing downstream marts should treat it as a hub with associated satellites and links rather than as a transactional fact.

Key Information Stored

The surrogate primary key is ARTICLE_ID, enforced by OKC_ARTICLES_ALL_PK1 and mirrored by the unique index OKC_ARTICLES_ALL_U1, making it the strongest business-key candidate. Column-level highlights include:

Common Use Cases and Queries

Typical reporting needs include listing all standard clauses for an operating unit, locating clauses by language or title, and auditing recently modified clause library content.

  • Operating-unit clause inventory: SELECT article_id, article_number, article_title FROM okc_articles_all WHERE org_id = :p_org_id AND standard_yn = 'Y';
  • Multilingual clause lookup joining FND_LANGUAGES on ARTICLE_LANGUAGE.
  • Audit reporting using CREATION_DATE / LAST_UPDATE_DATE ranges and CREATED_BY / LAST_UPDATED_BY.
  • Dependency discovery — joining to OKC_K_ARTICLES_B or OKC_ARTICLE_VERSIONS on ARTICLE_ID to trace where a clause is consumed.

Because ORG_ID is enforced, queries should always be filtered by operating unit in multi-org environments, and standard_yn combined with org_id is the primary filter pair used by the clause library UI.

Related Objects