Search Results relationship_cd




Overview
Explore in AI Chat

Overview

The table IGF_SL_CL_RECIPIENT is a core data structure within the now-obsolete Financial Aid (IGF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary function is to act as a central relationship registry, defining and maintaining the formal business associations between the key entities involved in the student loan process: lenders, guarantors, and recipients (students). This table is critical for ensuring that loan origination, disbursement, and guarantee processes reference the correct and authorized parties. The metadata indicates that while the table structure is defined, it may not be implemented in all databases, suggesting potential variations in deployment based on institutional configuration.

Key Information Stored

The table's design centers on uniquely identifying the parties and their specific relationship. The most significant columns include identifiers for each entity: LENDER_ID, GUARANTOR_ID, and RECIPIENT_ID. These are complemented by branch identifiers (LEND_NON_ED_BRC_ID and RECIP_NON_ED_BRC_ID) for more granular location tracking. The RELATIONSHIP_CD column is a crucial attribute that codifies the nature of the association between these parties (e.g., primary lender-guarantor pairing). A surrogate key, RCPT_ID, serves as the primary unique identifier for each record. The table's multiple unique constraints (IGF_SL_CL_RECIPIENT_U1, IGF_SL_CL_RECIPIENT_U2, RCPT_UK) enforce data integrity by preventing duplicate relationship entries.

Common Use Cases and Queries

This table is primarily queried to validate and report on the network of participants for a student's loan. Common operational and reporting scenarios include verifying that a loan application is associated with an approved lender-guarantor pairing, generating lists of all recipients (students) for a specific guarantor, or identifying all lenders associated with a particular recipient. A typical query pattern involves joining to related entity tables to retrieve descriptive names. For example, to retrieve a recipient's details with their associated lender and guarantor names, a SQL statement would join IGF_SL_CL_RECIPIENT to IGF_SL_LENDER and IGF_SL_GUARANTOR on their respective ID columns. Another common use is to lookup the valid RELATIONSHIP_CD for use in other loan processing tables like IGF_SL_LOR_ALL or IGF_SL_CL_SETUP_ALL.

Related Objects

IGF_SL_CL_RECIPIENT is a nexus table with extensive foreign key relationships, as documented in the ETRM metadata. It references master entity tables to ensure referential integrity:

  • IGF_SL_GUARANTOR via GUARANTOR_ID
  • IGF_SL_LENDER via LENDER_ID
  • IGF_SL_LENDER_BRC via LENDER_ID and LEND_NON_ED_BRC_ID

Conversely, its RELATIONSHIP_CD column is referenced as a foreign key by several other configuration and transaction tables, including:

These relationships demonstrate that the relationship codes defined in IGF_SL_CL_RECIPIENT drive configurations for preferred lenders, loan origination records, and fund categories.