Search Results spnsr_charge_id




Overview

APPS.IGF_DB_AWD_DISB_DTL is a multi-org view in the Oracle E-Business Suite Financial Aid (IGF) module, exposing award disbursement detail records used by the Student Financial Aid and Grants Management processes. In EBS 12.1.1 and 12.2.2, this view is registered with FND Design Data as IGF.IGF_DB_AWD_DISB_DTL and is owned by the APPS schema with a VALID status. The view is defined as a multi-org view, meaning it automatically restricts rows to the operating unit currently set in the user's session and ignores disbursement data belonging to other operating units. This behavior is enforced through the standard Oracle multi-org security mechanism, which typically resolves through the ORG_ID column of the underlying base table rather than exposing ORG_ID in the view's select list.

The view presents a consolidated picture of award-level disbursement activity including gross amounts, fees, net amounts, adjustments, disbursement dates, and status information related to the Student Finance (SF) interface. It is used in financial aid reporting, disbursement reconciliation, and downstream integration with student accounts and third-party servicers.

Underlying Base Objects

The ETRM documentation excerpt for this object does not explicitly list referenced base objects, and the documented base objects section returns none for the 12.2.2 metadata. Functionally, IGF_DB_AWD_DISB_DTL is a view over the IGF award disbursement detail entity, which in the IGF schema is the IGF_DB_AWD_DISB_DTL table (or its equivalent base table storing award disbursement rows keyed by AWARD_ID, DISB_NUM, and DISB_SEQ_NUM). The view applies the multi-org predicate on the base table's ORG_ID column. Because the view is owned by APPS with FND Design Data registered, it is intended to be queried directly by applications and reports rather than through the base table, ensuring operating unit security is applied consistently.

Key Columns

Several columns are retained for backward compatibility only and are documented as no longer used: DISB_BATCH_ID, DISB_ACK_DATE, BOOKING_BATCH_ID, BOOKED_DATE, DISB_STATUS, and DISB_STATUS_DATE.

Common Use Cases and Queries

This view is commonly used to report award disbursement activity by operating unit, to reconcile sponsor charge and credit amounts, and to trace Student Finance interface outcomes. Because the user searched for SPNSR_CHARGE_ID, a typical query retrieves disbursements tied to a specific sponsor charge:

SELECT award_id, disb_num, disb_seq_num, disb_gross_amt, disb_net_amt, disb_date, sf_status, sf_invoice_num, spnsr_charge_id, spnsr_credit_id FROM apps.igf_db_awd_disb_dtl WHERE spnsr_charge_id = :p_charge_id;

A second common pattern lists disbursements for an award within a date range and evaluates fee and net amounts:

SELECT disb_num, disb_seq_num, disb_date, disb_gross_amt, fee_1, fee_2, disb_net_amt, disb_activity FROM apps.igf_db_awd_disb_dtl WHERE award_id = :p_award_id AND disb_date BETWEEN :p_from AND :p_to ORDER BY disb_num, disb_seq_num;

Because the view enforces multi-org security, callers must initialize the operating unit (via FND_CLIENT_INFO or an equivalent session setup) before querying, so results reflect only the current operating unit. Reporting on cross-operating-unit data requires querying the base table or using a multi-org aware reporting tool configured accordingly.