Search Results unique_fee_name

Overview

LNS_FEES_ALL is the Loan Fees Setup table in the Oracle E-Business Suite Loans (LNS) module. It stores the master definition of fees that can be assessed against loan contracts, including the fee amount or rate, the basis on which the fee is calculated, the periods during which the fee is active, and the rules governing billing, waiver, and editability. In EBS 12.1.1 and 12.2.2 the table is owned by the LNS schema and is documented as VALID with 26 physical columns in the 12.2.2 reference schema.

The table is multi-organization enabled: it carries ORG_ID, and the documented primary key is the surrogate UNIQUE_FEE_NAME, which is composed of the business columns FEE_NAME and ORG_ID. The heuristic Data Vault classification supplied in the metadata is standalone, meaning the object is modeled most naturally as a satellite (or reference/hub-style master record) rather than as a link table. This classification should be treated as a modeling suggestion; because the key is a composite of FEE_NAME and ORG_ID, a strict Data Vault treatment would separate the fee business key into a hub and place descriptive and effective-dated attributes in a satellite. The absence of mined foreign-key relationships reinforces the standalone classification — LNS_FEES_ALL is a setup/reference object referenced by transaction tables rather than one that itself depends on parent objects.

Key Information Stored

The most significant columns fall into identification, definition, and control categories:

• UNIQUE_FEE_NAME — the documented surrogate primary key, unique per fee setup row.
• FEE_NAME — the user-facing name of the fee; together with ORG_ID it forms the business-key candidate behind the primary key.
• ORG_ID — the operating unit that owns the setup row; the second component of the composite business key and the driver of multi-org security.
• FEE_ID — the numeric fee identifier, a common join key in downstream transaction tables.
• FEE_DESCRIPTION — free-text description of the fee.
• FEE_CATEGORY and FEE_TYPE — classification attributes controlling how the fee is grouped and applied.
• FEE and FEE_BASIS — the fee amount or rate and the basis on which it is computed.
• FEE_BASIS_RULE — the rule that determines the calculation base.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window for the fee definition.
• NUMBER_GRACE_DAYS and MINIMUM_OVERDUE_AMOUNT — thresholds that control when the fee is triggered.
• CURRENCY_CODE — the currency in which a monetary fee is expressed.
• RATE_TYPE and BILLING_OPTION — rate sourcing and billing behavior.
• COLLECTED_THIRD_PARTY_FLAG, FEE_WAIVABLE_FLAG, and FEE_EDITABLE_FLAG — behavioral flags governing collection, waiver, and user editability.
• CUSTOM_PROCEDURE — a hook allowing custom logic to be invoked for the fee.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — optimistic locking and audit information.

Common Use Cases and Queries

Typical scenarios include fee setup validation, fee usage reporting, and effective-date auditing. A standard lookup by the business key pattern is:

• SELECT * FROM lns.lns_fees_all WHERE fee_name = :p_fee_name AND org_id = :p_org_id; — resolves a fee definition using the primary key components.
• SELECT fee_name, fee, fee_basis, currency_code, start_date_active, end_date_active 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)); — lists currently active fees for an operating unit.
• SELECT fee_category, fee_type, COUNT(*) FROM lns.lns_fees_all WHERE org_id = :p_org_id GROUP BY fee_category, fee_type; — summarizes fee configurations by category and type.
• SELECT fee_name, fee_waivable_flag, fee_editable_flag, billing_option FROM lns.lns_fees_all WHERE org_id = :p_org_id; — audits behavioral flags and billing options.

Reporting use cases include feeding fee master data into downstream loan transaction analysis, verifying that flags such as FEE_WAIVABLE_FLAG are consistently set across operating units, and reconciling effective-dated fee definitions against historical transactions. Because the table is a setup object, most operational reporting joins it to transaction tables using FEE_ID rather than querying it in isolation.

Related Objects

The ETRM metadata records no mined foreign keys for LNS_FEES_ALL, consistent with its standalone classification. From functional knowledge of the Loans module, the most significant related objects are:

• LNS_FEE_DEFAULTS / fee assignment setup tables — reference LNS_FEES_ALL by FEE_ID to attach fees to loan products or contracts.
• Transaction fee tables (loan fee transaction objects) — store assessed fee instances and join to this table via FEE_ID, or via FEE_NAME and ORG_ID where the business key is used.
• LNS_LOAN_HEADERS_ALL (loan contracts) — the parent loan context under which fee setups are applied; joined through ORG_ID and the loan's fee associations.
• LNS_SYSTEM_OPTIONS / LNS_APPLICATION_OPTIONS — supply the ORG_ID context and module-level defaults that govern fee behavior.
• FND_LOOKUPS (FEE_CATEGORY, FEE_TYPE, FEE_BASIS, BILLING_OPTION) — provide the valid values displayed and stored in the classification columns.
• LNS_FEE_SETUP_PUB / Loans public APIs and fee validation packages — programmatic interfaces that read and write fee setup records for contract and product administration.

Because no formal FK relationships are documented, any join to these objects should be validated against the consuming application's own referential logic rather than assumed from schema metadata.