Results for “oke_k_terms_u1”

12 results




Overview
Explore in AI Chat

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

Overview

OKE.OKE_K_TERMS is a transaction table in the Oracle E-Business Suite Contracts (OKE) application schema. It stores the terms and conditions that apply to a particular contract or to individual contract lines, functioning as the attribute store for clause and term selections captured during contract authoring. Each row associates a defined term — identified by TERM_CODE and up to two term value primary keys (TERM_VALUE_PK1 and TERM_VALUE_PK2) — with either a contract header or a contract line. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10 and holds 26 documented columns, including the standard WHO audit columns and a fifteen-segment descriptive flexfield (ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15).

The heuristic Data Vault classification for this object is link. This classification is a modeling suggestion derived from the foreign key structure: OKE_K_TERMS sits between contract headers and contract lines and resolves the many-to-many-style association between a contract entity and the term values selected for it. It is not a pure hub (it carries no single natural business key) and not a pure satellite (it holds the relationship itself rather than descriptive history about one parent).

Key Information Stored

The most significant columns fall into three groups.

  • Relationship keys. K_HEADER_ID identifies the contract document, and K_LINE_ID identifies the contract document line item. Both are foreign keys: K_HEADER_ID references OKE_K_HEADERS and K_LINE_ID references OKE_K_LINES.
  • Term identity. TERM_CODE (VARCHAR2(30)) is the internal identifier for the term. TERM_VALUE_PK1 (VARCHAR2(80)) and TERM_VALUE_PK2 (VARCHAR2(80)) carry the first and, where needed, second primary key value for the selected term value. The available selections are exposed through the OKE_TERM_VALUES_V view.
  • Audit and extensibility. The standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — support auditing and concurrency. ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 provide the descriptive flexfield context and segments.

The documented unique index OKE_K_TERMS_U1 covers K_HEADER_ID, TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2, and K_LINE_ID, making this composite the business-key candidate that enforces one selection per term value per contract or line. The relationship metadata identifies the primary key as OKE_K_TERMS_UK01 over the same five columns. The non-unique index OKE_K_TERMS_N1 on TERM_CODE supports term-centric lookups.

Common Use Cases and Queries

Typical reporting scenarios include listing all terms and conditions on a contract, extracting selected values for a specific term across a contract portfolio, and reconciling line-level versus header-level term placement.

  • Retrieve all terms for a contract header: SELECT TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2 FROM OKE.OKE_K_TERMS WHERE K_HEADER_ID = :p_header_id;
  • Retrieve terms for a specific contract line: SELECT TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2 FROM OKE.OKE_K_TERMS WHERE K_LINE_ID = :p_line_id;
  • Find every contract using a given term: SELECT K_HEADER_ID, K_LINE_ID FROM OKE.OKE_K_TERMS WHERE TERM_CODE = :p_term_code; — this path benefits from the OKE_K_TERMS_N1 index.
  • Resolve selected values to their display text by joining rows to OKE_TERM_VALUES_V on TERM_CODE and the term value primary keys.

Because the table is a link between headers, lines, and term values, it is frequently used in contract clause audit reports and in data migration validation when term selections are loaded from legacy contract repositories.

Related Objects

  • OKE.OKE_K_HEADERS — parent contract document; joined on K_HEADER_ID.
  • OKE.OKE_K_LINES — contract line items; joined on K_LINE_ID.
  • OKE.OKE_TERM_VALUES_V — view exposing the term values available for selection, keyed by TERM_CODE and the term value primary keys.
  • OKE.OKE_K_TERMS_U1 and OKE.OKE_K_TERMS_N1 — indexes on the table that constrain uniqueness and accelerate access.
  • Contract authoring and Terms & Conditions setup pages in the OKE module, which read and write rows in this table through the Contracts APIs.