Search Results okc_std_articles_v




Overview
Explore in AI Chat

Overview

OKC_STD_ARTICLES_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite contracts core (OKC). It is documented as a backward-compatible view for the OKC_ARTICLES_ALL table and resides in the APPS schema, with a status of VALID. The view is designed to present standard contract articles — reusable, centrally maintained clause text — in the legacy column layout that older OKC code, reports, and integrations expect. The view exists because the underlying article storage model was reorganized around OKC_ARTICLES_ALL; rather than force every dependent object to be rewritten, Oracle exposes the legacy row shape through this view. A defining characteristic of the view is its filter: it returns only rows where STANDARD_YN = 'Y', so it exclusively surfaces standard articles rather than one-off, locally authored clauses. The view also applies an access check through MO_GLOBAL.CHECK_ACCESS so that only articles accessible to the current operating unit context are returned. Because the view exposes a ROWID-based ROW_ID and an ID alias, the output closely resembles the pre-consolidation OKC_ARTICLES structure, which is precisely the shape used by legacy forms, concurrent programs, and interface extracts.

Underlying Base Objects

The view is defined over the OKC_ARTICLES_ALL synonym, aliased as ART, which supplies all projected columns. It also references the OKC_ARTICLES synonym in the WHERE clause, the OKC_ARTICLE_ADOPTIONS and OKC_ARTICLE_VERSIONS synonyms through a correlated UNION ALL subquery, and the MO_GLOBAL package for the access check. The documented base references are OKC_ARTICLES_ALL, OKC_ARTICLES, OKC_ARTICLE_ADOPTIONS, OKC_ARTICLE_VERSIONS (all synonyms), and MO_GLOBAL (package). The subquery establishes visibility in two ways: directly, when a matching standard row exists in OKC_ARTICLES, and indirectly, when the article has been adopted by a local organization (via OKC_ARTICLE_ADOPTIONS joined to OKC_ARTICLE_VERSIONS on GLOBAL_ARTICLE_VERSION_ID = ARTICLE_VERSION_ID) and MO_GLOBAL.CHECK_ACCESS returns 'Y' for that adoption's LOCAL_ORG_ID. This dual path lets globally maintained standard articles flow to operating units that have adopted them, while still filtering out articles outside the user's access. In effect, the view is a security- and standardization-filtered projection of the global article repository.

Key Columns

Common Use Cases and Queries

Typical uses include legacy report queries, migration or extract scripts that must reproduce the pre-consolidation article layout, and diagnostics of which standard articles are visible in the current operating unit context.

SELECT id, name, sbt_code, last_update_date
FROM   apps.okc_std_articles_v
WHERE  sbt_code = :p_article_type
ORDER  BY name;

Because visibility depends on MO_GLOBAL.CHECK_ACCESS, initialize the operating unit context before querying:

BEGIN
  mo_global.init('OKC');
  mo_global.set_policy_context('S', :p_org_id);
END;

SELECT id, name
FROM   apps.okc_std_articles_v;

For adoption tracing, join ID back to OKC_ARTICLES_ALL or OKC_ARTICLE_VERSIONS on ARTICLE_ID. Note that STANDARD_YN = 'Y' and the access-check predicate are enforced internally; callers cannot retrieve non-standard or inaccessible articles through this view.