Results for “lns_int_rate_lines”

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

Overview

The LNS_INT_RATE_LINES table is a core transactional structure within the Oracle EBS Loans (LNS) module. It stores the individual interest rate lines that belong to a parent interest rate definition, allowing a single rate record to carry multiple historical or future-dated rate values. This design supports the versioning and effective-dating requirements that are central to loan servicing, where the applicable interest rate on an instrument changes over time as markets move, as repricing dates pass, or as contractual terms are renegotiated.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the LNS schema and is documented with 11 physical columns. Based on the heuristic Data Vault classification mined from its foreign-key structure, the object is characterized as standalone, meaning it does not act as a strongly dependent child through an enforced FK relationship in the mined metadata. As a modeling suggestion, this pattern aligns most closely with a satellite-style structure, since the table records descriptive, dated rate attributes around a parent INTEREST_RATE_ID hub. The classification is heuristic and should be validated against the actual enforced constraints in the target instance.

Key Information Stored

The table captures both the identity of each rate line and its effective-dating attributes. The most significant columns are:

• INTEREST_RATE_LINE_ID — The surrogate primary key, enforced by LNS_INT_RATE_LINES_PK and uniquely indexed by LNS_INT_RATE_LINES_U1. This is the technical identifier for each rate line.
• INTEREST_RATE_ID — The link back to the parent interest rate record, and the primary business-key candidate. Combined with START_DATE_ACTIVE, it forms the UNIQUE_START_DATE business key that prevents duplicate effective dates for the same rate.
• INTEREST_RATE — The actual rate value applicable for the line, expressed as a percentage. This is the principal business attribute of the table.
• START_DATE_ACTIVE — The date from which the rate line becomes effective. This is a business-key candidate and a critical driver for effective-dated queries.
• END_DATE_ACTIVE — The date on which the line ceases to be effective, supporting historical rate reconstruction.

The remaining documented columns are the standard Oracle EBS audit and concurrency attributes: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER. These support WHO-column auditing and optimistic locking rather than business logic.

Common Use Cases and Queries

Typical uses include rate history reporting, effective-rate lookup as of a given date, and reconciliation of rate changes against loan repricing events. A common pattern retrieves the active rate for a parent interest rate on a specific date:

• Effective rate at a point in time: filter START_DATE_ACTIVE <= :as_of_date and (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= :as_of_date), ordered by START_DATE_ACTIVE.
• Full rate timeline: select all lines for a given INTEREST_RATE_ID ordered by START_DATE_ACTIVE to display the evolution of the rate.
• Audit reporting: compare LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent rate maintenance activity.

Because the object is standalone with no enforced incoming FKs in the mined metadata, joins are performed logically on INTEREST_RATE_ID rather than through database-level referential integrity. Reporting queries should therefore validate the parent record explicitly when necessary.

Related Objects

The following objects are most significant in relation to LNS_INT_RATE_LINES:

• Parent interest rate table (LNS interest rates) — joined on INTEREST_RATE_ID, providing the rate definition header that the lines elaborate.
• LNS loan/master contract tables — reference the interest rate definition that ultimately supplies the rate lines for a loan instrument.
• LNS interest rate history/audit structures — parallel records that track rate changes over time.
• LNS_INT_RATE_LINES_PK — the primary key constraint enforcing uniqueness of INTEREST_RATE_LINE_ID.
• LNS_INT_RATE_LINES_U1 — the unique index supporting the business-key candidate on INTEREST_RATE_LINE_ID.

These relationships should be confirmed against the deployed LNS data model, since the heuristic classification indicates no enforced foreign keys were detected in the source metadata.