Search Results lns_loan_lines




Overview
Explore in AI Chat

Overview

LNS_LOAN_LINES is a transactional table in the Oracle E-Business Suite Loans (LNS) module, holding the individual line-level records that comprise a loan or loan-related financial instrument. Within the LNS schema, the table functions as the granular detail layer beneath a loan header, capturing references, amounts, payment schedules, installment information, approval or rejection activity, and adjustment data. It is populated and maintained primarily through the Loans origination, funding, and servicing flows in Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined foreign key structure classifies this table heuristically as standalone — that is, the column set does not exhibit the classic hub-and-link partitioning expected of a fully normalized Data Vault design. In practice, this means LNS_LOAN_LINES behaves less like a pure hub or link and more like a transactional or satellite-style record whose rows are anchored by the LOAN_LINE_ID surrogate key and whose descriptive and numeric attributes are subject to update over the loan lifecycle, as evidenced by columns such as LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER, and ADJUSTMENT_DATE.

Key Information Stored

The table is defined with a documented physical schema of 24 columns. The most significant columns for integration and reporting purposes include:

The standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide audit trail attributes.

Common Use Cases and Queries

Typical reporting scenarios include retrieving all lines for a given loan, reconciling requested versus reference amounts, and auditing approval or rejection activity. A representative query joining lines to their parent loan is:

  • SELECT ll.LOAN_LINE_ID, ll.LOAN_ID, ll.REQUESTED_AMOUNT, ll.STATUS FROM LNS.LNS_LOAN_LINES ll WHERE ll.LOAN_ID = :p_loan_id;
  • SELECT LOAN_ID, SUM(REQUESTED_AMOUNT) FROM LNS.LNS_LOAN_LINES GROUP BY LOAN_ID;
  • SELECT LOAN_LINE_ID, APPR_REJECT_BY, APPR_REJECT_DATE FROM LNS.LNS_LOAN_LINES WHERE APPR_REJECT_DATE IS NOT NULL;
  • SELECT LOAN_LINE_ID, INSTALLMENT_NUMBER, END_DATE FROM LNS.LNS_LOAN_LINES WHERE PAYMENT_SCHEDULE_ID = :p_schedule_id ORDER BY INSTALLMENT_NUMBER;

Adjustment reporting commonly filters on ORIGINAL_FLAG and ADJUSTMENT_DATE to separate original lines from restructured ones, while the REC_ADJUSTMENT_ID and REC_ADJUSTMENT_NUMBER columns support receipt-level reconciliation.

Related Objects

The following objects are most significant to working with LNS_LOAN_LINES, based on the primary key, foreign key, and reference structure documented above:

  • LNS_LOAN_HEADERS (or the parent loan table) — joined on LOAN_ID = LOAN_LINE_ID's parent, providing header-level loan attributes.
  • LNS_LOAN_LINES_PK — the primary key constraint enforcing LOAN_LINE_ID uniqueness.
  • LNS_LOAN_LINES_U1 — the unique index on LOAN_LINE_ID supporting business-key lookups.
  • Receipt adjustment tables — referenced via REC_ADJUSTMENT_ID and REC_ADJUSTMENT_NUMBER.
  • Payment schedule tables — referenced via PAYMENT_SCHEDULE_ID for installment planning.
  • LNS Loans public APIs — origination, approval, and servicing APIs that insert, update, and lock rows using OBJECT_VERSION_NUMBER.

Because the table is classified as standalone, joins are driven by the explicit LOAN_ID and REFERENCE_ID/PAYMENT_SCHEDULE_ID columns rather than a normalized link table.