Results for “oke_k_terms”

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

Overview

OKE_K_TERMS is a transactional table in the OKE (Project Contracts) module of Oracle E-Business Suite, documented as VALID in release 12.1.1 and 12.2.2. It stores the Terms & Conditions lines associated with contract headers and contract lines managed within Oracle Project Contracts. In EBS, Project Contracts supports the authoring, negotiation, and administration of complex agreements such as sales contracts, purchase agreements, and subcontracts. Terms and conditions capture the contractual clauses — payment terms, delivery obligations, penalty provisions, warranty statements, governing law, and similar negotiated text or coded values — that accompany the commercial structure of a contract. OKE_K_TERMS therefore functions as the detailed repository for those clause-level entries.

The table is owned by the OKE schema and contains 26 documented physical columns. Based on the foreign key structure supplied in the ETRM metadata, the heuristic Data Vault classification for this object is link. It records an association between a contract header, a contract line, and a term definition/term value, rather than functioning as a standalone hub of business entities or a satellite of descriptive attributes.

Key Information Stored

The most significant columns define the contract context and the term being recorded:

• K_HEADER_ID — Identifier of the parent contract header in OKE_K_HEADERS.
• K_LINE_ID — Identifier of the associated contract line in OKE_K_LINES.
• TERM_CODE — Code identifying the term or clause type being recorded.
• TERM_VALUE_PK1 and TERM_VALUE_PK2 — Key values that identify the specific term value, supporting terms with flexible or multi-part value structures.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the term record was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login responsible for it.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, used to store client-specific extensions of the terms data.

The unique index OKE_K_TERMS_U1 covers K_HEADER_ID, TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2, and K_LINE_ID, and serves as a business-key candidate enforcing uniqueness of a term entry within its contract and line context. The documented primary key constraint is OKE_K_TERMS_UK01, spanning K_HEADER_ID, K_LINE_ID, TERM_CODE, TERM_VALUE_PK1, and TERM_VALUE_PK2. The surrogate-to-business key relationship is therefore explicit: the composite key columns represent the business identity of each term record.

Common Use Cases and Queries

Typical applications include retrieving all terms for a given contract, auditing clause coverage across lines, and reporting on term usage by code.

• Listing all terms for a contract header:
  SELECT term_code, term_value_pk1, term_value_pk2 FROM oke.oke_k_terms WHERE k_header_id = :header_id;
• Drilling into terms for a specific contract line:
  SELECT * FROM oke.oke_k_terms WHERE k_header_id = :header_id AND k_line_id = :line_id;
• Counting obligations by term type for reporting:
  SELECT term_code, COUNT(*) FROM oke.oke_k_terms GROUP BY term_code;
• Joining to headers to surface contract names alongside terms: oke_k_terms t, oke_k_headers h WHERE t.k_header_id = h.k_header_id.

Descriptive flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) can be queried to expose customer-specific term attributes in custom reports and integrations.

Related Objects

• OKE_K_HEADERS — Parent contract header; joined on OKE_K_TERMS.K_HEADER_ID = OKE_K_HEADERS.K_HEADER_ID.
• OKE_K_LINES — Parent contract line; joined on OKE_K_TERMS.K_LINE_ID = OKE_K_LINES.K_LINE_ID.
• OKE_K_TERMS_UK01 / OKE_K_TERMS_U1 — Primary key constraint and unique index enforcing the business key.
• OKE_K_TERM_TYPES / term definition objects — Reference data resolving TERM_CODE to descriptive term definitions, where configured in the module.
• Oracle Project Contracts APIs — Contract authoring and term maintenance APIs that insert and update rows in OKE_K_TERMS during contract lifecycle processing.