Search Results okl_index_values




Overview
Explore in AI Chat

Overview

The OKL_INDEX_VALUES table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It functions as the central repository for storing historical and current interest rate values associated with defined financial indices. This table is critical for the accurate calculation of variable interest rates on leases, loans, and other financial instruments managed within the system. By maintaining a time-series record of index values, it enables the system to apply the correct historical or current rate during billing, revenue recognition, and financial reporting cycles, ensuring contractual and accounting compliance.

Key Information Stored

The table's structure is designed to uniquely identify a specific rate value for a given index at a precise point in time. Its primary columns, as indicated by the primary and unique keys, are foundational. The ID column serves as the system-generated primary key for the record. The IDX_ID column is a foreign key that links the value to its parent definition in the OKL_INDICES table, identifying which financial index (e.g., LIBOR, Prime Rate) the value belongs to. The DATETIME_VALID column specifies the exact date and time from which the associated index value becomes effective, establishing the temporal context essential for accurate financial calculations. Additional columns, implied by the table's purpose, would store the actual numeric VALUE of the index and likely metadata such as creation date and last update information.

Common Use Cases and Queries

A primary use case is retrieving the effective index value for a contract on a specific date. For instance, to determine the LIBOR rate (IDX_ID = 100) valid for June 1, 2023, a query would select the value with the latest DATETIME_VALID on or before that date. This logic is central to batch processes that calculate variable interest charges. Reporting use cases include analyzing historical rate trends for a particular index or auditing rate changes over time. A common sample SQL pattern involves joining to OKL_INDICES to get the index name:

  • SELECT idx.NAME, iv.DATETIME_VALID, iv.VALUE
  • FROM OKL_INDEX_VALUES iv, OKL_INDICES idx
  • WHERE iv.IDX_ID = idx.ID
  • AND idx.NAME = 'LIBOR 1-Month'
  • ORDER BY iv.DATETIME_VALID DESC;

This supports both operational and analytical requirements within the leasing and finance lifecycle.

Related Objects

The OKL_INDEX_VALUES table exists within a defined relational schema, with documented dependencies to other key OKL objects. The primary relationship is with the OKL_INDICES table, which holds the master definition of the financial index. The foreign key constraint from OKL_INDEX_VALUES.IDX_ID to OKL_INDICES enforces referential integrity, ensuring every recorded value corresponds to a valid index. Furthermore, this table is referenced by the OKL_FE_STD_RT_TMP_ALL_B table via the column INDEX_ID. This relationship indicates that OKL_INDEX_VALUES provides the base rate data used in processes related to fee and standard rate templates, a core component of the product's pricing and billing engine. The documented primary key constraint IVE_IVE_UK (IDX_ID, DATETIME_VALID) guarantees that no duplicate rate values can exist for the same index and effective datetime.