Results for “cat_type”

50+ results




Overview
Explore in AI Chat

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

Overview

OKC_K_ARTICLES_HV is an APPS-owned, VALID database view within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the history view for the OKC_K_ARTICLES entity, exposing the full temporal record of contract article definitions and their versions across Oracle EBS 12.1.1 and 12.2.2. The "_HV" suffix denotes a history view built over the "_BH" (history) base table, OKC_K_ARTICLES_BH, whose rows are themselves populated by the Contracts Core history/audit infrastructure (typically via a TCA-style history package) whenever article records are inserted, updated, or deleted.

From a reporting and integration standpoint, OKC_K_ARTICLES_HV provides point-in-time and change-tracked access to contract terms, boilerplate clauses, and article text without requiring consumers to reconstruct version chains manually. Because it is a view rather than a table, it participates transparently in the standard EBS security and org-access model and can be queried by BI Publisher reports, OAF/ADF pages, Discoverer workbooks, and external integrations that read from the APPS schema.

Underlying Base Objects

The view is defined over three documented base objects, all exposed as APPS synonyms:

The outer join to the standard version (STD) is significant: it allows history rows to be returned even when the associated standard article version no longer exists, preserving audit completeness.

Key Columns

Columns fall into identification, version, and descriptive categories:

  • ROW_ID — the ROWID of the underlying history row, used as the surrogate key for the view.
  • ID, CHR_ID, CLE_ID, CAT_ID — identifiers for the article and its owning contract hierarchy (contract header, line, and terms), linking history back to the contract structure.
  • MAJOR_VERSION, OBJECT_VERSION_NUMBER, SAV_SAV_RELEASE — versioning metadata. SAV_SAV_RELEASE is derived via DECODE to select either the standard release or the article version number depending on whether the source article is standard.
  • SAV_SAE_ID — the resolved article ID; DECODE returns SAV_SAE_ID from CATB when the article is standard (STANDARD_YN = 'Y'), otherwise STD.ARTICLE_ID.
  • SBT_CODE — maps to ART.ARTICLE_TYPE, the sub-type/code classifying the article.
  • NAME — NVL(VERS.DISPLAY_NAME, ART.ARTICLE_TITLE), the user-facing label.
  • TEXT, COMMENTS, VARIATION_DESCRIPTION, FULLTEXT_YN — the article body, description, variation text, and full-text indicator.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield columns carried from the history table.
  • CAT_TYPE — derived by DECODE on ORIG_SYSTEM_REFERENCE_CODE ('OKE', 'OKC11510UPG:OKE' → 'STA'; otherwise falls back to DECODE on ART.STANDARD_YN, returning 'STA' or 'NSD').
  • SFWT_FLAG, DNZ_CHR_ID — a NULL placeholder flag and denormalized contract header ID.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include auditing clause changes over time, generating "as-of" contract term reports, and reconciling imported legacy contracts (the OKE upgrade paths mapped by CAT_TYPE). A representative query retrieves the change history of a contract's articles:

  • SELECT ID, MAJOR_VERSION, NAME, SBT_CODE, CAT_TYPE, SAV_SAV_RELEASE, LAST_UPDATE_DATE FROM OKC_K_ARTICLES_HV WHERE CHR_ID = :contract_id ORDER BY MAJOR_VERSION, LAST_UPDATE_DATE;
  • SELECT CHR_ID, COUNT(*) FROM OKC_K_ARTICLES_HV WHERE MAJOR_VERSION = :ver GROUP BY CHR_ID — to enumerate articles belonging to a specific version.
  • SELECT ID, TEXT FROM OKC_K_ARTICLES_HV WHERE FULLTEXT_YN = 'Y' AND STANDARD_YN implied standard via CAT_TYPE = 'STA' — isolating standard boilerplate articles.

Because the view joins three substantial tables, queries should be filtered on CHR_ID or ID to leverage the underlying indexes and avoid full scans of the history table.