Search Results okc_std_art_versions_b




Overview
Explore in AI Chat

Overview

The OKC_STD_ART_VERSIONS_B table is a core data object within the Oracle E-Business Suite Contracts Core (OKC) module, specifically in releases 12.1.1 and 12.2.2. Its primary function is to maintain a version history for the text of Standard Articles. In the context of contract authoring and management, Standard Articles are pre-defined, reusable clauses or terms. This table enables the system to track changes over time by storing prior versions of an article's text as well as any future-dated text revisions that are scheduled to become effective. This versioning capability is critical for audit trails, compliance, and ensuring the correct article text is applied to a contract based on its effective date.

Key Information Stored

The table's structure is designed to link a version to a specific Standard Article and manage its lifecycle. The primary key is a composite of SAE_ID and SAV_RELEASE, enforcing uniqueness for each version of an article. The SAE_ID column is a foreign key that links directly to the base standard article record in the OKC_STD_ARTICLES_B table. The SAV_RELEASE column typically holds a numeric or date-based identifier that denotes the version sequence or the effective release of the article text. While the provided metadata does not list all columns, based on its purpose, the table would also contain columns for the full article text (or a pointer to it), effective start and end dates for the version, and status indicators to manage active, historical, and future-dated entries.

Common Use Cases and Queries

A primary use case is retrieving the correct, effective version of a Standard Article's text for inclusion in a contract at a given point in time. For example, when generating a contract dated for a future period, the system must select the article version valid for that date. Common reporting needs include auditing changes to standard terms and generating a version history log for compliance purposes. A typical query pattern would join this table to OKC_STD_ARTICLES_B to fetch article details and filter by SAE_ID and a target effective date.

  • Sample Query for Effective Text: SELECT article_text FROM okc_std_art_versions_b WHERE sae_id = :article_id AND :target_date BETWEEN effective_start_date AND effective_end_date;
  • Use Case: Generating a report of all modifications made to a specific Standard Article over the last year for legal review.

Related Objects

The most direct and critical relationship for OKC_STD_ART_VERSIONS_B is with the OKC_STD_ARTICLES_B table, as defined by its foreign key constraint. Every record in the versions table must correspond to a parent record in the standard articles table. This table is also foundational for the Contracts Core application logic; therefore, it is referenced by various OKC package bodies (e.g., OKC_STD_ARTICLES_PVT) and views that provide API and reporting layers for article management. While not listed in the brief metadata, related transactional tables, such as those storing contract lines (OKC_K_ARTICLES_B), would indirectly rely on the integrity of this version data to ensure the correct article text is associated with a contract.