Results for “lns_custom_paymnt_scheds”

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

Overview

The LNS_CUSTOM_PAYMNT_SCHEDS table resides in the LNS schema of Oracle E-Business Suite and is part of the Loans (LNS) product family. It stores user-defined or non-standard amortization schedules associated with a loan contract, complementing the standard payment schedules generated by the Loans engine. Where standard schedules reflect the system-calculated repayment plan, this table captures the custom installment definition that must be honored over the life of the instrument, including principal, interest, fee components, and running balances for each payment period.

From a Data Vault modeling perspective, the FK structure indicates that this object is satellite-leaning. It carries a foreign key to the parent loan record via LOAN_ID, and the timeline and amount columns it holds describe the changing state of that parent entity rather than establishing a new business hub or linking two independent hubs. Modelers should treat it as an attribute satellite of the loan hub.

Key Information Stored

The table contains 43 columns. The most operationally significant are:

• CUSTOM_SCHEDULE_ID — surrogate primary key; enforced by the unique index LNS_CUSTOM_PAYMNT_SCHEDS_U1 and the sole documented business-key candidate.
• LOAN_ID — foreign key linking each custom schedule row to its parent loan in LNS.
• PAYMENT_NUMBER — sequence of the installment within the schedule.
• DUE_DATE — date the payment is due.
• PRINCIPAL_AMOUNT and INTEREST_AMOUNT — the scheduled principal and interest split for the period.
• PRINCIPAL_PAID_TODATE and INTEREST_PAID_TODATE — cumulative amounts applied to date.
• INSTALLMENT_BEGIN_BALANCE and INSTALLMENT_END_BALANCE — opening and closing balances for the period.
• OTHER_AMOUNT and FEE_AMOUNT — ancillary charges and fees attached to the installment.
• CURRENT_TERM_PAYMENT — total contractual payment due for the period.
• PRINCIPAL_PERCENT — percentage share of principal applied in the installment.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), the twenty ATTRIBUTE flex columns, and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

The most frequent reporting requirement is reconstructing the projected cash flow for a loan that uses a custom schedule. A typical query joins the schedule to the loan header and orders installments chronologically:

• Extract the full schedule for a given loan: SELECT PAYMENT_NUMBER, DUE_DATE, CURRENT_TERM_PAYMENT, PRINCIPAL_AMOUNT, INTEREST_AMOUNT FROM LNS_CUSTOM_PAYMNT_SCHEDS WHERE LOAN_ID = :p_loan_id ORDER BY PAYMENT_NUMBER;
• Identify installments past due: compare DUE_DATE against SYSDATE and test PRINCIPAL_PAID_TODATE/INTEREST_PAID_TODATE against the scheduled amounts.
• Projection reporting: aggregate PRINCIPAL_AMOUNT, INTEREST_AMOUNT, and FEE_AMOUNT by DUE_DATE month for cash forecasting.
• Variance analysis: compare custom schedule amounts with the standard schedule to detect manual overrides.
• Period balancing: verify that INSTALLMENT_BEGIN_BALANCE minus principal equals INSTALLMENT_END_BALANCE.

Related Objects

• LNS_CUSTOM_PAYMNT_SCHEDS (self-referencing FK on LOAN_ID) — indicates dependent child rows linked back to the same schedule family.
• Parent loan record in the LNS loan master (joined via LOAN_ID), which supplies contract-level terms such as currency, rate, and maturity.
• Standard Loans schedule tables and views that represent the system-generated amortization plan, useful for reconciliation.
• Transaction and disbursement tables in LNS, joined to confirm amounts actually posted against each PAYMENT_NUMBER.
• GL interface and accounting entry tables that consume PRINCIPAL_AMOUNT, INTEREST_AMOUNT, and FEE_AMOUNT for journal creation.
• Standard concurrent programs and Loans APIs that maintain custom schedules, invoked from the loan servicing forms.