Search Results okc_article_versions




Overview
Explore in AI Chat

Overview

The OKC_ARTICLE_VERSIONS table is a core data object within the Oracle E-Business Suite Contracts Core module (OKC). It serves as the central repository for managing the version history of clauses, which are referred to as "articles" within the application. Every clause attached to a business document, such as a contract or an amendment, is stored as a versioned record in this table. It distinguishes between standard clauses, which can have multiple iterative versions over time, and non-standard (ad-hoc) clauses, which are typically created with a single, immutable version. This table is fundamental to the contract authoring and compliance lifecycle, enabling precise tracking of clause changes, auditability, and ensuring the correct version of a clause is applied to a given document.

Key Information Stored

The table stores metadata and content for each unique version of a clause. While the full column list is extensive, key fields typically include a unique identifier (ARTICLE_VERSION_ID), a foreign key to the base clause definition (ARTICLE_ID from OKC_ARTICLES), and a version number (VERSION_NUMBER). It holds the substantive clause text in fields like ARTICLE_TEXT or ARTICLE_TEXT_UPDATE. Critical status and tracking columns include START_DATE and END_DATE to define the version's active period, a VERSION_STATUS (e.g., DRAFT, APPROVED, ACTIVE), and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) for audit purposes.

Common Use Cases and Queries

A primary use case is retrieving the active version of a standard clause for a given date to ensure contract integrity. For reporting and audit trails, queries often join to the OKC_ARTICLES table to list all versions of a specific clause. Support and development teams may query this table to diagnose issues with clause rendering or versioning logic.

  • Find Active Version: SELECT * FROM okc_article_versions WHERE article_id = :1 AND sysdate BETWEEN start_date AND NVL(end_date, sysdate+1);
  • Clause Version History: SELECT av.version_number, av.article_text, av.version_status FROM okc_articles a, okc_article_versions av WHERE a.article_id = av.article_id AND a.article_number = 'CLAUSE_123' ORDER BY av.version_number DESC;

Related Objects

OKC_ARTICLE_VERSIONS is a central hub in the Contracts Core data model. Its primary relationship is with the OKC_ARTICLES table, where OKC_ARTICLE_VERSIONS.ARTICLE_ID is a foreign key to OKC_ARTICLES.ARTICLE_ID. This defines the parent-child relationship between a clause definition and its versions. Furthermore, the table is referenced by document line detail tables, such as OKC_K_ARTICLES_B (which likely uses ARTICLE_VERSION_ID as a foreign key), to link a specific clause version to its instance on a contract or business document. This ensures the precise text used in a signed document is preserved.