Search Results okc_std_art_versions_b_u1

Overview

OKC.OKC_STD_ART_VERSIONS_B is the base table within the Oracle E-Business Suite Contracts (OKC) schema that stores the versioned definitions of Standard Articles, such as the FAR and DFAR clauses commonly referenced in government and commercial contracting. The table exists because Standard Articles are revised periodically; when a revision occurs, prior text must be preserved intact, since existing contracts reference the version that was current at authoring time, while newly authored contracts must draw on the currently active version.

The _B suffix denotes the base (non-translated) table. The descriptive text associated with each version is held in the corresponding _TL table, OKC_STD_ART_VERSIONS_TL, following the standard EBS multilingual pattern. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index OKC_STD_ART_VERSIONS_B_U1 resides in APPS_TS_TX_IDX.

Using Data Vault modeling heuristics derived from the foreign key structure, this object is classified as satellite-leaning. In practical terms, it behaves as a descriptive satellite attached to the Standard Article hub (OKC_STD_ARTICLES_B), capturing time-variant, version-specific attributes rather than independent business entities.

Key Information Stored

The table is identified in ETRM documentation with 26 columns. The most operationally significant columns are:

• SAE_ID (NUMBER) — Identifier of the parent standard article. This column participates in the composite primary key and is a foreign key to OKC_STD_ARTICLES_B.
• SAV_RELEASE (VARCHAR2, 150) — The version label of the article; described in the ETRM metadata as holding the incremental number of the version.
• DATE_ACTIVE (DATE) — The date and time at which this version occurrence becomes active for user access, supporting effective-dated selection of the correct clause text.
• OBJECT_VERSION_NUMBER (NUMBER) — Sequential number set to 1 on insert and incremented on update; used by the APIs to enforce optimistic locking and confirm that the current record is being modified.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level access control consistent with the rest of the OKC schema.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, providing audit lineage for every version record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns (VARCHAR2 90 and 450 respectively) available for customer-specific extensions without schema modification.

The surrogate primary key is defined by OKC_STD_ART_VERSIONS_B_PK over (SAE_ID, SAV_RELEASE). A separate unique index, OKC_STD_ART_VERSIONS_B_U1, covers the same two columns, making the article identifier combined with the release label the business-key candidate for this table.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving the currently active version of a clause, reconstructing the historical text referenced by a legacy contract, and validating version coverage across a library of standard articles.

• Listing all versions for a given article: SELECT SAV_RELEASE, DATE_ACTIVE FROM OKC.OKC_STD_ART_VERSIONS_B WHERE SAE_ID = :p_sae_id ORDER BY DATE_ACTIVE;
• Identifying the effective version as of a contract date: filter on DATE_ACTIVE <= :contract_date and select the row with the maximum DATE_ACTIVE.
• Joining to the translation table, OKC_STD_ART_VERSIONS_TL, on SAE_ID and SAV_RELEASE (plus LANGUAGE) to surface the actual article text.
• Audit reporting using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to track when new clause versions were introduced.
• Integration through the standard OKC APIs, which rely on OBJECT_VERSION_NUMBER to detect concurrent updates before committing changes.

Related Objects

• OKC.OKC_STD_ARTICLES_B — Parent entity; joined via SAE_ID. Holds the article header definition.
• OKC.OKC_STD_ART_VERSIONS_TL — Translation table holding the version-specific text, joined on SAE_ID and SAV_RELEASE.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID to govern row-level security.
• OKC_STD_ART_VERSIONS_B_PK / OKC_STD_ART_VERSIONS_B_U1 — Primary key constraint and unique index supporting the business key.
• OKC Contracts APIs — Standard article and contract authoring APIs that read version records and enforce OBJECT_VERSION_NUMBER during updates.