Search Results okl_index_values_v




Overview
Explore in AI Chat

Overview

OKL_INDEX_VALUES_V is a reporting view in the Oracle E-Business Suite (EBS) Lease and Finance Management module (OKL), owned by the APPS schema. Its documented purpose is to expose interest rate values maintained within the OKL interest rate index framework. In Oracle Lease and Finance Management, interest rate indices (such as a prime rate index or a reference rate) are stored as a series of dated values that vary over time. The view provides read access to those dated value records, including their effective and expiration dates, so that downstream processes, reports, and integrations can determine the applicable interest rate for a given index on a given date.

The object is a simple pass-through (projection) view rather than a complex join. It selects all columns from a single underlying object and adds a ROWID alias, meaning it presents an unfiltered, denormalized read of the base table. This makes it suitable for concurrent program extracts, custom reports, and interface queries where the rate value history for a lease index is required.

Underlying Base Objects

The view is defined over a single base object: OKL_INDEX_VALUES, referenced through a synonym in the APPS schema. The view text confirms this with a straightforward SELECT of all columns from OKL_INDEX_VALUES (aliased IVEB), adding only a ROW_ID column derived from the base table ROWID. Because the view introduces no joins, filtering, or aggregation, it returns exactly the same row set as the base table, with column names preserved. This design means the view carries no independent logic — changes to the base table structure or data flow directly into the view. In implementation terms, the synonym OKL_INDEX_VALUES resolves to the OKL schema table that stores the transactional interest rate value records.

Key Columns

  • ROW_ID — The base table ROWID, exposed for uniquely identifying a row within the view.
  • ID — Primary identifier of the index value record.
  • OBJECT_VERSION_NUMBER — Optimistic locking/versioning column used by the OKL framework for concurrent update control.
  • IDX_ID — Foreign key to the interest rate index definition to which this value belongs. This links the value to a specific index.
  • VALUE — The actual interest rate value (the rate number) effective for the associated index over the validity interval.
  • DATETIME_VALID — The date/time from which the value becomes effective.
  • DATETIME_INVALID — The date/time at which the value ceases to be effective.
  • PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, PROGRAM_UPDATE_DATE — Standard concurrent program audit columns indicating which program last touched the record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "WHO" audit columns recording creation and last modification details.

Common Use Cases and Queries

Typical uses include reporting historical rate movements for an index, resolving the rate applicable on a contract date, and building interfaces that export rate values to external pricing or treasury systems. A representative query retrieving all values for a specific index ordered by effective date is:

SELECT idx_id, value, datetime_valid, datetime_invalid FROM okl_index_values_v WHERE idx_id = :index_id ORDER BY datetime_valid;

To find the rate effective on a particular date, a query constrains the validity interval:

SELECT value FROM okl_index_values_v WHERE idx_id = :index_id AND :as_of_date BETWEEN datetime_valid AND NVL(datetime_invalid, :as_of_date + 1);

Because the view is unfiltered, standard predicates on IDX_ID, VALUE, and the validity dates provide the primary selectivity. Audit columns support impact analysis and troubleshooting of rate changes, while OBJECT_VERSION_NUMBER supports programmatic update logic in custom extensions.