Search Results okc_k_headers_bh




Overview
Explore in AI Chat

Overview

The OKE_K_HEADERS_H table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for historical information related to the extended header data of project contracts. While the main contract header information is managed in foundational tables like OKC_K_HEADERS_BH, this table stores the OKE-specific, versioned attributes for a contract. Its role is critical for maintaining a complete audit trail and version history of a contract's key project-related attributes throughout its lifecycle, enabling compliance, historical reporting, and analysis of changes over time.

Key Information Stored

The table's structure is designed to track changes to a contract's extended header by version. The primary key is a composite of K_HEADER_ID, which identifies the contract, and MAJOR_VERSION, which identifies the specific historical snapshot. Key foreign key columns link this historical data to other master and transactional entities. These include PROGRAM_ID (linking to OKE_PROGRAMS), PROJECT_ID (linking to PA_PROJECTS_ALL), K_TYPE_CODE (linking to contract types in OKE_K_TYPES_B), and PRIORITY_CODE (linking to OKE_PRIORITY_CODES_B). The BOA_ID column establishes a relationship with the base contract header record in OKE_K_HEADERS. Collectively, these columns store a versioned record of the contract's project context, type, priority, and other OKE-specific classifications.

Common Use Cases and Queries

This table is primarily accessed for historical auditing and version comparison reports. A common use case is to generate a report showing all changes to a contract's project or program assignment over time. Another scenario involves reconciling billing or deliverable terms against the contract version that was active at a specific historical point in time. A typical query pattern retrieves the full version history for a specific contract, often joining with descriptive tables for clearer reporting.

Sample Query Pattern:
SELECT h.K_HEADER_ID, h.MAJOR_VERSION, h.PROJECT_ID, p.NAME PROJECT_NAME,
h.PROGRAM_ID, pg.NAME PROGRAM_NAME, h.K_TYPE_CODE
FROM OKE.OKE_K_HEADERS_H h
LEFT JOIN PA.PA_PROJECTS_ALL p ON h.PROJECT_ID = p.PROJECT_ID
LEFT JOIN OKE.OKE_PROGRAMS pg ON h.PROGRAM_ID = pg.PROGRAM_ID
WHERE h.K_HEADER_ID = :p_contract_id
ORDER BY h.MAJOR_VERSION DESC;

Related Objects

OKE_K_HEADERS_H sits at the center of a network of historical tables in the Project Contracts schema. It has defined foreign key relationships with several master tables and is referenced as a parent table by other historical detail tables. Based on the provided metadata, the key relationships are:

  • Parent Tables (Foreign Keys from OKE_K_HEADERS_H):
    • OKE_PROGRAMS (via PROGRAM_ID)
    • PA_PROJECTS_ALL (via PROJECT_ID)
    • OKE_K_HEADERS (via BOA_ID)
    • OKE_K_TYPES_B (via K_TYPE_CODE)
    • OKE_PRIORITY_CODES_B (via PRIORITY_CODE)
    • OKC_K_HEADERS_BH (via K_HEADER_ID, MAJOR_VERSION)
  • Child Tables (Foreign Keys referencing OKE_K_HEADERS_H):

This structure ensures that historical versions of billing methods, standard notes, terms, and user attributes are correctly associated with the corresponding version of the extended contract header.