Search Results term_value_pk1




Overview
Explore in AI Chat

Overview

The OKE_K_TERMS_H table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It functions as the historical repository for terms and conditions associated with contract headers and lines. In the context of Oracle EBS 12.1.1 and 12.2.2, this table is essential for maintaining a complete, auditable record of all contractual term changes over the lifecycle of a project contract. Its role is to capture snapshots of term data each time a major version of a contract is created, enabling users to review the exact terms that were applicable at any point in the contract's history. This supports critical business processes like contract amendments, compliance auditing, and historical reporting.

Key Information Stored

The table stores historical versions of specific contractual terms linked to either a contract header or a line. Its primary key structure indicates the granularity of the data: it uniquely identifies a historical term record by combining the contract identifier, line identifier, term code, term value keys, and the major version number. Key columns include K_HEADER_ID (the contract identifier), K_LINE_ID (the associated line, if applicable), TERM_CODE (the type of term), TERM_VALUE_PK1 and TERM_VALUE_PK2 (keys identifying the specific value of the term), and MAJOR_VERSION (the contract version this historical record belongs to). This design allows the system to track precisely which terms were attached to which contract or line version.

Common Use Cases and Queries

A primary use case is auditing the evolution of specific contractual terms, such as payment terms or liability clauses, across contract amendments. Support teams may query this table to resolve disputes by verifying the terms in effect on a specific historical date. For reporting, it is central to generating contract history dossiers. A typical query pattern involves joining to the contract headers history table to filter by contract number and date ranges. For example, to find all historical records for a term 'PAYMENT_TERMS' on a specific contract, one might use: SELECT major_version, term_value_pk1 FROM oke_k_terms_h WHERE k_header_id = :p_header_id AND term_code = 'PAYMENT_TERMS' ORDER BY major_version;. Analysts also use this table in conjunction with current-term tables to perform delta analyses between versions.

Related Objects

The OKE_K_TERMS_H table has defined foreign key relationships with other central history tables in the Project Contracts schema, ensuring referential integrity for historical data. As per the provided metadata, the key relationships are:

  • OKE_K_HEADERS_H: The table is linked via K_HEADER_ID and MAJOR_VERSION. This ensures every historical term record corresponds to a valid historical version of a contract header.
  • OKE_K_LINES_H: The table is linked via K_LINE_ID and MAJOR_VERSION. This ensures that historical terms associated with a specific contract line correspond to a valid historical version of that line.
These relationships mean that queries for comprehensive historical contract data typically involve joining OKE_K_TERMS_H with both OKE_K_HEADERS_H (for header attributes like contract number and dates) and OKE_K_LINES_H (for line details like item and quantity).