Results for “okc_k_headers_bh”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_K_HEADERS_BH is the history (audit) table associated with OKC_K_HEADERS_B in the Oracle Contracts Core (OKC) module. In Oracle EBS 12.1.1 and 12.2.2, the "_BH" suffix convention denotes a shadow or history table that captures prior versions of the corresponding base table's rows. Each time a contract header row in OKC_K_HEADERS_B is updated, the pre-change image is preserved in OKC_K_HEADERS_BH, allowing point-in-time reconstruction of contract header master data without impacting transactional performance against the base table.

The table is documented in ETRM under product OKC - Contracts Core with the description "History table for OKC_K_HEADERS_B." Notably, the metadata states that this object is "Not implemented in this database," meaning it appears in the data model lineage but is not physically deployed in the referenced environment. Its Data Vault classification, derived heuristically from the foreign key structure, is hub-leaning. This suggests the table can be modeled as a hub-like structure where the combination of ID and MAJOR_VERSION forms a stable, non-volatile identity for a contract header version. Analysts designing a Data Vault or dimensional model on contract data may treat OKC_K_HEADERS_BH as a historical hub supplying versioned contract header identities.

Key Information Stored

The documented columns of OKC_K_HEADERS_BH are limited to the components of its primary key, OKC_K_HEADERS_BH_PK:

• ID — Surrogate identifier for the contract header. Together with MAJOR_VERSION it forms the composite primary key and represents the closest documented business-key candidate, mirroring the contract header identity in the base table.
• MAJOR_VERSION — Version number of the contract header at the time the history row was written. Because history tables capture the state before an update, each (ID, MAJOR_VERSION) pair uniquely identifies a preserved version of a contract header.

The primary key is composite, distinguishing this history table from single-column surrogate-key designs. Columns inherited from OKC_K_HEADERS_B beyond the key (for example contract number, name, status, and dates) are not enumerated in the provided metadata; the excerpt intentionally lists only the documented key columns. Where the base table carries descriptive attributes, those same attributes typically flow into the history shadow table so that full-row versioning is preserved.

Common Use Cases and Queries

Because history tables are append-only, they support auditing, version comparison, and historical reporting. Typical scenarios include reconstructing a contract header's attributes as of a past date, comparing successive major versions, and auditing who or what changed a contract.

• Retrieve all preserved versions for a contract: SELECT id, major_version FROM okc_k_headers_bh WHERE id = :contract_id ORDER BY major_version;
• Identify the latest historical version prior to a cutoff: SELECT * FROM okc_k_headers_bh WHERE id = :contract_id AND major_version = (SELECT MAX(major_version) FROM okc_k_headers_bh WHERE id = :contract_id);
• Reconcile base versus history counts to detect versioning gaps: join OKC_K_HEADERS_B and OKC_K_HEADERS_BH on ID.
• Feed downstream Data Vault or EDW models where the (ID, MAJOR_VERSION) pair serves as the hub key.

Related Objects

FK relationship data documents the following linkage:

• OKC_K_HEADERS_B — The base (current) contract header table whose historical images are stored here; related on ID and MAJOR_VERSION.
• OKE_K_HEADERS_H — Related through OKE_K_HEADERS_H.K_HEADER_ID and OKE_K_HEADERS_H.MAJOR_VERSION, matching the ID and MAJOR_VERSION columns of OKC_K_HEADERS_BH.
• OKC_K_HEADERS_BH_PK — The composite primary key constraint (ID, MAJOR_VERSION) that enforces version uniqueness.

Because the object is documented as not implemented in the referenced database, verify its physical presence and column completeness in the target environment before relying on it for reporting or ETL design.