Search Results okc_articles_b




Overview
Explore in AI Chat

Overview

OKC_ART_NON_STANDARDS_V is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. It exposes a filtered, denormalized projection of contract article data, restricted specifically to non-standard articles. The view is defined over the OKC_ARTICLES_B table and related article definition and version tables, and its defining predicate ART.STANDARD_YN = 'N' ensures that only clauses or articles flagged as non-standard are returned.

Functionally, the view serves reporting and integration consumers that need to distinguish user-defined or negotiated article content from the pre-seeded standard clause library. Because it resolves description, display name, and article text from the version table and derives the article type from the article definition table, it presents a business-friendly record without requiring callers to join the underlying normalized structures. In embedded or downstream code paths that reference the Contracts Core article model, this view provides a stable, read-only surface for extracting non-standard article content associated with contract documents.

Underlying Base Objects

The ETRM documentation for 12.2.2 identifies three referenced base objects, all accessed through APPS synonyms:

The three-way inner join means a row is returned only where the article instance resolves to both a master definition and a version record, and where that master definition is marked non-standard. The literal NULL in the SFWT_FLAG column indicates a fixed placeholder rather than a value sourced from any base table.

Key Columns

  • ROW_ID — the ROWID of the OKC_K_ARTICLES_B row, useful for direct row addressing and update-by-rowid patterns.
  • ID — primary identifier of the contract article instance.
  • CHR_ID / CLE_ID / CAT_ID / DNZ_CHR_ID — contractual context: parent contract header, line, category, and the document/version header linkage.
  • SBT_CODE — the article type drawn from OKC_ARTICLES_ALL.ARTICLE_TYPE, allowing classification of non-standard articles by type.
  • NAME — derived using NVL(VERS.DISPLAY_NAME, ART.ARTICLE_TITLE), preferring the version-level display name and falling back to the master article title.
  • TEXT / COMMENTS — the article body (VERS.ARTICLE_TEXT) and description (VERS.ARTICLE_DESCRIPTION).
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and segments for the article instance.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include auditing negotiated (non-standard) clauses within a contract, reporting all non-standard articles by type across a contract portfolio, and feeding external document-generation or compliance systems with the effective article text.

List all non-standard articles for a contract:

SELECT id, chr_id, sbt_code, name, comments
FROM   apps.okc_art_non_standards_v
WHERE  chr_id = :p_chr_id;

Group non-standard articles by type:

SELECT sbt_code, COUNT(*) article_count
FROM   apps.okc_art_non_standards_v
GROUP  BY sbt_code
ORDER  BY article_count DESC;

Retrieve the effective text of a specific non-standard article:

SELECT name, text, comments, last_update_date
FROM   apps.okc_art_non_standards_v
WHERE  id = :p_article_id;

Because OKC_ARTICLES_ALL is a translated (TL/ALL) master structure, consumers should be aware that NAME and TEXT reflect the resolved version record at query time, and multilingual implementations should confirm the appropriate language context through the underlying article master.