Search Results okc_k_ate_v




Overview
Explore in AI Chat

Overview

OKC_K_ATE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. Its name follows the Oracle Contracts (OKC) naming convention, where "K" denotes the contract header entity and "ATE" reflects its association with articles. The view's documented purpose is to provide the contract records that utilize standard articles, enabling reporting and integration consumers to isolate those contracts whose article content derives from a standardized, pre-approved article template rather than from bespoke authored text.

In Oracle EBS 12.1.1 and 12.2.2, the OKC module underpins Contract Core functionality, including contract authoring, article management, versioning, and template reuse. Because the base data for contract articles is normalized across multiple header, article, and version tables, direct queries are cumbersome and error-prone. OKC_K_ATE_V addresses this by projecting a denormalized, DISTINCT result set joining the contract header, the contract-article association, the article version, and the articles view. This makes it a useful object for reports, extracts, and interfaces that need a concise list of contracts linked to standard articles.

Underlying Base Objects

The view text references three objects directly in its FROM clause and a fourth in its WHERE clause:

The documented metadata lists OKC_UTIL (PACKAGE) as a referenced base object; this package supplies utility logic commonly used across OKC views, though it is not visible in the excerpted view text. The join predicate ART.STANDARD_YN = 'Y' is the critical filter that restricts output to standard articles only, which is why the view can be described as "contracts using standard articles."

Key Columns

  • ID — the contract header identifier (DNZ_CHR_ID), the primary join key back to contract header data.
  • CONTRACT_NUMBER — the human-readable contract number.
  • CONTRACT_NUMBER_MODIFIER — the sub-number or modifier that distinguishes versions/instances of a contract.
  • SHORT_DESCRIPTION — a concise description of the contract.
  • SAV_SAE_ID — the article identifier for the standard article attached to the contract.
  • SAV_SAV_RELEASE — the resolved article release, computed as NVL(VERS.SAV_RELEASE, VERS.ARTICLE_VERSION_NUMBER); it returns the configured SAV release when present, otherwise falls back to the article version number.

Common Use Cases and Queries

Typical uses include identifying which contracts are governed by standard (template-based) articles for compliance reporting, and validating that article versions align with approved releases.

SELECT ID, CONTRACT_NUMBER, SAV_SAE_ID, SAV_SAV_RELEASE
FROM   APPS.OKC_K_ATE_V
WHERE  CONTRACT_NUMBER = :contract_number;

SELECT CONTRACT_NUMBER, COUNT(DISTINCT SAV_SAE_ID) std_article_count
FROM   APPS.OKC_K_ATE_V
GROUP BY CONTRACT_NUMBER
ORDER BY std_article_count DESC;

Because the view is DISTINCT and already filters on STANDARD_YN = 'Y', callers should not re-apply the standard-article filter. Joins to OKC_K_HEADERS_V on ID remain valid for retrieving additional header detail.