Search Results oke_k_standard_notes_bh




Overview
Explore in AI Chat

Overview

The OKE_K_STANDARD_NOTES_BH 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 functions as a historical (or "backup header") table designed to capture and preserve versioned changes to standard notes associated with contract headers, lines, and deliverables. Its primary role is to maintain a complete audit trail and historical record, enabling users to view the exact state of contractual notes at any point in a contract's revision history. This is critical for compliance, auditing, and understanding the evolution of contractual terms over time.

Key Information Stored

As a historical table, OKE_K_STANDARD_NOTES_BH stores snapshots of note data linked to specific major versions of contract components. The table's structure is defined by its primary key, which combines the STANDARD_NOTES_ID and the MAJOR_VERSION. This composite key uniquely identifies each historical record. Key columns include the STANDARD_NOTES_ID, which links to the base standard notes table (OKE_K_STANDARD_NOTES_B), and the MAJOR_VERSION, which aligns with the versioning of the parent contract object (header, line, or deliverable). The table also contains foreign key columns such as K_HEADER_ID, K_LINE_ID, and DELIVERABLE_ID to establish the relationship with the specific contract component whose history is being tracked, along with the corresponding MAJOR_VERSION for that component.

Common Use Cases and Queries

The primary use case for this table is historical reporting and audit analysis. For instance, to retrieve all historical versions of standard notes for a specific contract header, a common query would join OKE_K_STANDARD_NOTES_BH to OKE_K_HEADERS_H on K_HEADER_ID and MAJOR_VERSION. Another critical scenario is during contract amendments or renewals, where the system may reference historical note text. A sample SQL pattern to fetch the full history for a standard note ID would be:

  • SELECT * FROM OKE.OKE_K_STANDARD_NOTES_BH WHERE STANDARD_NOTES_ID = <note_id> ORDER BY MAJOR_VERSION DESC;

Reporting use cases often involve comparing note text across different major versions of a contract line or deliverable to document changes made during specific amendment cycles.

Related Objects

The OKE_K_STANDARD_NOTES_BH table is centrally connected to several other historical and base tables in the Project Contracts schema, as documented by its foreign key relationships. These relationships are essential for constructing complete historical views of contract data.

  • OKE_K_STANDARD_NOTES_B: The base table for standard notes. Joined via STANDARD_NOTES_ID.
  • OKE_K_HEADERS_H: The contract headers history table. Joined via K_HEADER_ID and MAJOR_VERSION.
  • OKE_K_LINES_H: The contract lines history table. Joined via K_LINE_ID and MAJOR_VERSION.
  • OKE_K_DELIVERABLES_BH: The deliverables history table. Joined via DELIVERABLE_ID and MAJOR_VERSION.
  • OKE_K_STANDARD_NOTES_TLH: The transaction line history table for standard notes. This table references OKE_K_STANDARD_NOTES_BH via STANDARD_NOTES_ID and MAJOR_VERSION.