Results for “begin_installment_number”

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

Overview

The LNS.LNS_RATE_SCHEDULES table is a core transactional data object within the Oracle E-Business Suite LNS – Loans module. It stores the loan interest rate schedule, capturing the rate terms, spread, index references, and effective date ranges that define how interest accrues on a loan or loan term over its life. Each row associates a rate configuration with a specific loan TERM_ID, allowing multiple rate periods and installment ranges to coexist for a single loan. In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the LNS schema and is classified as VALID.

From a dimensional modeling perspective, the mined foreign key structure suggests this object is satellite-leaning — that is, it functions as a dependent attribute table hanging off a parent term entity (TERM_ID), rather than acting as an independent hub or an associative link. This classification is a heuristic modeling suggestion, not a declared Oracle designation.

Key Information Stored

The table contains 19 documented columns. The most significant are:

• RATE_ID — Surrogate primary key, enforced by LNS_RATE_SCHEDULES_PK and the unique index LNS_RATE_SCHEDULES_U1.
• TERM_ID — Foreign key linking the rate schedule to its parent loan term.
• INDEX_RATE and INDEX_DATE — The underlying benchmark rate and the date on which it is observed.
• SPREAD — The margin applied to the index rate to derive the effective rate.
• CURRENT_INTEREST_RATE — The active interest rate for the schedule line.
• FLOATING_FLAG — Indicates whether the rate floats against an index or is fixed.
• INTEREST_ONLY_FLAG — Marks interest-only periods within the schedule.
• BEGIN_INSTALLMENT_NUMBER and END_INSTALLMENT_NUMBER — The installment range to which the rate applies.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective date boundaries for the rate line.
• PHASE — Distinguishes rate phases within a term.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit and concurrency columns.

Business-key candidates are defined by unique indexes LNS_RATE_SCHEDULES_U2 (TERM_ID, BEGIN_INSTALLMENT_NUMBER, START_DATE_ACTIVE, END_DATE_ACTIVE, PHASE) and LNS_RATE_SCHEDULES_U3 (TERM_ID, END_INSTALLMENT_NUMBER, START_DATE_ACTIVE, END_DATE_ACTIVE, PHASE). These distinguish the surrogate key from the natural business key.

Common Use Cases and Queries

Typical reporting scenarios include identifying floating-rate exposure, auditing spread changes over time, and reconciling accrued interest to scheduled rates. A common query retrieves active rate lines for a term:

• Filter by TERM_ID and a date between START_DATE_ACTIVE and END_DATE_ACTIVE to find the current rate.
• Group by FLOATING_FLAG to report fixed versus floating loan portfolios.
• Join INDEX_RATE plus SPREAD to reconstruct the effective rate when CURRENT_INTEREST_RATE is stale.
• Use BEGIN_INSTALLMENT_NUMBER / END_INSTALLMENT_NUMBER to align rates with amortization schedules.

A representative SQL pattern: SELECT RATE_ID, TERM_ID, CURRENT_INTEREST_RATE, FLOATING_FLAG FROM LNS.LNS_RATE_SCHEDULES WHERE TERM_ID = :term_id AND TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);

Related Objects

The most significant related objects, based on the documented foreign key and relationship data, include:

• LNS_RATE_SCHEDULES self-referencing relationship via TERM_ID, anchoring each rate row to its term parent.
• The parent loan term table referenced through LNS_RATE_SCHEDULES.TERM_ID, which governs the loan’s installment structure.
• Loan interest accrual and transaction tables in the LNS schema that consume CURRENT_INTEREST_RATE.
• Index rate source tables providing INDEX_RATE and INDEX_DATE values.
• Standard EBS audit/WHO columns linking to FND user tables via CREATED_BY and LAST_UPDATED_BY.

Note that the metadata supplied references only LNS_RATE_SCHEDULES.TERM_ID as an explicit foreign key, so downstream dependencies should be confirmed against the deployed 12.2.2 schema before reporting use.