Results for “ive_ive_uk”

6 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_INDEX_VALUES is a transaction and reference table in the OKL (Lease and Finance Management) schema of Oracle E-Business Suite, holding the time-phased interest rate values associated with interest rate indices. In Oracle Lease and Finance Management (OLFM), index values underpin variable-rate lease contracts, where the periodic reset of an interest rate index drives billing, accrual, and revaluation calculations. Each row captures the value of a given index as of a specific valid date, allowing the application to retrieve the prevailing rate for any effective period.

From a Data Vault modeling perspective, the documented foreign key structure suggests this object is satellite-leaning. Its grain is defined by the composite of an index identifier and a validity timestamp, with each row recording a measurable attribute (the rate value) that changes over time but remains tied to a stable parent, OKL_INDICES. This heuristic classification treats OKL_INDICES as the hub-like anchor and OKL_INDEX_VALUES as the time-variant satellite carrying the descriptive rate data. Secondary referencing tables hold additional transactional detail, which is consistent with a dependent satellite or link-adjacent role.

Key Information Stored

The table contains fifteen documented columns. The most significant are:

The surrogate key (ID) is distinct from the business-key candidates exposed by the unique indexes: IDX_ID plus DATETIME_VALID defines the natural uniqueness of a rate observation, while ID provides the technical row identifier used by foreign-key references.

Common Use Cases and Queries

Typical scenarios include retrieving the effective rate for a variable-rate contract on a billing date, auditing rate history for a given index, and reconciling rate changes against contracts. A common pattern joins the value table to its parent index and filters on the validity window:

  • Retrieve the current rate for an index: SELECT VALUE FROM OKL_INDEX_VALUES WHERE IDX_ID = :p_idx AND TRUNC(DATETIME_VALID) <= TRUNC(SYSDATE) AND (DATETIME_INVALID IS NULL OR TRUNC(DATETIME_INVALID) > TRUNC(SYSDATE));
  • List full rate history for an index: SELECT IDX_ID, DATETIME_VALID, DATETIME_INVALID, VALUE FROM OKL_INDEX_VALUES WHERE IDX_ID = :p_idx ORDER BY DATETIME_VALID;
  • Join to the index master for reporting: SELECT i.INDEX_CODE, v.DATETIME_VALID, v.VALUE FROM OKL_INDEX_VALUES v, OKL_INDICES i WHERE v.IDX_ID = i.ID AND v.DATETIME_VALID BETWEEN :from_dt AND :to_dt;
  • Trace values loaded by a specific concurrent request: SELECT * FROM OKL_INDEX_VALUES WHERE REQUEST_ID = :p_request_id;

Related Objects

  • OKL_INDICES — parent index master; joined on OKL_INDEX_VALUES.IDX_ID = OKL_INDICES.ID (documented foreign key).
  • OKL_FE_STD_RT_TMP_ALL_B — temporary/standard rate staging table that references OKL_INDEX_VALUES via its INDEX_ID column (documented foreign key).
  • OKL_INDEX_VALUES_PK — primary key constraint on ID.
  • OKL_INDEX_VALUES_U1 — unique index on ID.
  • OKL_INDEX_VALUES_U2 / IVE_IVE_UK — unique business-key constraint on IDX_ID and DATETIME_VALID.
  • OKL_INDEX_VALUES_N1-style access paths on IDX_ID and DATETIME_VALID would typically support validity-window lookups (inferred, not documented).
  • OKL_INDICES_B / OKL_INDICES_TL — index master and translation tables commonly used alongside this object in reporting (inferred).