Results for “okc_article_intent”

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

Overview

The view OKC_KOL_STD_ART_LATEST_REL_V belongs to the OKC — Contracts Core module of Oracle E-Business Suite and exposes standard contract clause (article) records together with their latest released versions. The view acts as a reporting and integration access point for consumers that need to retrieve only the most current, globally enabled, standard article definitions rather than the full transactional article history held in the base tables.

The view is defined with an explicit SELECT against the article and article version tables and joins several FND_LOOKUPS instances to translate coded values into validated lookup meanings. A noteworthy aspect of the definition is the status derivation logic driven by the OKC_ARTICLE_STATUS lookup type. When a version holds the status APPROVED, the view compares the effective end date against the system date; an approved article whose end date has already passed is surfaced as EXPIRED rather than APPROVED. This dynamic evaluation means the view returns a status that reflects the current point in time, rather than the raw stored value. The view therefore plays a role similar to a semantic or business view layer over the physical OKC article model.

Underlying Base Objects

The ETRM metadata lists no separately documented base objects, but the view text identifies its underlying tables directly. The primary sources are OKC_ARTICLES_ALL, which holds the standard article header, and OKC_ARTICLE_VERSIONS, which holds each version of a given article. Additional lookup context is drawn from five aliased instances of FND_LOOKUPS: SM for OKC_ARTICLE_STATUS, TM for OKC_SUBJECT (article type), DSM for OKC_ARTICLE_SECTION, PM for OKC_ARTICLE_PROVISION, and IM for OKC_ARTICLE_INTENT.

The join conditions enforce several restrictions that define the view's scope. Only rows where STANDARD_YN = 'Y' in OKC_ARTICLES_ALL are eligible, so non-standard or user-defined clauses are excluded. Only versions where GLOBAL_YN = 'Y' are included. A call to the function OKC_STD_ARTICLE_PUB.LATEST_RELEASE, passing the article ID and version number, must evaluate to 'Y', which restricts output to the latest release of each standard article. Lookup joins are largely inner joins, meaning rows missing valid lookup codes for article type, status, provision, or intent are filtered out; the section lookup (DSM) is an outer join, reflecting that the default section may be null.

Key Columns

• ID — maps to ART.ARTICLE_ID and uniquely identifies the standard article header.
• NAME — maps to ART.ARTICLE_TITLE, the display title of the article.
• SAV_RELEASE — maps to ARTV.ARTICLE_VERSION_NUMBER and identifies the released version of the standard article.
• START_DATE — the effective start date of the article version.
• ARTICLE_INTENT — maps to ART.ARTICLE_INTENT and is validated against the OKC_ARTICLE_INTENT lookup type.

Although not projected in the column list, the WHERE clause references end date (END_DATE), article type, status, default section, and provision flag, which govern both filtering and the derived status value.

Common Use Cases and Queries

The most frequent scenario is enumerating the currently released standard articles and their effective dates, for example to populate a clause library, an LOV, or an integration feed. A typical query is:

SELECT id, name, sav_release, start_date, article_intent FROM okc_kol_std_art_latest_rel_v;

Because the view already derives status, it can be used to surface articles that have transitioned from APPROVED to EXPIRED without additional logic. Other uses include validating that a chosen standard article has a current global release, auditing the set of clauses available to contract authors, and correlating article intent or type values with their lookup meanings for reporting. Since the view reflects live system dates and lookup definitions, results can change as data is maintained, and it should be treated as a read-only reporting object rather than a target for DML.