Search Results article_name




Overview
Explore in AI Chat

Overview

APPS.OKC_TERMS_DOC_LATEST_ART_V is a reporting and integration view in the Oracle E-Business Suite ETRM (Enterprise Contracts) module. It exposes article-level data for standard contract terms documents, joining the article definition layer to the term-version layer and resolving descriptive attributes through the OKC_TERMS_UTIL_PVT utility package. The view is defined over the base objects OKC_K_ARTICLES_B and OKC_ARTICLES_ALL, and its derived columns are populated by function calls into OKC_TERMS_UTIL_PVT. It does not store data; it project a curated, denormalized presentation of article and version metadata suitable for reporting, personalization, and interface extraction in both 12.1.1 and 12.2.2 releases.

The distinguishing characteristic of this view is its focus on the latest article version. For each article row it returns the current version number and version identifier alongside the article and section identifiers, enabling consumers to report on the effective wording of a terms document without navigating multiple version rows themselves. The hardcoded literal 'ARTICLE' in the OBJECT_TYPE column confirms its role within a family of term-object views that share a common projection shape.

Underlying Base Objects

The view is documented as referencing three base objects:

  • OKC_K_ARTICLES_B (alias k) — the primary driving table. It supplies the article identifier (SAV_SAE_ID), the article version identifier (ARTICLE_VERSION_ID), the section identifier (SCN_ID), the document type and document id, the object version number, and the original system reference columns. Rows are restricted to those where ARTICLE_VERSION_ID is not null.
  • OKC_ARTICLES_ALL (alias art) — joined on k.sav_sae_id = art.article_id and filtered by art.standard_yn = 'Y'. This constrains the result set to standard (seeded) articles rather than user-defined or nonstandard ones.
  • OKC_TERMS_UTIL_PVT — a PL/SQL package whose functions resolve the descriptive attributes: article name, section label, version number, the latest version number and id, local article id, and adoption type. Because these are function calls, the view is not a pure relational join; each row incurs the cost of these lookups.

In both 12.1.1 and 12.2.2 these objects are exposed to APPS through synonyms, so the view resolves against the ETRM schema objects as documented.

Key Columns

Common Use Cases and Queries

This view is typically used to report on the current wording of standard articles within a terms document, to reconcile article versions, and to drive downstream interfaces that require the latest effective version of each article.

Report the latest version of each standard article for a given document:

  • SELECT article_name, section_label, article_version_number, latest_article_version_number, adoption_type FROM apps.okc_terms_doc_latest_art_v WHERE document_type = :p_doc_type AND document_id = :p_doc_id ORDER BY section_label, article_name;

Identify articles whose current row is not the latest version (stale versions):

  • SELECT article_id, article_name, article_version_number, latest_article_version_number FROM apps.okc_terms_doc_latest_art_v WHERE article_version_id <> latest_article_version_id;

Extract localized article names through the LOCAL_ARTICLE_ID for multilingual deployments, or filter by ORIG_SYSTEM_REFERENCE_CODE when loading articles from an external contract authoring system. Because the view relies on OKC_TERMS_UTIL_PVT function calls for most descriptive columns, queries that filter on ARTICLE_NAME or SECTION_LABEL cannot use index access; constrain first on the identifier columns (DOCUMENT_TYPE, DOCUMENT_ID, ARTICLE_ID) to limit the driving row set before applying descriptive predicates.