Search Results oke_k_terms




Overview
Explore in AI Chat

Overview

The OKE_K_TERMS table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It serves as the primary repository for storing terms and conditions associated with project contracts. This table is essential for managing the contractual details that govern agreements, capturing specific clauses, deliverables, payment milestones, and other conditional attributes beyond the basic header and line information. Its role is to provide a structured and flexible framework for attaching detailed contractual stipulations to both contract headers and individual line items, enabling comprehensive contract administration and compliance tracking within the Oracle EBS environment.

Key Information Stored

The table's structure is designed to link terms to specific contracts and their components. The primary key uniquely identifies a term record through a combination of columns: K_HEADER_ID (the contract identifier), K_LINE_ID (the specific line item, which may be null for header-level terms), TERM_CODE (a code identifying the type of term or condition), and the composite key columns TERM_VALUE_PK1 and TERM_VALUE_PK2. This composite key structure allows for the storage of complex term values. Key columns, as indicated by the foreign key relationships, include K_HEADER_ID, which links to the OKE_K_HEADERS table to define the parent contract, and K_LINE_ID, which optionally links to the OKE_K_LINES table to associate a term with a specific deliverable or line within that contract.

Common Use Cases and Queries

A primary use case is the extraction of all contractual terms for audit, reporting, or fulfillment purposes. For instance, to generate a report of all payment-related terms for a specific contract, a query would join OKE_K_TERMS with OKE_K_HEADERS, filtering on the contract number and relevant TERM_CODE values. Another common scenario involves validating line-specific deliverables by querying terms where K_LINE_ID is not null. Sample SQL to list all terms for a contract header would be:

  • SELECT term_code, term_value_pk1, term_value_pk2 FROM oke_k_terms WHERE k_header_id = :header_id ORDER BY k_line_id, term_code;

This table is also critical for integration points, where external systems may query contractual terms to trigger downstream processes like billing or project task creation based on defined conditions.

Related Objects

The OKE_K_TERMS table has direct and integral relationships with other fundamental tables in the Project Contracts schema. As documented, it is linked via foreign key constraints to two primary entities:

  • OKE_K_HEADERS: The master contract header table. The foreign key on K_HEADER_ID ensures every term is associated with a valid contract.
  • OKE_K_LINES: The contract lines table. The foreign key on K_LINE_ID allows terms to be attached at a granular, line-item level, providing detailed contractual control over specific deliverables or services.

These relationships position OKE_K_TERMS as a central detail table supporting the core contract structure, and it is frequently referenced in custom reports, interfaces, and extensions built around contractual term management.