Search Results alt_prog_type_code




Overview
Explore in AI Chat

Overview

IGF_DB_CL_DISB_RESP is a multi-org view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGF.IGF_DB_CL_DISB_RESP. It falls within the Financial Aid / Student Loan processing area of the Oracle EBS footprint, historically aligned with the Intellection/IGF (International Government Finance) product family used to support Title IV and related student loan disbursement reporting. The view exposes a wide, denormalized record set describing loan disbursement activity at the student borrower level, combining guarantor, lender, school, disbursement, fee, and cancellation attributes in a single queryable structure. Its multi-org behavior means that query results are automatically filtered to the operating unit of the active session, so data from other operating units is excluded unless the view is queried in a context that ignores the ORG_ID filter.

The view is registered as a VALID object in 12.1.1 and 12.2.2. It is not a base table itself, and no base objects are documented in the ETRM metadata, meaning the view definition is not surfaced as a set of documented underlying tables. Treat it as a reporting and integration surface rather than as a transactional source of truth.

Underlying Base Objects

The documented metadata does not list the base tables or synonyms referenced by the view definition; the ETRM entry records "Referenced base objects: none documented." As a consequence, the physical lineage can only be confirmed by querying the view definition itself or by inspecting DBA_VIEWS / DBA_DEPENDENCIES in the target instance. The presence of a ROW_ID (ROWID) column and the multi-org designation indicate that the view is a join or union over one or more organization-enabled tables in the IGF schema, likely combining disbursement, borrower, school, lender, and guarantor entities into a single flattened record for downstream reporting.

The column set suggests a composite of at least a disbursement table (CDBR_ID, CBTH_ID, DISB_NUM, FUND_RELEASE_DATE, GROSS_DISB_AMT, NET_DISB_AMT), a borrower table (B_LAST_NAME, B_FIRST_NAME, B_SSN), a student table (S_LAST_NAME, S_SSN, SCHOOL_ID), and lender/guarantor reference tables (LENDER_ID, GUARANTOR_ID). Because the lineage is undocumented, the safest handling is to treat IGF_DB_CL_DISB_RESP as an interface view whose shape is contractual, not its internals.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling disbursement totals by school, producing borrower-level disbursement reports, auditing net-versus-gross amounts after fee deduction, and extracting records flagged with error codes for remediation. Because the view is multi-org, any query executed with a valid operating unit context returns only that organization's rows.

SELECT cl_seq_number,
       loan_number,
       b_last_name,
       b_first_name,
       s_last_name,
       school_id,
       gross_disb_amt,
       net_disb_amt,
       fund_release_date,
       disb_num
  FROM apps.igf_db_cl_disb_resp
 WHERE fund_release_date >= :p_from_date
   AND fund_release_date <  :p_to_date
 ORDER BY school_id, cl_seq_number;

Auditing net amounts after fee deduction:

SELECT cdbr_id,
       gross_disb_amt,
       NVL(fee_1,0) + NVL(fee_2,0) AS total_fees,
       net_disb_amt,
       gross_disb_amt - (NVL(fee_1,0) + NVL(fee_2,0)) AS computed_net
  FROM apps.igf_db_cl_disb_resp
 WHERE NVL(net_disb_amt,0) <> gross_disb_amt - (NVL(fee_1,0) + NVL(fee_2,0));

Identifying records with downstream errors:

SELECT cdbr_id, loan_number, err_code1, err_code2, err_code3, err_code4, err_code5
  FROM apps.igf_db_cl_disb_resp
 WHERE err_code1 IS NOT NULL
    OR err_code2 IS NOT NULL
    OR err_code3 IS NOT NULL;

Because DUNS_SCHOOL_ID is flagged obsolete, joins to current school master data should use SCHOOL_ID rather than the DUNS column, and results should be validated against the current school reference in the instance.