Results for “sam_object_version_number”
2 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_KOL_STD_ART_LIB_V is a Contracts Core (OKC) reporting view that exposes the standard article library used by Oracle Contracts. It joins the master article definitions held in OKC_ARTICLES_ALL with their versioned content in OKC_ARTICLE_VERSIONS, then decorates those rows with lookup meanings sourced from FND_LOOKUPS for subject, article status, default section, provision, and intent. In Oracle EBS 12.1.1 and 12.2.2 the view serves as the canonical read-only window into reusable boilerplate clauses, terms, and conditions that can be attached to contract templates and authored contracts.
The view name embeds the "KOL" prefix common to Contracts Core library objects. Its principal role in reporting and integration is to provide a flattened, human-readable catalog of articles rather than the normalized, multi-table structure behind them. External systems, custom concurrent programs, and OBIEE/XML Publisher reports can consume this single view to list available clauses without joining the underlying base tables. The view is documented as not implemented in the reference database, meaning it is a seeded, upgrade-maintained object that may not appear in every environment depending on the patch level applied.
Underlying Base Objects
The view is defined over the following documented base objects:
- OKC_ARTICLES_ALL — the master article header table, aliased ART, filtered by STANDARD_YN = 'Y' so that only library-standard articles are returned.
- OKC_ARTICLE_VERSIONS — the versioned body table, aliased ARTV, providing article text, dates, status, and version number. Joined to ART on ARTICLE_ID and restricted to GLOBAL_YN = 'Y'.
- FND_LOOKUPS — referenced five times (aliases SM, TM, DSM, PM, IM) for the lookup types OKC_ARTICLE_STATUS, OKC_SUBJECT, OKC_ARTICLE_SECTION, OKC_ARTICLE_PROVISION, and OKC_ARTICLE_INTENT respectively. The section lookup is an outer join (DSM.LOOKUP_TYPE(+) with DSM.LOOKUP_CODE(+) = ARTV.DEFAULT_SECTION), allowing articles without a default section. Two packaged PL/SQL functions, OKC_STD_ARTICLE_PUB.USED_IN_CONTRACTS and OKC_STD_ARTICLE_PUB.LATEST_OR_FUTURE_RELEASE, are also invoked inline as columns.
A notable predicate applies DECODE to ARTICLE_STATUS: an APPROVED version whose end date has passed relative to SYSDATE is reported as EXPIRED. Subject, status, section, provision, and intent lookups are matched on both LOOKUP_TYPE and LOOKUP_CODE, meaning the view silently drops rows whose lookup values are not yet defined.
Key Columns
- ID — ARTICLE_ID of the standard article.
- NAME — ARTICLE_TITLE of the article.
- SUBJECT — MEANING from the OKC_SUBJECT lookup, giving the business subject classification.
- SBT_CODE / SAT_CODE — ARTICLE_TYPE values mapped to the subject and article-type codes.
- SAE_OBJECT_VERSION_NUMBER, SAV_RELEASE, SAM_OBJECT_VERSION_NUMBER, SAV_OBJECT_VERSION_NUMBER — all mirror ARTICLE_VERSION_NUMBER for use by different integration mappings.
- START_DATE / END_DATE — effective window of the article version.
- SHORT_DESCRIPTION — ARTICLE_DESCRIPTION from the version row.
- ARTICLE_SET — ARTICLE_INTENT, the intent code the article belongs to.
- TEXT — full CLOB article body.
- SHORT_TEXT — DBMS_LOB.SUBSTR of the article text truncated to 240 characters and suffixed with ' ....'; this is the column most often retrieved when a user searches for "short_text". The concatenation returns the leading portion of the article body suitable for list-of-values and summary displays without transmitting the entire CLOB.
- USED_IN_CONTRACTS — function result indicating whether the article version is referenced by any contract.
- LATEST_RELEASE — function result flagging whether the version is the latest or a future release.
Common Use Cases and Queries
Typical uses include populating article-selection lists of values, locating reusable clauses by subject, auditing which library articles are still in force, and identifying articles already consumed by contracts. A representative query retrieving short text for approved, unexpired articles is:
SELECT ID, NAME, SUBJECT, START_DATE, SHORT_TEXT FROM OKC_KOL_STD_ART_LIB_V WHERE SUBJECT = 'TERMS' AND (END_DATE IS NULL OR END_DATE > SYSDATE);
To find standard articles never cited in a contract, filter on the packaged function: SELECT ID, NAME, SHORT_TEXT FROM OKC_KOL_STD_ART_LIB_V WHERE USED_IN_CONTRACTS = 'N'; Because SHORT_TEXT is derived via DBMS_LOB.SUBSTR, it is safe to concatenate and compare in SQL, but the full TEXT column should be treated as a LOB and fetched only when required.
-
View: OKC_KOL_STD_ART_LIB_V 12.2.2
Not implemented in this database·Explore OKC module →
-
View: OKC_KOL_STD_ART_LIB_V 12.1.1
Not implemented in this database·Explore OKC module →