Search Results okl_opt_values_v




Overview
Explore in AI Chat

Overview

OKL_OPT_VALUES_V is a validity (V) view in the Oracle Lease and Finance Management (OKL) product family of Oracle E-Business Suite. Its documented purpose in the ETRM 12.2.2 metadata is to expose the values that can be associated with an option. In the OKL contract and lease authoring model, an option represents a contractual right or election available to a party on a lease or financing agreement — for example a purchase option, a renewal or extension option, a termination option, or a rate-related election. Each option may be presented to the user with a discrete set of allowable values, and OKL_OPT_VALUES_V is the reporting and integration surface through which those allowable values are published.

The view is owned by the APPS schema and is marked VALID. Because it is a view rather than a table, it stores no data of its own; it is a stable, read-only projection intended for queries, concurrent programs, Discoverer/BI Publisher reports, and external integration extracts. The leading "V" suffix follows the standard Oracle EBS convention for a view, and the "_V" object is the recommended reference point rather than the underlying base table.

Underlying Base Objects

The documented view definition reads exclusively from OKL_OPT_VALUES (referenced through a synonym), aliased as OVEB. The ETRM metadata lists OKL_OPT_VALUES (SYNONYM) as the single referenced base object. The view text is a straightforward column projection with no joins, unions, or aggregation:

Because no filtering predicate or join is applied, OKL_OPT_VALUES_V returns exactly the rows present in OKL_OPT_VALUES, with a renamed ROWID column. OKL_OPT_VALUES is the child of the option definition (keyed by OPT_ID, which points to the parent option entity in the OKL option setup model), and OBJECT_VERSION_NUMBER indicates that the base table participates in Oracle's optimistic locking (OAF/ADF row versioning) framework.

Key Columns

  • ROW_ID — The base table ROWID, exposed for row-level identification and lock-aware processing.
  • ID — Primary identifier of the individual option value record.
  • OBJECT_VERSION_NUMBER — Optimistic locking / version stamp for the row.
  • OPT_ID — Foreign key to the parent option definition; this is the column used to join an option to its permitted values.
  • VALUE — The option value itself, i.e. the discrete value that may be selected when the option is exercised or configured.
  • DESCRIPTION — Descriptive text explaining the value in user-facing terms.
  • FROM_DATE / TO_DATE — Effective date range during which the value is valid, supporting date-effective option configuration.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns (last-update login uses the LAST_UPDATE_LOGIN alias).

Common Use Cases and Queries

Typical uses include populating option value lists in lease authoring, validating contract option inputs, feeding BI Publisher reports that display allowed option values, and extracting setup data during data conversion or migration.

List values for a specific option:

SELECT id, opt_id, value, description, from_date, to_date
FROM   apps.okl_opt_values_v
WHERE  opt_id = :p_opt_id
ORDER  BY value;

Retrieve only currently effective values (SYSDATE prototype):

SELECT v.opt_id, v.value, v.description
FROM   apps.okl_opt_values_v v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(v.from_date, TRUNC(SYSDATE))
                          AND NVL(v.to_date, TRUNC(SYSDATE));

Audit recent setup changes:

SELECT id, opt_id, value, last_updated_by, last_update_date
FROM   apps.okl_opt_values_v
WHERE  last_update_date >= :p_since
ORDER  BY last_update_date DESC;

Queries should be executed with the APPS schema context or via a synonym granted to the reporting user; because the view is read-only, DML must be directed to OKL_OPT_VALUES through the supported OKL application APIs.