Results for “oke_k_standard_notes_bh”

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

Overview

The table OKE_K_STANDARD_NOTES_BH resides in the OKE schema and belongs to the Oracle Project Contracts (OKE) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores historical information about contract standard notes. In the Oracle EBS architecture, this table functions as a historical (audit-versioned) companion to the base table OKE_K_STANDARD_NOTES_B, capturing prior or versioned states of standard notes associated with contract headers, lines, and deliverables. The "BH" suffix, consistent with the OKE Contracts data model naming convention, denotes a history or background table that preserves multiple major versions of a record over its lifecycle.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive and contextual attributes tied back to parent entities (contract headers, lines, and deliverables) through foreign keys. Its composite primary key of STANDARD_NOTES_ID and MAJOR_VERSION qualifies this as a versioned descriptive structure rather than an independent hub.

Key Information Stored

The table contains 28 documented columns. The most significant are described below.

• STANDARD_NOTES_ID — Surrogate identifier inherited from the base table OKE_K_STANDARD_NOTES_B; part of the primary key.
• MAJOR_VERSION — Version discriminator; combined with STANDARD_NOTES_ID it forms the primary key OKE_K_STD_NOTES_BH_PK and the unique index OKE_K_STD_NOTES_BH_U1, both serving as the business-key candidate.
• K_HEADER_ID — Foreign key to OKE_K_HEADERS_H, linking the standard note to its contract header version.
• K_LINE_ID — Foreign key to OKE_K_LINES_H, associating the note with a specific contract line version.
• DELIVERABLE_ID — Foreign key to OKE_K_DELIVERABLES_BH, tying the note to a deliverable component.
• TYPE_CODE — Classifies the nature or category of the standard note.
• DEFAULT_FLAG — Indicates whether the note is treated as a default for the associated entity.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The flexible descriptive flexfield (DFF) columns used to capture client-specific or context-dependent information.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who-columns providing audit tracking for each historical row.

Common Use Cases and Queries

Because this table preserves historical versions, it is primarily used for audit reporting, version comparison, and reconstruction of contract terms as they existed at a point in time. Typical scenarios include comparing the current standard note against its prior major version, auditing changes to contract deliverables, and validating which notes applied to a contract at a given milestone.

A representative query retrieving the current version of standard notes for a contract header:

SELECT sn.STANDARD_NOTES_ID, sn.MAJOR_VERSION, sn.K_HEADER_ID, sn.TYPE_CODE, sn.DEFAULT_FLAG
FROM OKE.OKE_K_STANDARD_NOTES_BH sn
WHERE sn.K_HEADER_ID = :header_id
ORDER BY sn.MAJOR_VERSION DESC;

A version-history query joining the base table to the historical table is also common when trend analysis of note revisions is required.

Related Objects

• OKE_K_STANDARD_NOTES_B — Base (non-historical) source table; the historical rows reference it via STANDARD_NOTES_ID.
• OKE_K_STANDARD_NOTES_TLH — Translation/language history table referencing this table through STANDARD_NOTES_ID and MAJOR_VERSION.
• OKE_K_HEADERS_H — Contract header history; joined on K_HEADER_ID and MAJOR_VERSION.
• OKE_K_LINES_H — Contract line history; joined on K_LINE_ID and MAJOR_VERSION.
• OKE_K_DELIVERABLES_BH — Deliverable history; joined on DELIVERABLE_ID and MAJOR_VERSION.

These relationships make OKE_K_STANDARD_NOTES_BH a central historical reference point for contract note traceability across the OKE Contracts data model.