Search Results okl_k_rate_params




Overview
Explore in AI Chat

Overview

OKL_K_RATE_PARAMS is a transaction table within the OKL (Leasing and Finance Management) schema of Oracle E-Business Suite. It stores the interest rate parameters associated with a lease contract, keyed to a contract header identified by KHR_ID. Each row represents a dated configuration of interest calculation attributes — such as base rate, index reference, adder, floors and ceilings, compounding behavior, and conversion options — that the leasing engine consumes when generating interest schedules, amortization, and cash flow projections.

Because the table records parameters effective across defined date ranges, it supports the re-rating, repricing, and conversion logic required for variable-rate and adjustable leases. Under a Data Vault modeling heuristic mined from the foreign key structure, OKL_K_RATE_PARAMS classifies as a standalone object — neither hub, link, nor satellite by derivation. This suggests that, absent documented parent-child foreign keys within the OKL schema, the table is best treated as a self-contained transaction entity referenced through its business key rather than as a strictly dependent child in a normalized hierarchy.

Key Information Stored

The primary key is the composite OKL_K_RATE_PARAMS_PK, defined on PARAMETER_TYPE_CODE, EFFECTIVE_FROM_DATE, and KHR_ID. A unique index, OKL_K_RATE_PARAMS_U1, covers KHR_ID, PARAMETER_TYPE_CODE, and EFFECTIVE_FROM_DATE, making this triplet the principal business-key candidate. The surrogate composite PK and this unique index are functionally aligned, so the business key effectively serves as the identifying key.

The most consequential columns include:

Fifteen ATTRIBUTE columns provide a DESCRIPTIVE flexfield for client-specific extensions.

Common Use Cases and Queries

Typical reporting includes retrieving the currently effective rate parameters for a contract, auditing rate history, and validating schedule generation inputs. A representative query returns the active parameter row for a given contract:

  • Select PARAMETER_TYPE_CODE, BASE_RATE, ADDER_RATE, EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE FROM OKL_K_RATE_PARAMS WHERE KHR_ID = :p_khr_id AND TRUNC(SYSDATE) BETWEEN EFFECTIVE_FROM_DATE AND NVL(EFFECTIVE_TO_DATE, TRUNC(SYSDATE));
  • Join to the contract header on KHR_ID to report rate parameters alongside contract terms.
  • Aggregate MAXIMUM_RATE and MINIMUM_RATE prevalence across a portfolio for risk reporting.
  • Analyze RATE_CHANGE_FREQUENCY_CODE distributions to assess exposure to scheduled repricing.

Related Objects

Because the FK structure was mined as standalone, dependency is expressed primarily through the contract header identifier rather than enforced parent-child constraints. The most significant related objects include:

  • Contract header table (referenced via KHR_ID) — the parent contractual record each parameter row attaches to.
  • Interest index reference (via INTEREST_INDEX_ID) — supplies the external index used to derive floating rates.
  • Calculation formula reference (via CALCULATION_FORMULA_ID) — the formula definition invoked during rate computation.
  • Lease stream/schedule generation tables — consume these parameters to build amortization and cash flow lines.
  • Contract conversion tables — interact with CONVERSION_OPTION_CODE and NEXT_CONVERSION_DATE during rate conversion processing.

These objects are joined on KHR_ID and the respective coded foreign keys, forming the working set for lease interest processing in Oracle Leasing and Finance Management.