Search Results okc_articles_v




Overview
Explore in AI Chat

Overview

OKC_ARTICLES_V is a reporting and integration view in the Oracle E-Business Suite Contracts Core (OKC) module, owned by the APPS schema and marked VALID in both 12.1.1 and 12.2.2. It presents a consolidated, denormalized picture of contract articles (clauses, provisions, and boilerplate text) by joining the master article header record to its individual versions. The view answers the fundamental business question of "what does this article say, in which language, and at which version" without requiring callers to navigate the parent/child relationship between the two underlying tables themselves.

Because the repository lists OKC_ARTICLES_V as a standard APPS view over documented ETRM base objects, it is a supported read interface for custom reports, Oracle Business Intelligence extracts, and integration programs that need article content. It is not intended as a maintenance path; DML against contract articles should continue to flow through the Contracts Core APIs rather than through this view. Consumers searching on article_language, for example, will find that attribute exposed directly at the view level rather than buried in the header table.

Underlying Base Objects

The view text defines an inner join between two documented base objects:

  • OKC_ARTICLES_ALL (alias AA) — the article header table, holding the article identity, organization, language, type, intent, and the "standard article" indicator. The _ALL suffix confirms it is partitioned by operating unit through ORG_ID, which is why ORG_ID must always be constrained in multi-org queries.
  • OKC_ARTICLE_VERSIONS (alias AV) — the version child table, holding the actual clause text plus version numbering, status, effective dates, approval metadata, translated flag, and the DFF attribute columns 1 through 15.

The join predicate is AA.ARTICLE_ID = AV.ARTICLE_ID, so a single article with multiple versions produces one row per version. Callers must therefore decide whether they want the full version history or only the currently effective row before aggregating. In the 12.2.2 ETRM metadata both base objects are documented as synonyms owned by APPS.

Key Columns

Frequently referenced columns include:

Common Use Cases and Queries

Typical scenarios include clause-library audits by language, extraction of approved clause text for downstream document generation, and reconciliation of article versions across operating units.

Listing articles for a given language and operating unit:

SELECT article_id, article_number, article_title, article_language, article_type
FROM   okc_articles_v
WHERE  org_id = :p_org_id
AND    article_language = 'US';

Retrieving the currently effective version of an article:

SELECT article_number, article_version_number, article_status,
       date_approved, article_text
FROM   okc_articles_v
WHERE  article_id = :p_article_id
AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1)
AND    article_status = 'APPROVED';

Counting versions per article to detect clauses with excessive revision history:

SELECT article_id, article_number, COUNT(article_version_id) versions
FROM   okc_articles_v
GROUP  BY article_id, article_number
HAVING COUNT(article_version_id) > 5;

Because the view performs no filtering of its own, every query should constrain ORG_ID and, where only current language is required, ARTICLE_LANGUAGE and TRANSLATED_YN to avoid returning stale or duplicated version rows.