Results for “interest_calculation_method”

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 integration object within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. Its stated purpose is to present "Variable Interest Rate Information," consolidating the parameters that govern variable-rate interest calculation on lease and finance contracts. The view exposes interest calculation periods, interest rates, calculated interest amounts, and descriptive lookup values in a single flattened structure, which simplifies downstream reporting and integration consumption by hiding the join logic required to resolve coded lookup values.

Because it is a view and not a base table, it carries no independent storage; it is a read-only projection defined over the variable interest parameter table and supporting reference objects. In ETRM 12.1.1 and 12.2.2, such _UV (user view) objects are typically surfaced through Oracle Forms, OAF pages, and Business Intelligence Publisher extracts. The user search term INTEREST_AMOUNT corresponds directly to a projected column of this view, indicating that users commonly locate this object when searching for calculated interest figures tied to variable-rate contracts.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKL_VAR_INT_PARAMS (SYNONYM) — the primary table holding variable interest parameters, aliased as VAR. It supplies the calculation dates, method code, rate, amount, source identifier, and KHR identifier.
• OKL_TRX_AR_INVOICES_B (SYNONYM) — the transaction/receivables invoice base table, aliased as HDR, joined via an outer join on VAR.SOURCE_ID = HDR.ID.
• FND_LOOKUPS (VIEW) — the standard Oracle lookup view, aliased as LKP. It is filtered to LOOKUP_TYPE = 'OKL_BPD_VAR_RATE_CALC_CODE' to translate the calculation method code into a user-facing meaning.
• FND_GLOBAL (PACKAGE) — listed as a referenced object, typically providing session context such as organization and responsibility identifiers used for security or defaulting within the surrounding OKL logic.

The primary relationship is a left outer join from the variable interest parameters to the invoice header, ensuring that parameter rows are retained even when no corresponding invoice header exists. The lookup join resolves the CALC_METHOD_CODE into its descriptive meaning.

Key Columns

• DATE_FROM — mapped from VAR.INTEREST_CALC_START_DATE; the start of the interest calculation period.
• DATE_TO — mapped from VAR.INTEREST_CALC_END_DATE; the end of the interest calculation period.
• COMPOSITE — a derived flag that returns 'Y' when the calculation method code is 'REAMORT', otherwise 'N', indicating a composite/reamortizing calculation.
• INTEREST_CALCULATION_METHOD — the descriptive meaning resolved from FND_LOOKUPS for the calculation code.
• INTEREST_CALC_MTHD_CODE — the raw calculation method code from the parameter table.
• INTEREST_RATE — the variable interest rate applied for the period.
• INTEREST_AMOUNT — mapped from VAR.INTEREST_AMT; the calculated interest amount, which is the column most frequently sought by users.
• KHR_ID — the key identifier linking the parameter record to its associated contract or header context.

Common Use Cases and Queries

Typical uses include reconciling variable interest amounts against receivables invoices, auditing rate periods for a contract, and feeding interest data into custom reports or integrations. A representative query follows.

• Retrieve all interest periods and amounts for a contract: SELECT DATE_FROM, DATE_TO, INTEREST_RATE, INTEREST_AMOUNT, INTEREST_CALCULATION_METHOD FROM APPS.OKL_CS_VARIABLE_INT_RATE_UV WHERE KHR_ID = :khr_id ORDER BY DATE_FROM;
• Filter to composite (reamortizing) calculations only: SELECT KHR_ID, DATE_FROM, INTEREST_AMOUNT FROM APPS.OKL_CS_VARIABLE_INT_RATE_UV WHERE COMPOSITE = 'Y';
• Aggregate periodic interest by contract: SELECT KHR_ID, SUM(INTEREST_AMOUNT) TOTAL_INT FROM APPS.OKL_CS_VARIABLE_INT_RATE_UV GROUP BY KHR_ID;

Because the view already resolves lookup meanings and applies the outer join, it is preferable to querying the base parameter table directly, reducing the need to replicate join and decode logic in custom reports.