Search Results lns_participants




Overview
Explore in AI Chat

Overview

The LNS_PARTICIPANTS table is a core data object within the Oracle E-Business Suite Loans (LNS) module, specifically in versions 12.1.1 and 12.2.2. It functions as the master repository for all participant entities associated with a loan. A participant represents an individual or organization, such as a borrower, guarantor, or co-signer, that has a defined role and financial interest in a loan contract. The table's primary role is to establish and maintain the critical relationships between a loan and the various parties involved, linking loan data from the LNS module to the centralized Trading Community Architecture (TCA) model for customer and party information. This enables comprehensive management, tracking, and reporting on all stakeholders throughout the loan lifecycle.

Key Information Stored

The table's structure is designed to capture the identity, role, and specific details of each loan participant. Its primary key, PARTICIPANT_ID, uniquely identifies each participant record. The most significant foreign key is LOAN_ID, which ties the participant to a specific loan in the LNS_LOAN_HEADERS_ALL table. The table extensively integrates with the TCA model through columns like HZ_PARTY_ID (the core party identifier), CUST_ACCOUNT_ID (customer account), and BILL_TO_ACCT_SITE_ID (billing address). It also stores relationship details for contacts (CONTACT_PERS_PARTY_ID, CONTACT_REL_PARTY_ID) and links to credit management processes via CREDIT_REQUEST_ID and CASE_FOLDER_ID. Collectively, these columns define who the participant is, their relationship to the loan, and their associated financial and contact details.

Common Use Cases and Queries

This table is central to numerous operational and reporting functions. A common use case is generating a comprehensive participant list for a specific loan, often required for loan documentation or internal reviews. Another critical scenario involves analyzing the network of guarantors or co-borrowers associated with a customer across multiple loans for risk assessment. A typical query to retrieve all participants for a loan, including their party name, would be:

  • SELECT lp.participant_id, lp.loan_id, hp.party_name, lp.role_code FROM lns_participants lp, hz_parties hp WHERE lp.hz_party_id = hp.party_id AND lp.loan_id = :p_loan_id;

Reporting use cases include exposure reports by participant, compliance reports detailing required signatories, and audit trails of all parties associated with a loan from origination to closure.

Related Objects

The LNS_PARTICIPANTS table sits at a key integration point within the EBS schema. Its primary relationship is with the loan header table, LNS_LOAN_HEADERS_ALL. As indicated by its foreign keys, it is fundamentally dependent on the TCA registry tables: HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_CUST_ACCT_SITES_ALL. It also integrates with the Credit Management (AR_CMGT) module through AR_CMGT_CREDIT_REQUESTS and AR_CMGT_CASE_FOLDERS. This table is likely referenced by various Loans transactional forms, participant-specific views, and public APIs within the LNS_ PKG packages for creating and updating participant records. Any process or report concerning loan stakeholders will ultimately query this table.