Search Results igf_sl_recipient_all_v




Overview
Explore in AI Chat

Overview

IGF_SL_RECIPIENT_ALL_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Financial Aid module (IGF). It presents a consolidated, single-row-per-recipient listing of the three participant types that appear in the Federal Family Education Loan (FFEL) processing chain: lenders, guarantors, and servicers. Rather than requiring report developers and integrators to query three separate registration tables, the view projects each source table into a uniform column layout and stitches the results together with UNION ALL, exposing a single "recipient" abstraction.

The object is documented as VALID and is available in both EBS 12.1.1 and 12.2.2. Its principal design characteristic is the RECIPIENT_TYPE discriminator column, which carries one of three literal values — LND for lender, GUARN for guarantor, and SRVC for servicer. This view is therefore the canonical lookup point for any code that must resolve a lender, guarantor, or servicer identifier without knowing in advance which entity type is stored in a given transaction or setup record.

Underlying Base Objects

The view text references five Financial Aid base tables, joined in three UNION ALL branches:

  • IGF_SL_LENDER and IGF_SL_LENDER_BRC — joined on LENDER_ID with an outer join to the BRC (Branch) table, producing the LND branch.
  • IGF_SL_GUARANTOR — queried directly with no join, producing the GUARN branch. The BRC-related columns are hard-coded as empty strings, since guarantors in this release do not carry the non-ED BRC attributes that lenders and servicers do.
  • IGF_SL_SERVICER and IGF_SL_SERVICER_BRC — joined on SERVICER_ID with an outer join to the BRC table, producing the SRVC branch.

The outer joins to the BRC tables are significant: a lender or servicer that has no branch record still appears in the result set, with NULL BRC columns. The ETRM metadata documents no additional referenced base objects beyond these five tables.

Key Columns

Common Use Cases and Queries

The view is typically used to drive validation lists, recipient-selection LOVs, and reconciliation extracts. A representative query that lists all enabled recipients of a single type follows:

  • SELECT recipient_id, recip_description, duns_recip_id FROM igf_sl_recipient_all_v WHERE recipient_type = 'LND' AND recip_enabled = 'Y' ORDER BY recip_description;

A common cross-type usage is resolving an identifier whose entity type is not known in advance:

  • SELECT recipient_type, recip_description FROM igf_sl_recipient_all_v WHERE recipient_id = :p_recipient_id;

For integration and audit extracts, the entire population is often selected with the type exposed as a grouping key:

  • SELECT recipient_type, COUNT(*) FROM igf_sl_recipient_all_v GROUP BY recipient_type;

Because the view is a UNION ALL without DISTINCT, counts reflect the underlying registration rows; duplicate identifiers across entity types are possible and should be filtered by RECIPIENT_TYPE when uniqueness is required.