Results for “okc_article_section”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OKC_ARTICLES_GLOBAL_V is a reporting view in the Oracle E-Business Suite Contracts (OKC) module, exposed under the APPS schema. It presents a flattened, denormalized projection of contract clause and article content that has been flagged as "global" and "standard," making it suitable for cross-operating-unit reporting, template governance, and integration feeds. Rather than requiring callers to join the article header, its versioned body, and multiple lookup tables manually, the view assembles the clause title, number, type, version, lifecycle status, global flag, and full text into a single query surface.

The view is significant for the search term okc_article_status because it applies a derived-status transformation rather than returning the raw stored column. In Oracle Contracts, article versions progress through statuses such as DRAFT, APPROVED, and EXPIRED. The view's DECODE logic recalculates status at query time: any version stored as APPROVED whose end date has passed is dynamically reported as EXPIRED. This means the STATUS column returned by the view always reflects the article's effective status as of the current system date, not the persisted value.

Underlying Base Objects

The view is defined over three documented base objects:

• OKC_ARTICLES_ALL (SYNONYM) — the article header table, supplying title, number, type, intent, and ORG_ID. The view restricts this set with art.standard_yn = 'Y'.
• OKC_ARTICLE_VERSIONS (SYNONYM) — the versioned article body, supplying version number, status, article text, description, start/end dates, default section, and the global and provision flags. It joins to the header on ARTICLE_ID.
• OKC_LOOKUPS_V (VIEW) — referenced six times with aliases SM, TM, DSM, PM, IM, GM, to translate coded values into user-facing meanings via lookup types OKC_ARTICLE_STATUS, OKC_SUBJECT, OKC_ARTICLE_SECTION, OKC_ARTICLE_PROVISION, OKC_ARTICLE_INTENT, and OKC_YN.

Only the status and subject lookups use outer-join semantics; the remaining lookup joins are mandatory, so a version lacking a valid global flag or provision code will not appear in the result set.

Key Columns

• ARTICLE_STATUS — the dynamically derived status (e.g., APPROVED, EXPIRED); the primary column for okc_article_status queries.
• ARTICLE_TITLE / ARTICLE_NUMBER / ARTICLE_TYPE — identifying attributes of the clause, with the type meaning supplied by TM.MEANING.
• ARTICLE_VERSION_NUMBER / ARTICLE_VERSION_ID — the specific version row and its surrogate key.
• ARTICLE_TEXT / ARTICLE_DESCRIPTION — the clause body and its descriptive summary.
• GLOBAL_YN / GLOBAL meaning — indicates the article is available across business units.
• START_DATE / END_DATE — the validity window used by the EXPIRED derivation.
• ORG_ID / ARTICLE_ID — operating unit and header keys for joins and security filtering.
• MEANING columns — decoded labels for subject, status, section, provision, intent, and global flag.

Common Use Cases and Queries

Typical scenarios include auditing active global clauses, identifying expired approvals, and feeding clause libraries into external repositories.

SELECT article_number, article_title, meaning_status, article_version_number,
       start_date, end_date
FROM   apps.okc_articles_global_v
WHERE  article_status = 'EXPIRED';

SELECT article_id, article_version_id, article_title
FROM   apps.okc_articles_global_v
WHERE  article_status = 'APPROVED'
AND   (end_date IS NULL OR end_date >= TRUNC(SYSDATE));

Because status is computed at runtime, any query filtering on okc_article_status must reference the view's STATUS column rather than the base table to obtain accurate expiry results.