Search Results okl_var_int_params




Overview

OKL_VAR_INT_PARAMS is a configuration table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. Its documented description identifies it as the "Variable Rate parameters table," indicating that it stores the control and setup attributes governing how variable (floating) interest rates are calculated, applied, and validated against lease and finance contracts. In lease management, contracts frequently reference interest rates that are not fixed for the full term; the parameters held in this table determine how those rates are derived from external index sources, how frequently they are reset, and how the resulting values flow into contract pricing and billing.

The ETRM metadata classifies this object as standalone under a heuristic Data Vault modeling suggestion. This classification implies that OKL_VAR_INT_PARAMS functions as an independent reference entity rather than a transactional link or dependent satellite. In Data Vault terms, it behaves most like a hub or a standalone reference table, with its own primary key and no documented foreign-key dependencies on other tables in the mined relationship data. Practically, this means the table is a self-contained source of parameter definitions consumed by other processes rather than a table that aggregates or references transactions elsewhere.

Key Information Stored

The primary key is documented as OKL_VIR_PK, which is attributed to the ID column. This surrogate key uniquely identifies each parameter row. The metadata does not document additional unique business-key indexes, so the specific descriptive attributes that would serve as natural-key candidates are not enumerated in the available source. Based on the object's role as a variable rate parameters table, the most significant columns to expect include:

  • ID — the surrogate primary key (OKL_VIR_PK) that uniquely identifies each parameter record.
  • Index or rate source identifiers — references to the underlying index or benchmark from which the variable rate is drawn.
  • Rate type and reset frequency parameters — attributes controlling how often a rate is refreshed and the method used to determine each reset value.
  • Margin, spread, or floor/cap parameters — the adjustments applied on top of an index rate and the limits governing the final applied rate.
  • Effective date and active status attributes — date-range and enablement controls that determine when a given parameter set is valid.

Because the ETRM record states that this object is "not implemented in this database," the definitive column inventory must be confirmed against the actual target instance; the entries above reflect the functional expectations of a variable rate parameters table rather than columns enumerated in the supplied metadata, which names only ID.

Common Use Cases and Queries

Typical scenarios involving OKL_VAR_INT_PARAMS include setting up and maintaining the parameter definitions used when contracts reference floating rates, verifying which parameter set was active for a given period, and auditing how a particular index or spread configuration was applied. Reporting use cases focus on rate configuration review, effective-dating checks, and impact analysis before changing a parameter value.

A representative pattern to retrieve parameter definitions by key is:

  • SELECT id, ... FROM okl_var_int_params WHERE id = :p_id;

To examine currently effective parameters, a date-range predicate on the effective date columns is commonly used. When the table is absent in a given environment — as the metadata notes — the query returns no rows, confirming that the object has not been deployed or has been superseded by an alternative configuration mechanism.

Related Objects

The mined FK structure classifies the table as standalone, so no direct parent or child foreign-key relationships are documented. Where this object is most likely surfaced is through the surrounding OKL interest and rate-processing objects that consume parameter definitions rather than through enforced constraints. Relevant companion objects to review include:

  • Variable and index rate definition tables within the OKL module that supply the underlying benchmark values.
  • Lease contract and contract line tables that reference variable rate terms.
  • Stream and billing schedule objects that consume the calculated rate for invoicing.
  • OKL interest calculation and concurrent programs that evaluate the parameters at runtime.
  • OKL setup or lookup objects providing list-of-values for rate source and reset configuration.

Because the documented relationship data is limited, these associations should be validated by querying the target database's constraints and dependencies before relying on any specific join column.