Search Results origination_fee_billing_option

Overview

LNS.LNS_FEES_ALL is the Oracle Loans setup table in which loan fee definitions are created, maintained, and stored for the Oracle E-Business Suite (EBS) Loans module. The table functions as the master repository for fee templates; each row defines a fee that may subsequently be assigned to a loan during loan application creation. Because fee records are seeded reference data rather than transactional loan activity, the object resides in the APPS_TS_SEED tablespace with a PCT Free of 10, consistent with its role as controlled setup data. In EBS 12.1.1 and 12.2.2 the table is registered under FND Design Data as LNS.LNS_FEES_ALL and carries a VALID status. The heuristic Data Vault classification mined from its foreign key structure is standalone, which suggests modelling this object as an independent hub (with a business key of FEE_NAME, ORG_ID) rather than as a link or satellite dependent on parent loan entities.

Key Information Stored

The physical schema documented for ETRM 12.2.2 comprises 26 columns. The most operationally significant are:

• FEE_ID — surrogate numeric (15) identifier for the fee definition.
• FEE_NAME — the descriptive name of the fee; part of the unique business key.
• ORG_ID — organization identifier enabling multi-org (operating unit) partitioning of fee definitions; the second component of the unique key.
• FEE_CATEGORY — lookup-driven classification (lookup type 'FEE_CATEGORY') that governs downstream behaviour.
• FEE_TYPE — the applicable-to value, driven by the category and validated against lookups such as 'ORIGINATION_FEE_APPLICABLE_TO', 'SERVICING_FEE_APPLICABLE_TO', and 'MEMO_FEE_APPLICABLE_TO'.
• FEE — the fee amount or percentage, interpreted according to RATE_TYPE.
• FEE_BASIS and FEE_BASIS_RULE — define the calculation base for the fee (lookup type 'FEE_BASIS').
• RATE_TYPE — indicates whether FEE is a flat amount or a rate, driven by lookup type 'RATE_TYPE'.
• BILLING_OPTION — how the fee is billed, validated against category-specific lookup sets ('ORIGINATION_FEE_BILLING_OPTION', 'SERVICING_FEE_BILLING_OPTION', 'MEMO_FEE_BILLING_OPTION').
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-range activation controls.
• CURRENCY_CODE — the currency in which the fee is denominated.
• FEE_WAIVABLE_FLAG and FEE_EDITABLE_FLAG — control whether the fee may be waived or modified during loan processing.
• NUMBER_GRACE_DAYS and MINIMUM_OVERDUE_AMOUNT — apply to late-payment fee logic.
• COLLECTED_THIRD_PARTY_FLAG — indicates whether the fee is collected on behalf of a third party.
• Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus OBJECT_VERSION_NUMBER, and the extensibility column CUSTOM_PROCEDURE, complete the definition.

The documented unique constraint UNIQUE_FEE_NAME (FEE_NAME, ORG_ID) establishes the business key, distinct from the surrogate FEE_ID. All lookups are validated against FND lookup types, so referential integrity for descriptive values is enforced through the lookup framework rather than through foreign keys.

Common Use Cases and Queries

Typical usage centres on verifying which fees are active for an operating unit, checking calculation bases before a loan application is submitted, and reporting fee revenue exposure by category or currency. Because the table is reference data, queries usually filter by ORG_ID and effective dates:

SELECT fee_name, fee_category, fee_type, fee, rate_type,
       billing_option, currency_code
  FROM   lns.lns_fees_all
 WHERE   org_id = :p_org_id
   AND   TRUNC(SYSDATE) BETWEEN start_date_active
                             AND NVL(end_date_active, TRUNC(SYSDATE));

Analysts frequently join the fee definitions to loan-level fee assignment tables to reconcile expected versus charged amounts, and to report waivable or third-party-collected fees separately. Date-range logic (including the NVL on END_DATE_ACTIVE) and multi-org predicates are the two most common sources of incorrect reporting results and should always be applied explicitly.

Related Objects

Because LNS_FEES_ALL is modelled as standalone, it does not itself carry foreign keys; dependents reference it. The most significant related objects are:

• LNS_LOAN_FEES — loan-level fee assignment records that reference LNS_FEES_ALL.FEE_ID when a fee is attached to a loan application.
• LNS_LOAN_HEADERS — the parent loan record to which fee assignments ultimately attach.
• FND_LOOKUP_VALUES — validates FEE_CATEGORY, FEE_TYPE, FEE_BASIS, RATE_TYPE, and BILLING_OPTION values.
• FND_LOOKUP_TYPES — defines the lookup type sets that constrain the fee configuration.
• HR_OPERATING_UNITS / FND_ORGANIZATIONS — supply the ORG_ID operating unit context for multi-org access.
• Oracle Loans application APIs — the loan creation and fee assignment PL/SQL interfaces that consume these definitions.
• FND_ID_FLEX_STRUCTURES-style WHO column consumers — audit and concurrency mechanisms relying on the standard WHO and OBJECT_VERSION_NUMBER columns.