Results for “okl_bpd_var_rate_calc_code”

15 results




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

Overview

The view APPS.OKL_CS_VARIABLE_INT_RATE_UV is a reporting and inquiry object within the Oracle E-Business Suite Lease and Finance Management (ETRM) module. It exposes the variable interest rate parameters captured against lease and loan contracts, presenting them in a form suitable for user-facing queries and integration extracts. Its primary role is to resolve the variable interest calculation method stored on each parameter record into a human-readable meaning by joining to the FND_LOOKUPS view, while simultaneously exposing the associated accounts receivable invoice header where one exists.

The view is a logical presentation layer: it does not store data itself but derives every row from the parameter table, decorates it with lookup meaning, and links it to the corresponding AR invoice. Because the lookup condition on OKL_BPD_VAR_RATE_CALC_CODE is applied with an inner join, records whose calculation method code is not defined in that lookup type are excluded from the result set.

Underlying Base Objects

The view is defined over three referenced objects, all resolved through APPS synonyms:

  • OKL_VAR_INT_PARAMS — the primary source table, aliased as VAR. It supplies the interest calculation start and end dates, the calculation method code, the interest rate, the interest amount, the source identifier, and the knowledge base record identifier (KHR_ID).
  • OKL_TRX_AR_INVOICES_B — aliased as HDR, the AR invoice header table. It is joined with an outer join (VAR.SOURCE_ID = HDR.ID(+)), so parameter rows are returned even when no matching invoice header exists.
  • FND_LOOKUPS — aliased as LKP, joined on LOOKUP_TYPE = 'OKL_BPD_VAR_RATE_CALC_CODE' and LOOKUP_CODE = VAR.CALC_METHOD_CODE to translate the stored code into its printed meaning.
  • FND_GLOBAL — a package referenced by the view definition, typically for session and context resolution such as organization or user identifiers.

Key Columns

  • DATE_FROM — the interest calculation start date (INTEREST_CALC_START_DATE).
  • DATE_TO — the interest calculation end date (INTEREST_CALC_END_DATE).
  • COMPOSITE — a derived flag ('Y'/'N') set to 'Y' when the calculation method code is REAMORT, indicating a re-amortization style calculation rather than a simple rate update.
  • INTEREST_CALCULATION_METHOD — the lookup meaning corresponding to the stored calculation method code.
  • INTEREST_CALC_MTHD_CODE — the raw calculation method code (CALC_METHOD_CODE) as stored on the parameter record.
  • INTEREST_RATE — the variable interest rate applied for the period.
  • INTEREST_AMOUNT — the monetary interest amount (INTEREST_AMT) associated with the parameter record.
  • KHR_ID — the identifier linking the parameter row to its originating knowledge base / contract record.

Common Use Cases and Queries

Typical usage centres on reconstructing the interest schedule for a contract, auditing which calculation methods were applied, and reconciling variable interest parameters against invoiced amounts. A representative query follows:

  • SELECT khr_id, date_from, date_to, interest_calc_mthd_code, interest_calculation_method, composite, interest_rate, interest_amount FROM apps.okl_cs_variable_int_rate_uv WHERE khr_id = :p_khr_id ORDER BY date_from;
  • Filtering on composite = 'Y' isolates re-amortization parameter lines for a contract.
  • Joining the view back to the contract or AR invoice using KHR_ID and SOURCE_ID supports interest-to-invoice reconciliation reporting.

Because the lookup join is mandatory, any new calculation method code must be defined under OKL_BPD_VAR_RATE_CALC_CODE before its parameter rows become visible through this view.