Results for “loan_currency”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

LNS_LOAN_DTLS_ALL_MV is an APPS-owned table within the Loans (LNS) product family of Oracle E-Business and Oracle Financial Services applications, registered as a valid object in the ETRM repository for releases 12.1.1 and 12.2.2. The "_MV" suffix conventionally indicates a materialized view, and this object functions as a denormalized snapshot of loan detail data, pre-joining borrower, legal entity, loan product, loan type, and agent information into a single, query-efficient structure. Its physical schema documents 52 columns, making it one of the wider reporting-oriented objects in the LNS module. Because the object carries ORG_ID alongside legal entity and operating unit attributes, it is multi-org aware and supports operating-unit-scoped reporting across the enterprise.

The provided metadata classifies this object heuristically as standalone under the Data Vault lens, i.e., it does not participate in parent-child link structures within the documented FK graph. In Data Vault modeling terms, this suggests treating the object as a satellite-like reporting snapshot attached to the loan business key rather than as a normalized hub or link. The design intent is read-optimized aggregation rather than transactional integrity, since materialized views may be refreshed on a schedule and therefore can lag the base loan tables.

Key Information Stored

The surrogate-level identifier for a loan record is LOAN_ID, which anchors the snapshot together with the human-readable LOAN_NUMBER business key. Both LOAN_ID and LOAN_NUMBER are the primary candidates for business-key uniqueness, and LOAN_NUMBER is the most reliable unique index candidate for cross-checking against source systems.

Common Use Cases and Queries

Because the object is a denormalized snapshot, it is the natural source for loan portfolio dashboards, exposure aggregation, and maturity-gap reporting without repeatedly joining the underlying LNS tables.

  • Portfolio exposure by legal entity or operating unit: SELECT LEGAL_ENTITY_NAME, OPERATING_UNIT_NAME, SUM(TOTAL_PRINCIPAL_BALANCE) FROM LNS_LOAN_DTLS_ALL_MV GROUP BY LEGAL_ENTITY_NAME, OPERATING_UNIT_NAME.
  • Maturity laddering: filter on LOAN_MATURITY_DATE within a fiscal window and group by LOAN_PRODUCT_NAME.
  • Rate and currency segmentation: aggregate RATE by RATE_TYPE and LOAN_CURRENCY.
  • Refresh-lag monitoring: compare MAX(LAST_UPDATE_DATE) against MAX(LOAN_MAX_LAST_UPDATE_DATE).
  • Borrower concentration: rank PARTY_NAME by TOTAL_PRINCIPAL_BALANCE for exposure limits.

Queries should always be ORG_ID-scoped in multi-org environments to avoid cross-operating-unit contamination.

Related Objects

Consumers should treat this object as a read-only reporting surface and perform drill-through to the base LNS tables for transactional detail and audit-grade reconciliation.