Search Results okc_std_art_versions_b




Overview
Explore in AI Chat

Overview

OKC_STD_ART_VERSIONS_B is a core table within the Oracle E-Business Suite Contracts Core (OKC) module. It maintains prior and future text for Standard Articles, which are reusable contract clause templates authored and managed through Oracle Contracts. In Oracle EBS 12.1.1 and 12.2.2, Standard Articles provide the boilerplate legal and commercial language that is copied into contract templates and individual contracts. Because such language changes over time—through regulatory updates, negotiated redlines, or organizational policy revisions—this table preserves version history so that historical contract text remains reproducible and audit-ready.

The ETRM documentation explicitly describes the table's purpose as maintaining prior and future text for Standard Articles. Under a heuristic Data Vault classification, the object is modeled as satellite-leaning, since it stores descriptive, time-versioned attributes of a parent Standard Article keyed by a business-effective release identifier rather than independent business events. This classification is a modeling suggestion; the physical table remains a standard EBS transactional structure.

Key Information Stored

The table contains 26 documented columns. The most significant are:

  • SAE_ID — Foreign key to OKC_STD_ARTICLES_B. Identifies the parent Standard Article to which the versioned text belongs. Part of the primary key.
  • SAV_RELEASE — The version/release identifier for a particular dated snapshot of the Standard Article text. Part of the primary key and the discriminator that enables historical and future-dated versions to coexist.
  • DATE_ACTIVE — The effective date on which the version becomes applicable, supporting future-dated text changes.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework to prevent concurrent update conflicts.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking version authorship and modification history.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The DFF (Descriptive Flexfield) columns allowing customer-specific extension of version metadata without schema changes.
  • SECURITY_GROUP_ID — References FND_SECURITY_GROUPS and enforces multi-org/security group data isolation.

The surrogate-style primary key is OKC_STD_ART_VERSIONS_B_PK over (SAE_ID, SAV_RELEASE). The unique index OKC_STD_ART_VERSIONS_B_U1 over the same two columns is documented as the business-key candidate, confirming that a Standard Article may hold at most one version row per release.

Common Use Cases and Queries

Typical reporting and integration scenarios include reconstructing the exact article text in force on a given contract date, comparing successive versions of a clause, auditing who changed standard language, and identifying future-dated revisions pending activation.

  • Retrieve all versions of a Standard Article: SELECT SAV_RELEASE, DATE_ACTIVE FROM OKC.STD_ART_VERSIONS_B WHERE SAE_ID = :p_sae_id ORDER BY SAV_RELEASE;
  • Identify the version active on a date: SELECT MAX(SAV_RELEASE) KEEP (DENSE_RANK LAST ORDER BY DATE_ACTIVE) FROM OKC_STD_ART_VERSIONS_B WHERE SAE_ID = :p_sae_id AND DATE_ACTIVE <= :p_as_of_date;
  • List future-dated versions for change control review: SELECT SAE_ID, SAV_RELEASE, DATE_ACTIVE FROM OKC_STD_ART_VERSIONS_B WHERE DATE_ACTIVE > SYSDATE;
  • Join to the parent article to report title alongside versions, and join SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict output by operating unit.

Related Objects

  • OKC_STD_ARTICLES_B — Parent table; joiner via OKC_STD_ART_VERSIONS_B.SAE_ID = OKC_STD_ARTICLES_B.SAE_ID. Holds current Standard Article definitions.
  • OKC_STD_ARTICLES_TL — Language-specific translations of the parent Standard Articles.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for data security.
  • OKC_ARTICLES_B / OKC_ARTICLES_TL — Contract-level article instances that may source text from Standard Articles.
  • OKC_TEMPLATES_B and related template tables — Template assemblies consuming Standard Article content.
  • OKC Contract Terms APIs — Standard article and version maintenance is largely exposed through OKC public APIs rather than direct DML; direct updates to this table are not supported.