Search Results lns_assets




Overview
Explore in AI Chat

Overview

LNS_ASSETS is a table in the LNS (Loans) product schema of Oracle E-Business Suite, documented as VALID in both the 12.1.1 and 12.2.2 releases. The ETRM metadata defines its purpose succinctly: LNS_ASSETS is used to store the assets of a loan participant. In the Oracle Loans data model, this makes LNS_ASSETS the operational repository for collateral and asset records pledged against, or otherwise associated with, a loan and its obligors. Each row captures a discrete asset — its owner, classification, valuation, custodian, and, where applicable, lien information — thereby supporting credit exposure tracking, collateral monitoring, and participant-level reporting within the Loans module.

Heuristic Data Vault classification mined from the foreign-key structure labels this object satellite-leaning. As a modeling suggestion, LNS_ASSETS behaves primarily as a descriptive satellite: it carries a large payload of descriptive and quantitative attributes (51 documented columns) that change over time, while its four foreign keys to HZ_PARTIES act as secondary contextual references rather than a composite hub key. The single unique business key — LNS_ASSETS_U1 on ASSET_ID — distinguishes it from a pure hub-and-link construction.

Key Information Stored

The table is anchored by its surrogate primary key constraint, LNS_ASSETS_PK, defined on the ASSET_ID column. A second unique index, LNS_ASSETS_U1, is also documented on ASSET_ID, confirming the surrogate identifier is the sole unique business-key candidate on this object.

The remaining columns are the standard WHO audit set (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), twenty descriptive ATTRIBUTE flex columns (ATTRIBUTE1 through ATTRIBUTE20) with ATTRIBUTE_CATEGORY, plus appraiser details (APPRAISER_NAME, APPRAISER_PHONE_NUMBER) and reference fields (REFERENCE_TYPE, REFERENCE_NAME).

Common Use Cases and Queries

Typical queries retrieve assets by owner, by loan, or by valuation date. For example, to list all assets owned by a given party:

SELECT asset_id, description, valuation, currency_code, valuation_date FROM lns_assets WHERE asset_owner_id = :party_id;

To find assets requiring revaluation, filter on the scheduled evaluation date:

SELECT asset_id, asset_class_code, next_evaluation_date FROM lns_assets WHERE next_evaluation_date <= SYSDATE;

For collateral or lien reporting, query by LIEN_AMOUNT and ACQUIRED_ASSET_LOAN_ID to aggregate pledged value per loan. Reporting use cases include collateral coverage reports, asset registers by custodian, valuation aging, and asset lifecycle analysis using START_DATE_ACTIVE and END_DATE_ACTIVE. Because ASSET_OWNER_ID, CUSTODIAN_ID, and the two contact party columns all point into HZ_PARTIES, any party-oriented query joins back to the trading community model for names and addresses.

Related Objects

The ETRM relationship data documents the following significant dependencies:

  • HZ_PARTIES — referenced four times from LNS_ASSETS via ASSET_OWNER_ID, CUSTODIAN_ID, CONTACT_PERS_PARTY_ID, and CONTACT_REL_PARTY_ID. This is the dominant join path for party enrichment.
  • LNS_ASSET_ASSIGNMENTS — child table referencing LNS_ASSETS through LNS_ASSET_ASSIGNMENTS.ASSET_ID. Each asset may have multiple assignments, making this the primary dependent transactional object.

Together, LNS_ASSETS and LNS_ASSET_ASSIGNMENTS form the core asset sub-model of the LNS Loans schema, with HZ_PARTIES supplying the party dimension on four separate axes. Master-detail queries should join LNS_ASSETS to LNS_ASSET_ASSIGNMENTS on ASSET_ID, and resolve party details by joining each *_PARTY_ID or *_ID column to HZ_PARTIES.PARTY_ID.