Search Results int_cash




Overview
Explore in AI Chat

Overview

APPS.LNS_AMORTIZATION_SCHEDULES_V is a reporting view within the Oracle Lease and Loan Management (LNS) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The view exposes the amortization schedule detail underlying a loan or lease contract, presenting the periodic payment structure alongside billed, paid, credited, and adjusted amounts for principal, interest, and fees. It is registered under FND Design Data as LNS.LNS_AMORTIZATION_SCHEDULES_V and carries a status of VALID. Oracle classifies the object as Internal, and the standard warning applies: Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. The view is therefore intended for reporting, integration, and diagnostic use in conjunction with, rather than in replacement of, supported application flows.

Because the view combines schedule amounts with receivable-side aggregation, it is a common target for queries that reconcile contract billing activity against the underlying amortization plan.

Underlying Base Objects

The view is defined over a small set of LNS and Oracle Receivables objects, joined and supplemented by lookup and session-context sources:

  • LNS_AMORTIZATION_SCHEDS (synonym) — the primary amortization schedule table supplying payment number, due date, principal, interest, and fee amounts, paid and adjustment columns, remaining balances, and reversal attributes.
  • LNS_LOAN_HEADERS_ALL (synonym) — the loan header, supplying contract-level attributes such as loan status, currency, organization, and legal entity.
  • AR_PAYMENT_SCHEDULES_ALL (synonym) — the Receivables payment schedule, contributing billed and receivable amounts.
  • AR_RECEIVABLE_APPLICATIONS_ALL (synonym) — receivable application activity that drives applied and paid amounts and the last applied date.
  • FND_LOOKUPS (view) and LNS_LOOKUPS (view) — supply the descriptive values for lookup-backed columns such as reversal reason and bill type.
  • FND_GLOBAL (package) — supplies the runtime session context used for organization (ORG_ID) and related security filtering.

Key Columns

The view exposes the full amortization schedule structure. Core identifiers include LOAN_ID, AMORTIZATION_SCHEDULE_ID, PAYMENT_NUMBER, and PARENT_AMORTIZATION_ID. Schedule amounts are split across PRINCIPAL_AMOUNT, INTEREST_AMOUNT, and FEE_AMOUNT, with corresponding paid columns (PRINCIPAL_PAID, INTEREST_PAID, FEE_PAID) and remaining balances (PRINCIPAL_REMAINING, INTEREST_REMAINING, FEE_REMAINING).

The credit and adjustment columns decompose each component into cash, loan payment credit, net credit, other credit, credit, and adjustment buckets — for example PRIN_CASH, PRIN_LOAN_PMT_CREDIT, PRIN_NET_CREDIT, PRIN_OTHER_CREDIT, PRIN_CREDIT, and PRIN_ADJ — with equivalent sets for interest (INT_*) and fees (FEE_*).

Of particular interest to users searching on total_ar_billed_amount, the view exposes TOTAL_BILLED_AMOUNT, TOTAL_AR_BILLED_AMOUNT, and TOTAL_REMAINING_AMOUNT, along with FUNDED_AMOUNT and PRINCIPAL_BALANCE. TOTAL_AR_BILLED_AMOUNT represents the cumulative amount billed and recorded on the receivables side for the schedule line, as distinct from the internally billed total. Supporting columns include DUE_DATE, LAST_APPLIED_DATE, REVERSED_CODE and REVERSED_DESC, BILL_TYPE_CODE and BILL_TYPE_DESC, CREDIT_ENABLED_CODE, REBILL_ENABLED_CODE, the transaction identifiers PRINCIPAL_TRX_ID, INTEREST_TRX_ID, and FEE_TRX_ID, LOAN_STATUS, ORG_ID, CURRENCY, LEGAL_ENTITY_ID, PHASE, and the STATEMENT_XML CLOB.

Common Use Cases and Queries

Typical uses include reconciling billed versus amortized amounts, analyzing credit and adjustment activity, auditing reversal and rebill behavior, and feeding downstream reporting or integration extracts. A representative query for the searched column follows:

  • Reconcile billed amounts per schedule line:
    SELECT loan_id, amortization_schedule_id, payment_number, due_date, total_billed_amount, total_ar_billed_amount, total_remaining_amount FROM apps.lns_amortization_schedules_v WHERE loan_id = :p_loan_id ORDER BY payment_number;
  • Identify schedules with a gap between billed and AR-billed totals:
    SELECT loan_id, amortization_schedule_id, total_billed_amount, total_ar_billed_amount FROM apps.lns_amortization_schedules_v WHERE NVL(total_ar_billed_amount,0) <> NVL(total_billed_amount,0);
  • Summarize billed, paid, and remaining balances by contract:
    SELECT loan_id, SUM(total_ar_billed_amount) ar_billed, SUM(principal_paid + interest_paid + fee_paid) paid, SUM(principal_remaining + interest_remaining + fee_remaining) remaining FROM apps.lns_amortization_schedules_v GROUP BY loan_id;

All queries should apply the appropriate ORG_ID or legal entity filter consistent with the caller's FND_GLOBAL session context, given the internal classification of the object.