Search Results okl_k_articles_uv




Overview
Explore in AI Chat

Overview

OKL_K_ARTICLES_UV is a valid, APPS-owned database view within the Oracle E-Business Suite Lease and Finance Management (OKL) product family. It exposes article and clause data used in lease and finance contract authoring, and is consumed by reporting, integration, and extension logic that requires a consolidated, upward-compatible (UV) representation of article records. The suffix "UV" denotes a user-facing view that flattens and standardizes data from underlying contract repository structures so that downstream tools do not have to resolve type-specific joins themselves.

In the ETRM 12.2.2 documentation the view is registered with referenced base objects MO_GLOBAL (PACKAGE), OKC_K_ARTICLES_V (VIEW), and OKC_STD_ARTICLES_V (VIEW). It belongs to the OKL - Lease and Finance Management module, and in 12.1.1 it is defined in the APPS schema with STATUS = VALID.

Underlying Base Objects

The view text is a UNION of two branches over OKC_K_ARTICLES_V. The first branch selects articles whose CAT_TYPE equals 'NSD'. The second branch selects articles whose CAT_TYPE equals 'STA' and joins OKC_STD_ARTICLES_V (aliased SAE) on CAT.SAV_SAE_ID = SAE.ID to obtain the article name. This join is the locus of the SAV_SAE_ID column referenced in the user search.

  • OKC_K_ARTICLES_V — the core contract articles view supplying nearly every column in the projection (ID, CHR_ID, CLE_ID, CAT_ID, SAV_SAE_ID, CAT_TYPE, and audit columns).
  • OKC_STD_ARTICLES_V — the standard articles view, joined only in the 'STA' branch to source SAE.NAME.
  • MO_GLOBAL — the multi-org initialization package referenced by the view's dependent object graph, relevant to operating unit and org-secured access behavior.

Key Columns

  • ID — primary article identifier.
  • CHR_ID — contract header identifier linking the article to its contract.
  • CLE_ID — contract line (element) identifier.
  • CAT_ID — article category identifier.
  • SAV_SAE_ID — foreign key to the standard article (OKC_STD_ARTICLES_V.ID); populated for CAT_TYPE = 'STA' and used in the join that yields the article name.
  • SAV_SAV_RELEASE — release/version reference associated with the standard article.
  • NAME — for 'NSD' rows derived from CAT.NAME; for 'STA' rows derived from SAE.NAME.
  • CAT_TYPE — discriminator; 'NSD' (non-standard) versus 'STA' (standard).
  • SBT_CODE, DNZ_CHR_ID, COMMENTS, FULLTEXT_YN, VARIATION_DESCRIPTION — descriptive and control attributes.
  • OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard OAF/WHO audit columns enabling optimistic locking and traceability.

Common Use Cases and Queries

Typical use cases include reporting on standard versus non-standard articles attached to a lease, identifying articles linked to a specific standard article template via SAV_SAE_ID, and integration extracts into downstream document or pricing engines. A basic query returning standard articles tied to a template might read:

SELECT id, chr_id, cle_id, cat_id, sav_sae_id, name, cat_type FROM apps.okl_k_articles_uv WHERE cat_type = 'STA' AND sav_sae_id = :p_sae_id;

To segment article populations by origin:

SELECT cat_type, COUNT(*) FROM apps.okl_k_articles_uv GROUP BY cat_type;

Because the view presents both branches through a single column set, it is well suited to UNION-safe consumers and to extensions that must handle standard and non-standard articles uniformly. Queries should honor MO_GLOBAL-based org context where operating unit security applies.