Results for “oke_k_terms_h”

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

Overview

OKE_K_TERMS_H is the Terms & Conditions history table within the Oracle Project Contracts (OKE) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the historically versioned set of terms and conditions attached to contract headers and contract lines. Because the table name carries the "_H" suffix and the primary key includes MAJOR_VERSION, each row represents a specific version of a term rather than a single mutable record. When a contract is revised, amended, or re-approved, a new MAJOR_VERSION is stamped onto the affected terms, preserving a complete audit trail of contractual language over the life of the engagement.

From a data-modeling perspective, the ETRM heuristic classification for this object is a link. This suggestion reflects the table's role in resolving many-to-many associations: it connects contract headers and lines (via K_HEADER_ID and K_LINE_ID) to term definitions and their resolved values (TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2), while also anchoring each association to a specific contract version.

Key Information Stored

The column set divides cleanly into business keys, versioning attributes, and standard EBS audit/descriptive columns.

• K_HEADER_ID — Foreign key to OKE_K_HEADERS_H; identifies the contract header that owns the term.
• K_LINE_ID — Foreign key to OKE_K_LINES_H; identifies the specific contract line, when the term applies at line level.
• TERM_CODE — The defined term (the "question") being answered for this contract.
• TERM_VALUE_PK1 and TERM_VALUE_PK2 — Composite value keys that resolve the selected term value. Users searching for term_value_pk2 are typically tracing how a particular term value was captured and versioned. TERM_VALUE_PK2 is the second component of the value key and participates in both the primary key and the unique index, meaning it must be non-null and unique within its key combination.
• MAJOR_VERSION — The contract version stamp; part of the primary key and both unique indexes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns, available for client-specific term attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing who created and last touched each term version.

The primary key OKE_K_TERMS_H_UK01 combines K_HEADER_ID, K_LINE_ID, TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2, and MAJOR_VERSION. The unique index OKE_K_TERMS_H_U1 covers the same logical business key with a slightly different column ordering.

Common Use Cases and Queries

Typical reporting needs include reconstructing the terms in force at a given contract version, auditing changes between versions, and extracting term values for downstream contract-print or compliance reports.

• Retrieve all terms for the current version of a contract:
  SELECT term_code, term_value_pk1, term_value_pk2, major_version FROM oke.oke_k_terms_h WHERE k_header_id = :p_header AND major_version = (SELECT MAX(major_version) FROM oke.oke_k_terms_h WHERE k_header_id = :p_header);
• Trace history of a single term across versions:
  SELECT major_version, term_value_pk1, term_value_pk2, last_update_date FROM oke.oke_k_terms_h WHERE k_header_id = :p_header AND term_code = :p_term ORDER BY major_version;
• Find contracts where a specific term value was selected:
  SELECT k_header_id, k_line_id, major_version FROM oke.oke_k_terms_h WHERE term_value_pk2 = :p_value;
• Join to header and line history for descriptive context:
  SELECT h.contract_number, l.line_number, t.term_code, t.term_value_pk2 FROM oke.oke_k_terms_h t JOIN oke.oke_k_headers_h h ON h.k_header_id = t.k_header_id AND h.major_version = t.major_version JOIN oke.oke_k_lines_h l ON l.k_line_id = t.k_line_id AND l.major_version = t.major_version;

Related Objects

• OKE_K_HEADERS_H — Parent contract header history; joined on K_HEADER_ID (and MAJOR_VERSION).
• OKE_K_LINES_H — Parent contract line history; joined on K_LINE_ID (and MAJOR_VERSION).
• OKE_K_HEADERS — Current contract header records; cross-referenced for active contracts.
• OKE_K_LINES — Current contract line records; cross-referenced for active lines.
• OKE_TERM_DEFINITIONS / OKE_TERM_VALUES — Term and value lookup definitions that TERM_CODE and TERM_VALUE_PK1/PK2 resolve against.
• OKE_K_TERMS — The current (non-history) counterpart of this table.
• OKE_CONTRACTS_INT / Project Contracts APIs — Integration and public APIs that read and write term data, triggering new MAJOR_VERSION rows in this history table.

In practice, OKE_K_TERMS_H should be treated as an immutable audit stream: rows are inserted per version rather than updated, so queries must always filter on the intended MAJOR_VERSION to avoid mixing terms from different contract revisions.