Results for “igf_sl_guarantor”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGF_SL_GUARANTOR table is a reference object within the Oracle E-Business Suite Financial Aid module (IGF), which is documented as obsolete in current releases. It stores the detail of a guarantor — the party that guarantees a lender's loan within the student loan processing flow. Each row represents a single guarantor entity that can be associated with loan recipients, lenders, disbursement responsibilities, and loan setup configurations.

The table is owned by the IGF schema and, in the documented ETRM 12.1.1 physical schema, contains 10 columns. It is not implemented in the current database, and Oracle marks it as proprietary and confidential. From a dimensional modeling perspective, the mined foreign-key structure classifies IGF_SL_GUARANTOR as hub-leaning. This is a heuristic suggestion rather than a documented Data Vault design: the table behaves like a hub because its surrogate key, GUARANTOR_ID, is the stable identifier referenced by numerous dependent tables, while its descriptive attributes are minimal.

Key Information Stored

The table carries a compact set of attributes centered on identity and enablement of the guarantor record.

• GUARANTOR_ID — the surrogate primary key, enforced by the unique index IGF_SL_GUARANTOR_PK. This is the value propagated into all child tables as the foreign key.
• PARTY_ID — the business-key candidate, enforced by the unique index IGF_SL_GUARANTOR_U1. It links the guarantor to the Trading Community Architecture (TCA) party model, tying the record to a real person or organization.
• DESCRIPTION — free-text description of the guarantor.
• DUNS_GUARNT_ID — the Dun & Bradstreet (DUNS) identifier for the guarantor organization, used for external entity identification.
• ENABLED — a status flag controlling whether the guarantor record is active and selectable in loan processing.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture standard Oracle EBS who/when audit information and support change tracking and reconciliation reporting.

The distinction between the two unique indexes is important: GUARANTOR_ID is the internal surrogate key, while PARTY_ID is the natural business key that maps the guarantor to a TCA party.

Common Use Cases and Queries

Because the table centralizes guarantor identity, it is a common join point when reporting on student loan portfolios. Typical scenarios include listing active guarantors, resolving a guarantor to its TCA party, and tracing all loans or recipients backed by a given guarantor.

A basic lookup of enabled guarantors with their party reference might read: SELECT g.guarantor_id, g.party_id, g.description, g.duns_guarnt_id FROM igf_sl_guarantor g WHERE g.enabled = 'Y';

To find all recipients guaranteed by a particular guarantor, query the recipient table using the shared key: SELECT r.* FROM igf_sl_cl_recipient r, igf_sl_guarantor g WHERE r.guarantor_id = g.guarantor_id AND g.party_id = :party_id;

Reporting use cases include guarantor exposure summaries (counting associated loans and disbursement responsibilities), enablement audits, and reconciliation against TCA party records using PARTY_ID. Since the table is obsolete and not implemented, these patterns primarily serve historical data migration, archival analysis, or documentation of legacy Financial Aid installations.

Related Objects

IGF_SL_GUARANTOR is referenced extensively through the GUARANTOR_ID foreign key. The most significant dependent objects include:

• IGF_SL_CL_RECIPIENT — references GUARANTOR_ID, linking each loan recipient to its guarantor.
• IGF_SL_LOR_ALL and IGF_SL_LOR_LOC_ALL and IGF_SL_LOR_LOC_HISTORY — lender-of-record tables and their location history that carry GUARANTOR_ID.
• IGF_SL_CL_SETUP_ALL and IGF_SL_CL_RESP_R1_ALL — loan setup and responsibility configuration records keyed to the guarantor.
• IGF_DB_CL_DISB_RESP_ALL — disbursement responsibility records referencing the guarantor.
• OKL_PARTY_ROLES_INTERFACE — the party role interface (typically in the Oracle Lease/OKL context) that references GUARANTOR_ID, bridging guarantor data into party-role processing.

These relationships confirm the table's role as a hub-like entity: its surrogate key anchors many transactional and configuration satellites while the descriptive payload remains minimal.