Search Results oke_term_values_v




Overview
Explore in AI Chat

Overview

OKE_TERM_VALUES_V is an APPS-owned database view within the OKE – Project Contracts module of Oracle E-Business Suite. It is documented as the "Term value view" and carries a VALID status in both 12.1.1 and 12.2.2. Its purpose is to present a consolidated, read-only projection of the term and value pairs that drive contract and project configuration logic in Oracle Contracts (OKE). Because contract terms are not held in a single table, this view normalizes term values drawn from multiple heterogeneous sources into a uniform column layout, allowing forms, concurrent programs, and reporting tools to query contract term values through one interface rather than joining each source table individually.

The view plays a supporting role in EBS reporting and integration. It is typically consumed by OKE contract authoring and validation code, by Oracle Discoverer or BI Publisher reports needing term metadata, and by interface or extension logic that must resolve a valid term value given a term code. Because it aggregates lookup-driven and table-driven terms, it is particularly useful when the source of a term is not known in advance.

Underlying Base Objects

The view is defined with a UNION ALL across four SELECT statements. The documented base objects are AP_TERMS (synonym), RA_TERMS (synonym), ORG_FREIGHT (synonym), OKE_TERMS_B (synonym), FND_LOOKUP_VALUES_VL (view), FND_GLOBAL (package), and MTL_PARAMETERS (synonym).

  • AP_TERMS supplies payment terms as AP_PAYMENT_TERMS, keyed by TERM_ID with active-date logic.
  • RA_TERMS supplies receivables payment terms as RA_PAYMENT_TERMS, using the same date-based active calculation.
  • ORG_FREIGHT supplies shipping and freight terms as IB_SHIPPING_METHOD, keyed by organization and freight code, with an ACTIVE flag derived from DISABLE_DATE.
  • OKE_TERMS_B, joined to FND_LOOKUP_VALUES_VL, supplies lookup-driven terms. The join uses VIEW_APPLICATION_ID and LOOKUP_TYPE, and the security group is resolved through FND_GLOBAL.LOOKUP_SECURITY_GROUP to enforce lookup security.
  • MTL_PARAMETERS is referenced in the dependency list, supporting the shipping method branch.

Key Columns

  • TERM_CODE — the term type discriminator (AP_PAYMENT_TERMS, RA_PAYMENT_TERMS, IB_SHIPPING_METHOD, or the OKE term code from OKE_TERMS_B).
  • TERM_VALUE_PK1 / TERM_VALUE_PK2 — the composite primary key parts for the underlying term record (for example TERM_ID, or organization and code).
  • TERM_VALUE — the display value or name of the term.
  • DESCRIPTION — descriptive text for the term.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective date boundaries.
  • ENABLED_FLAG — populated for lookup-based terms from FND_LOOKUP_VALUES_VL.
  • ACTIVE — a computed Y/N indicator comparing SYSDATE against the start and end dates (and DISABLE_DATE for freight terms).

Common Use Cases and Queries

The view is commonly used to enumerate active terms for validation or to resolve a term value to its description in a report. A representative query retrieves all currently active payment terms:

 SELECT TERM_CODE, TERM_VALUE, DESCRIPTION
 FROM APPS.OKE_TERM_VALUES_V
 WHERE TERM_CODE = 'AP_PAYMENT_TERMS'
 AND ACTIVE = 'Y';

For lookup-driven contract terms, filtering by the OKE term code joins the view back to OKE_TERMS_B for additional attributes. Because it is a UNION ALL view without indexes of its own, performance depends on the underlying tables; queries should always include a TERM_CODE predicate to restrict the branches scanned. Direct DML against the view is not supported.