Results for “sav_sav_release”

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

Overview

The view APPS.OKL_VP_STD_ARTICLES_UV is a reporting and integration object within the Oracle E-Business Suite Leasing and Finance Management module (OKL). It exposes the standard article content associated with lease and finance contracts, presenting the textual terms, clauses, and conditions that are maintained as reusable standard articles in the contract repository. In Oracle EBS 12.1.1 and 12.2.2, contract terms and conditions are stored as standard articles with versioned text, and this view flattens the article header and its versioned body into a single, query-friendly structure.

Because it is owned by the APPS schema and defined as a view, it carries no storage of its own; it is a virtual projection over the underlying Oracle Contracts (OKC) article views. Its principal role is to supply customer-facing or internal reporting, document generation, and integration consumers with a consolidated read of article name, article text, and the versions to which that text belongs. This makes it particularly relevant where lease documents must reference standardized legal language.

Underlying Base Objects

The documented ETRM 12.2.2 metadata identifies three referenced base objects:

• OKC_STD_ARTICLES_V (VIEW) — the article header source, aliased as SAE in the view text.
• OKC_STD_ART_VERSIONS_V (VIEW) — the versioned article text source, aliased as SAV.
• MO_GLOBAL (PACKAGE) — the Multi-Org / operating unit access control package used to enforce organization-level security.

The view text joins the article header to its versioned text on the article identifier:

SELECT SAE.NAME NAME, SAV.TEXT TEXT, SAV.SAE_ID SAV_SAE_ID, SAV.SAV_RELEASE SAV_SAV_RELEASE FROM OKC_STD_ARTICLES_V SAE, OKC_STD_ART_VERSIONS_V SAV WHERE SAV.SAE_ID = SAE.ID

The join therefore links each standard article (SAE.ID) to its corresponding version rows (SAV.SAE_ID), producing one output row per article-version combination. The presence of MO_GLOBAL indicates that results are subject to multi-org security filtering, so accessible rows depend on the operating unit context of the session.

Key Columns

• NAME — the standard article name from OKC_STD_ARTICLES_V, identifying the clause or term.
• TEXT — the full article body text from OKC_STD_ART_VERSIONS_V, holding the version-specific content.
• SAV_SAE_ID — the article identifier (SAV.SAE_ID) linking the version back to its header article.
• SAV_SAV_RELEASE — the release or version indicator (SAV.SAV_RELEASE) distinguishing successive revisions of the article text.

Together these columns provide the article name, its text for a given release, and the keys needed to correlate versions.

Common Use Cases and Queries

This view is typically consumed for clause and terms-and-conditions reporting, audit of article versions, and integration with document generation. A simple retrieval of all accessible article versions is:

SELECT NAME, SAV_SAV_RELEASE, SAV_SAE_ID FROM OKL_VP_STD_ARTICLES_UV ORDER BY NAME, SAV_SAV_RELEASE;

To inspect text for a specific article identifier, filter on the article key:

SELECT NAME, SAV_SAV_RELEASE, TEXT FROM OKL_VP_STD_ARTICLES_UV WHERE SAV_SAE_ID = :p_sae_id;

Because the view is secured through MO_GLOBAL, callers should initialize the org context (for example, via MO_GLOBAL.SET_POLICY_CONTEXT or standard FND_GLOBAL initialization) before querying, otherwise row visibility may be restricted or inconsistent. The view is read-only and should be used for reporting rather than maintenance.