Search Results okl_var_int_params_v




Overview
Explore in AI Chat

Overview

OKL_VAR_INT_PARAMS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL — Leasing and Finance Management product. It exposes the parameters used to calculate interest for a variable rate contract. In ETRM 12.1.1 and 12.2.2, the view functions as a read-only projection over the variable interest parameter data maintained for lease contracts, allowing concurrent programs, reports, and external integrations to retrieve interest calculation inputs without accessing the base table directly.

The view is recorded as VALID in the data dictionary. It presents a single flat result set combining identification keys, interest rate attributes, calculation dates, method codes, principal balances, and the standard EBS WHO columns. Because the definition is a straight SELECT from the base object with no joins or filters, it does not alter the grain of the underlying data; each row of the view corresponds to one row of OKL_VAR_INT_PARAMS. The CALC_METHOD_CODE column, which the user searched for, is the field that determines how interest is calculated (for example simple versus compounded treatment) across the interest calculation window defined by the start and end date columns.

Underlying Base Objects

The documented view definition selects exclusively from OKL_VAR_INT_PARAMS, aliased as VIR. In the delivered environment, OKL_VAR_INT_PARAMS is exposed under the APPS schema as a synonym pointing to the OKL base table that physically stores variable interest parameter records. The view adds no additional tables, outer joins, or lookup translations; therefore, its rows and columns are a direct superset presentation of the base table plus the ROWID pseudo-column.

  • OKL_VAR_INT_PARAMS — the sole documented base object, referenced through the APPS synonym.
  • VIR — the alias applied in the view text, retained as ROW_ID via VIR.ROWID.

Because no filtering predicate is applied, all rows in the base table, including those flagged by VALID_YN, are returned by the view. Consumers must apply validity filters explicitly when only active parameters are required.

Key Columns

Common Use Cases and Queries

Typical usage includes verifying variable rate parameters entered for a contract, reconciling calculated interest against contract balances, and extracting calculation inputs for external reporting. The CALC_METHOD_CODE is frequently used to group or audit contracts by calculation method.

  • Retrieve all active parameters for a contract:
    SELECT id, khr_id, interest_rate, calc_method_code, principal_balance FROM okl_var_int_params_v WHERE khr_id = :contract_id AND valid_yn = 'Y';
  • List parameters by calculation method within an operating unit:
    SELECT calc_method_code, COUNT(*), SUM(interest_amt) FROM okl_var_int_params_v WHERE org_id = :org_id GROUP BY calc_method_code;
  • Inspect the calculation window and days for a parameter row:
    SELECT id, interest_calc_start_date, interest_calc_end_date, interest_calc_days, interest_rate FROM okl_var_int_params_v WHERE id = :param_id;
  • Audit recently changed parameter records:
    SELECT id, khr_id, last_updated_by, last_update_date FROM okl_var_int_params_v WHERE last_update_date >= SYSDATE - 7;

Because the view exposes ROW_ID and OBJECT_VERSION_NUMBER, it is also suitable for integrations that require row-level identification or version checking before updates are applied to the base table through supported APIs.