Search Results lns_fee_assignments




Overview
Explore in AI Chat

Overview

LNS_FEE_ASSIGNMENTS is a transaction-level table in the Oracle E-Business Suite Loans (LNS) module, owning schema LNS. It stores the assignment of fees to individual loan contracts, capturing how a specific fee is applied, calculated, and collected across the life of a loan. In Oracle EBS 12.1.1 and 12.2.2, this table forms part of the loan servicing and fee-processing infrastructure used by Oracle Loans and integrated treasury/lending workflows. Each row represents one fee assignment instance tied to a loan, distinguishing it from the fee definition master data held elsewhere in the LNS schema.

The ETRM metadata records LNS_FEE_ASSIGNMENTS with 26 documented columns and a primary key constraint, LNS_FEE_ASSIGNMENTS_PK, on FEE_ASSIGNMENT_ID. A unique index, LNS_FEE_ASSIGNMENTS_U1, also exists on FEE_ASSIGNMENT_ID, reinforcing its role as the sole business-key candidate. The table carries a foreign key from LOAN_ID, linking each fee assignment back to its parent loan. The heuristic Data Vault classification derived from the FK structure is satellite-leaning, suggesting this table behaves as a descriptive satellite attached to the loan hub/link — recording attributes and fee-level detail rather than acting as an independent hub or relationship link.

Key Information Stored

The surrogate primary key FEE_ASSIGNMENT_ID uniquely identifies each assignment record and is the sole unique-index candidate. LOAN_ID is the foreign key tying the fee assignment to a specific loan contract; it is the principal join column for loan-centric reporting. FEE_ID and FEE_TYPE identify which fee is being assigned and its categorization, while FEE and FEE_BASIS define the fee amount and the basis on which it is calculated (for example, a fixed or percentage basis).

Temporal and installment-scoping attributes are central to this table: BEGIN_INSTALLMENT_NUMBER, END_INSTALLMENT_NUMBER, NUMBER_OF_PAYMENTS, NUMBER_GRACE_DAYS, and NUMBER_OF_PAYMENTS govern when and over how many payment periods the fee applies. START_DATE_ACTIVE and END_DATE_ACTIVE bound the active window of the assignment. RATE_TYPE and BILLING_OPTION control how the fee is rated and billed. COLLECTED_THIRD_PARTY_FLAG, OPEN_PHASE_FLAG, and DELETE_DISABLED_FLAG carry status/flag semantics, while PHASE, CUSTOM_PROCEDURE, and DISB_HEADER_ID support phase-based or disbursement-linked fee handling and client extension logic. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER provide audit and optimistic-locking support.

Common Use Cases and Queries

Typical reporting retrieves all fee assignments for a given loan, computing total fees or filtering by active window and billing option. A representative query joins the assignment table to its loan parent:

  • SELECT fa.fee_assignment_id, fa.fee_id, fa.fee_type, fa.fee, fa.fee_basis, fa.billing_option FROM lns.lns_fee_assignments fa WHERE fa.loan_id = :loan_id;

  • Filtering by active period — WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE) — to list currently effective fees.

  • Aggregating fees by loan or fee type for reconciliation and accrual reporting: SELECT loan_id, fee_type, SUM(fee) FROM lns.lns_fee_assignments GROUP BY loan_id, fee_type;

  • Audit and change tracking using OBJECT_VERSION_NUMBER and the WHO columns to detect records modified since a given date.

These patterns support fee accrual schedules, loan amortization and payoff computations, and downstream GL/receivable entries driven by fee collection.

Related Objects

The most significant relationship is to the loan master, joined via LOAN_ID, where the parent loan record holds contract-level attributes. FEE_ID references the fee definition master (fees setup), providing fee name, type, and default calculation rules. FEE_TYPE and FEE_BASIS typically map to lookup values. DISB_HEADER_ID ties the assignment to a disbursement header when fees are associated with disbursement events. CUSTOM_PROCEDURE and PHASE may reference client-specific extension or phase configuration. The LNS_FEE_ASSIGNMENTS_PK and U1 constraints ensure each FEE_ASSIGNMENT_ID is unique, while the LOAN_ID foreign key guarantees referential integrity to the loan. Reporting views and the Oracle Loans fee-processing APIs consume these rows to drive fee calculation, billing, and collection in both 12.1.1 and 12.2.2.