Search Results lender_id




Overview
Explore in AI Chat

Overview

The IGF.IGF_SL_LENDER_BRC table is a core data repository within the Oracle E-Business Suite (EBS) Student Loan (SL) module, specifically under the IGF (Institutional Grants and Financial Aid) product family. Its primary function is to store and manage lender branch codes that are not assigned by the U.S. Department of Education (ED). This table enables financial institutions to map their internal branch office identifiers to the EBS system, facilitating accurate loan processing, reporting, and partner relationship management. It serves as a critical reference point for associating loan transactions with the correct lender branch entity outside the standard ED coding framework.

Key Information Stored

The table's structure is designed to capture both the external branch identifier and its integration with the EBS architecture. The most critical columns include:

  • LENDER_ID (VARCHAR2(30)): The mandatory, unique 6-character identification code assigned by the U.S. Department of Education to the lender. This column is part of the table's primary key.
  • LEND_NON_ED_BRC_ID (VARCHAR2(30)): The unique identification code assigned by a non-ED entity (e.g., the lender itself) to identify a specific branch office. This forms the second part of the primary key with LENDER_ID.
  • DESCRIPTION (VARCHAR2(80)): A textual description of the lender branch.
  • PARTY_ID (NUMBER(15)): A crucial integration column that links the lender branch record to a Trading Community Architecture (TCA) party record, enabling unified customer and organization management across EBS.
  • ENABLED (VARCHAR2(1)): An indicator flag that controls the active status of the lender branch record. Setting it to inactive prevents its use in new or modified transactions.
The table also contains standard "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

This table is central to operations involving lender branch validation and reporting. A common use case is verifying the active status and TCA linkage of a specific lender branch during loan origination or servicing. For reporting, it is frequently joined to loan transaction tables to produce detailed reports segmented by lender branch. The foundational query to retrieve all records, as indicated in the ETRM, is: SELECT LENDER_ID, LEND_NON_ED_BRC_ID, DESCRIPTION, PARTY_ID, ENABLED FROM IGF.IGF_SL_LENDER_BRC; A more practical query might involve filtering for active branches for a specific ED lender: SELECT * FROM IGF.IGF_SL_LENDER_BRC WHERE LENDER_ID = 'XXXXXX' AND ENABLED = 'Y'; Another critical pattern is joining to the TCA base tables via the PARTY_ID to fetch the organization's name and address details for correspondence or compliance reporting.

Related Objects

Based on the provided metadata, the primary relationship is through the PARTY_ID column, which creates a dependency on the Trading Community Architecture (TCA) party tables (e.g., HZ_PARTIES). The table is indexed for performance on its primary key (LENDER_ID, LEND_NON_ED_BRC_ID) and has a unique constraint on PARTY_ID (IGF_SL_LENDER_BRC_U1). The ETRM states that the table "is referenced by" the APPS.IGF_SL_LENDER_BRC synonym, which is the standard access point for all application code and queries. This design ensures that the underlying table structure in the IGF schema is abstracted for the application layer.