Search Results term_value




Overview
Explore in AI Chat

Overview

OKE_K_TERMS_V is a seeded, APPS-owned database view in the Oracle E-Business Suite Project Contracts (OKE) module. It is documented as the "Terms & Conditions View" and is delivered in the ETRM (Enterprise Technical Reference Manual) for Oracle EBS 12.1.1 and 12.2.2. The view consolidates contract terms and conditions associated with a project contract header, joining the stored term identifiers held in the contract terms table against the term definition and term type setup views, and resolving the coded term key values into human-readable meanings through the OKE_UTILS package. Because the underlying term values are stored as foreign-key references rather than descriptive text, the view performs the decoding at the database level, which makes it directly consumable by reports, concurrent programs, PL/SQL APIs, and integration extracts without additional application-layer logic. Its status is documented as VALID in the ETRM metadata.

Underlying Base Objects

The view text is defined over four sources, three of which are themselves views or synonyms:

The joins are: T.TERM_CODE = KT.TERM_CODE, TT.TERM_TYPE_CODE = T.TERM_TYPE_CODE, and K.CHR_ID = KT.K_HEADER_ID.

Key Columns

The view exposes 35 columns. The most significant are:

  • K_HEADER_ID / K_LINE_ID — foreign keys to the contract header and, where applicable, the contract line.
  • MAJOR_VERSION — the contract version obtained via OKE_K_VERS_NUMBERS_V.
  • TERM_CODE, TERM_VALUE_PK1, TERM_VALUE_PK2 — the stored term identifier and its composite value key; these are the raw stored values.
  • TERM_VALUE — the decoded MEANING returned by OKE_UTILS.GET_TERM_VALUES, i.e., the display value of the term.
  • DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE — additional decoded attributes derived from the term value record, with the date columns explicitly wrapped in TO_DATE.
  • TERM_NAME, TERM_TYPE_CODE, TERM_TYPE_NAME — descriptive setup data from OKE_TERMS_VL and OKE_TERM_TYPES_V.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from OKE_K_TERMS.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF/extension columns available for descriptive flexfield data.
  • ROW_ID — the ROWID of the underlying OKE_K_TERMS row, useful for direct row addressing.

Common Use Cases and Queries

Typical uses include contract-terms reporting, extraction of terms by contract version, validation of decoded term values, and diagnostic queries when a term displays incorrectly in the Contracts form. A representative query:

  • SELECT k_header_id, major_version, term_name, term_type_name, term_value, description, start_date_active, end_date_active FROM oke_k_terms_v WHERE k_header_id = :p_header_id ORDER BY term_type_name, term_name;
  • SELECT k_header_id, term_code, term_value_pk1, term_value_pk2 FROM oke_k_terms_v WHERE term_value IS NULL; — identifies terms whose stored key values cannot be decoded by OKE_UTILS.
  • SELECT term_type_code, term_type_name, COUNT(*) FROM oke_k_terms_v GROUP BY term_type_code, term_type_name; — validates term type distribution.

Because the view calls OKE_UTILS.GET_TERM_VALUES per row, decode cost scales with data volume; constrain queries by K_HEADER_ID or date range wherever possible.