Search Results con_party

Overview

APPS.LNS_LOAN_SUMMARY_V is a reporting view in the Oracle E-Business Suite Loan Management (LNS) module, part of the Enterprise Treasury and Risk Management (ETRM) family of applications in EBS 12.1.1 and 12.2.2. It presents a consolidated, denormalized picture of loan header records, joining each loan to its associated lookup meanings, loan type, currency name, assigned resource, and borrower party. Rather than forcing report authors and integrators to join LNS_LOAN_HEADERS against multiple lookup views and resource tables directly, this view delivers a single flat row per loan with human-readable values already resolved. It is particularly relevant to users searching for "loan_purpose," since the view exposes loan_purpose.meaning as a dedicated column, resolving the lookup code stored on the loan header into its descriptive meaning. The view is filtered to active loans only: it excludes records where the loan's end date has passed unless end date is null, ensuring reports show loans that are currently in effect.

Underlying Base Objects

The view is defined over a set of documented base objects. The primary driving table is LNS_LOAN_HEADERS (accessed via a synonym), which supplies the loan identifiers, amounts, dates, reference attributes, and descriptive flexfield columns. LNS_LOAN_TYPES supplies the loan type name. FND_CURRENCIES_VL provides the currency name, while LNS_LOOKUPS is joined multiple times — aliased as status, loan_class, loan_subtype, loan_purpose, periodlkup, and amort_periodlkup — to translate stored lookup codes into meanings. JTF_RS_RESOURCE_EXTNS is joined on loan_assigned_to to bring in the assigned employee's name components, with the constraint that the resource category is 'EMPLOYEE'. HZ_PARTIES supplies the contact party name via con_party.party_name. The LNS_FIN_UTILS package is called through the getActiveRate function, which returns the loan's currently active interest rate. FND_GLOBAL is referenced as a standard EBS session context package. As documented for the 12.2.2 release, the referenced base objects are: FND_CURRENCIES_VL (view), FND_GLOBAL (package), HZ_PARTIES (synonym), JTF_RS_RESOURCE_EXTNS (synonym), LNS_FIN_UTILS (package), LNS_LOAN_HEADERS (synonym), LNS_LOAN_TYPES (synonym), and LNS_LOOKUPS (view).

Key Columns

The view exposes a wide range of loan attributes. Identity and organizational columns include loan_id, org_id, and loan_number. Status and classification are represented by status.meaning (from the LOAN_STATUS lookup type), loan_type_name, loan_class meaning, loan_subtype meaning, and the loan_purpose meaning that answers the "loan_purpose" search. Financial columns include requested_amount, funded_amount, loan_currency with curr.name, and the active interest rate returned by lns_fin_utils.getActiveRate. Date columns cover creation_date, loan_application_date, loan_approval_date, loan_start_date, loan_maturity_date, loan_closing_date, gl_date, and end_date. Term columns include loan_term and amortized_term, each paired with a period lookup meaning. Reference information is exposed through reference_id, reference_type, reference_number, and reference_description. Borrower and contact details include primary_borrower_id, cust_account_id, bill_to_acct_site_id, and con_party.party_name. Loan assignment is shown through loan_assigned_to and the resource name columns. Twenty attribute columns (attribute1 through attribute20) and attribute_category expose descriptive flexfield data. Portfolio-level fields COLLATERAL_PERCENT, CREDIT_REVIEW_FLAG, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, and EXCHANGE_RATE are also included. Note that loan_product is returned as a null placeholder.

Common Use Cases and Queries

Typical uses include loan portfolio reporting, treasury dashboards, borrower exposure analysis, and integration extracts that feed downstream risk or accounting systems. A frequent pattern is filtering by loan purpose:

• SELECT loan_number, loan_purpose, requested_amount, funded_amount FROM apps.lns_loan_summary_v WHERE loan_purpose = 'Working Capital';
• SELECT loan_number, status.meaning, loan_maturity_date FROM apps.lns_loan_summary_v WHERE loan_maturity_date < SYSDATE + 30;
• SELECT loan_purpose, COUNT(*), SUM(funded_amount) FROM apps.lns_loan_summary_v GROUP BY loan_purpose;

Because the view already resolves lookup meanings and enforces the active-loan filter, it substantially reduces join complexity for both ad hoc queries and published reports.