Search Results okc_k_headers_bh_pk

Overview

The OKC_K_HEADERS_BH table is a history table within the Oracle E-Business Suite (EBS) Contracts Core (OKC) module. Its primary role is to maintain a historical record of changes made to the primary contract header table, OKC_K_HEADERS_B. This table is fundamental for tracking the evolution of contract master data over time, supporting audit trails, compliance reporting, and historical analysis. The presence of a versioning column (MAJOR_VERSION) indicates it is designed to capture significant revisions to contract headers, potentially aligning with formal contract amendment processes. According to the provided metadata, this specific object is noted as "Not implemented in this database," which may indicate it is a defined but inactive schema object in certain EBS instances or deployments.

Key Information Stored

As a history table, OKC_K_HEADERS_BH is expected to mirror the structure of its base table, OKC_K_HEADERS_B, while adding columns to manage historical tracking. The documented primary key consists of the ID and MAJOR_VERSION columns. The ID column typically stores the unique identifier for a contract header, linking each historical record back to its original contract. The MAJOR_VERSION column is critical, storing a version number that sequences the historical revisions for a given contract ID. While other columns are not detailed in the excerpt, standard history table patterns suggest it would also include audit columns such as CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY to track who made changes and when, along with all the core data columns from the base table at the point of each version save.

Common Use Cases and Queries

The primary use case for OKC_K_HEADERS_BH is auditing and historical reporting on contract header modifications. Analysts can reconstruct the state of a contract at any point in its version history. A common query pattern involves retrieving the full history for a specific contract or identifying the specific version active at a given date. For example, to find all historical versions for a contract, one might use: SELECT * FROM OKC_K_HEADERS_BH WHERE ID = :contract_id ORDER BY MAJOR_VERSION DESC;. Another critical use case is comparative reporting between versions to understand what terms, dates, or parties changed between major amendments. If the table is not implemented, as noted, these queries would not be operational in that specific environment.

Related Objects

The table maintains defined relationships with other objects in the Contracts schema. Its primary key (OKC_K_HEADERS_BH_PK on ID, MAJOR_VERSION) uniquely identifies each historical record. As per the provided foreign key metadata, it is referenced by the OKE_K_HEADERS_H table in the Oracle Contracts for Projects (OKE) module. This relationship is established through the columns OKE_K_HEADERS_H.K_HEADER_ID and OKE_K_HEADERS_H.MAJOR_VERSION, which join to the primary key columns of OKC_K_HEADERS_BH. This indicates that the projects-specific contract history is linked to the core contract history, ensuring data consistency across modules. The most directly related object is its base table, OKC_K_HEADERS_B, from which the historical snapshots are derived.