Search Results standard_yn




Overview
Explore in AI Chat

Overview

The APPS.OKC_STD_ARTICLES_V view is a standard Oracle E-Business Suite 12.1.1 / 12.2.2 reporting object within the Oracle Knowledge and Contracts (OKC) / Enterprise Contracts module of ETRM. It presents the subset of contract terms-library articles that are flagged as standard, that is, records whose STANDARD_YN attribute equals 'Y'. Because standard articles form the reusable clause library that drives contract authoring, this view serves as the canonical read-only interface for discovering which reusable articles are globally defined and accessible to the current operating unit. The view is designed for report generation, integration extracts, and inquiry forms rather than transactional maintenance; it exposes a renamed, denormalized projection of the underlying article table without exposing the full physical column set. Notably, the view does not expose STANDARD_YN itself as a projected column — the filter is applied internally in the WHERE clause, so the column is used for selection but not returned in the result set.

Underlying Base Objects

The view is defined over the synonym OKC_ARTICLES_ALL (aliased ART) and references, through a correlated EXISTS subquery, the synonyms OKC_ARTICLES, OKC_ARTICLE_ADOPTIONS, and OKC_ARTICLE_VERSIONS, together with the package MO_GLOBAL. The primary driving record comes from OKC_ARTICLES_ALL, which stores the article header including the STANDARD_YN standard-article flag, the ARTICLE_ID primary key, and the descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15. The accessibility predicate is enforced by MO_GLOBAL.CHECK_ACCESS(ADP.LOCAL_ORG_ID) = 'Y', which applies multi-org security so that only articles whose adoptions belong to an organization accessible to the current session are returned. Article adoptions link a global article version to a local operating unit through GLOBAL_ARTICLE_VERSION_ID, resolved against OKC_ARTICLE_VERSIONS on ARTICLE_VERSION_ID and ARTICLE_ID. The UNION ALL within the subquery deliberately admits rows matched either by the direct standard-article criterion or by the adoption/version path, avoiding duplicate evaluation while preserving the EXISTS semantics.

Key Columns

  • ROW_ID — the physical ROWID of the underlying OKC_ARTICLES_ALL row, used by Oracle Forms for row identification.
  • ID — the ARTICLE_ID, the primary key of the article.
  • OBJECT_VERSION_NUMBER — the optimistic locking / concurrency control column.
  • SFWT_FLAG — a hard-coded literal 'N', a descriptive flexfield/workflow flag retained for interface compatibility.
  • SBT_CODE — mapped from ARTICLE_TYPE, the article type classification code.
  • NAME — mapped from ARTICLE_TITLE, the user-facing article name.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values carried through from the base table.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include identifying the standard clause library available to a given responsibility, validating article loads, and feeding downstream contract-authoring reports. Because STANDARD_YN is not projected, callers cannot re-filter on it and must instead join OKC_ARTICLES_ALL directly when the raw flag is required. A representative query:

SELECT id, name, sbt_code
FROM   apps.okc_std_articles_v
WHERE  UPPER(name) LIKE '%LIABILITY%';

To correlate a standard article with its adopted local versions, join the view back to OKC_ARTICLE_VERSIONS on ARTICLE_ID. Practitioners should also confirm that MO_GLOBAL is initialized for the session; otherwise the multi-org access predicate returns no rows even though matching standard articles exist. This behavior is the most frequent cause of apparently missing data and is the key operational caveat when reporting from this view.