Results for “tot_accpt_amt”

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

Overview

IGF_AW_STUD_AWD_TOT_V is a Financial Aid (IGF) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a person-level aggregation of financial aid award activity, consolidating three monetary measures: total offered amount, total accepted amount, and total paid amount. Rather than storing transactional award detail, the view reduces potentially many award rows per student into a single summary record keyed by PERSON_ID.

The view is primarily consumed by Financial Aid reporting, inquiry screens, and downstream integration or analytics extracts that require per-student award totals without traversing the full award detail table. Because the name follows the IGF_AW_* naming convention, it belongs to the Award Management area of the Financial Aid product family. In ETRM documentation the view is listed with a VALID status and is described as storing the student total offered, accepted, and paid amounts. The user search term "tot_accpt_amt" corresponds directly to the TOT_ACCPT_AMT column exposed by this view, which is the aggregated accepted amount.

The view is defined with a filter on AWARD_STATUS restricted to 'OFFERED' and 'ACCEPTED'. Consequently, rows in a status such as declined, cancelled, or otherwise retired are excluded from all three totals. This status gate is important for consumers: the totals represent active award interest only, not the complete award history for the student.

Underlying Base Objects

The view is defined over two documented base objects joined by BASE_ID:

• IGF_AW_AWARD (alias AWD) — the award detail table supplying OFFERED_AMT, ACCEPTED_AMT, PAID_AMT, AWARD_STATUS, and BASE_ID. All three aggregated measures originate here.
• IGF_AP_FA_BASE_REC (alias FA) — the Financial Aid base record supplying PERSON_ID and BASE_ID. This table links the award to the individual student/aid applicant.

The join is AWD.BASE_ID = FA.BASE_ID, and grouping is performed by FA.PERSON_ID. Each monetary column is wrapped in SUM(NVL(column, 0)), so null amounts in the base award rows are treated as zero and never cause a total to become null. The ETRM metadata does not document additional referenced objects, so no further base tables are assumed.

Key Columns

• PERSON_ID — the grouping key; identifies the student or aid applicant. It is the join back to person-level master data.
• TOT_OFFRD_AMT — the sum of OFFERED_AMT across qualifying award rows; total aid offered to the person.
• TOT_ACCPT_AMT — the sum of ACCEPTED_AMT across qualifying award rows; the column referenced by the search term "tot_accpt_amt".
• TOT_PAID_AMT — the sum of PAID_AMT across qualifying award rows; total disbursed or paid aid.

Note that the SELECT list does not alias these aggregate expressions, but the ETRM column listing assigns the documented names above. Comparisons such as TOT_OFFRD_AMT vs. TOT_ACCPT_AMT vs. TOT_PAID_AMT are meaningful within a single person row because all three derive from the same status-filtered award population.

Common Use Cases and Queries

Typical uses include student-level aid summary reports, reconciliation of offered against accepted and paid amounts, and extraction of total accepted aid for downstream disbursement or analytics processing.

Retrieve totals for a specific person:

• SELECT person_id, tot_offrd_amt, tot_accpt_amt, tot_paid_amt FROM apps.igf_aw_stud_awd_tot_v WHERE person_id = :p_person_id;

Identify students with accepted aid not yet fully paid:

• SELECT person_id, tot_accpt_amt, tot_paid_amt, (tot_accpt_amt - tot_paid_amt) outstanding FROM apps.igf_aw_stud_awd_tot_v WHERE tot_accpt_amt > tot_paid_amt;

Join to person-level data for reporting:

• SELECT p.person_id, p.full_name, v.tot_offrd_amt, v.tot_accpt_amt, v.tot_paid_amt FROM apps.igf_aw_stud_awd_tot_v v, apps.per_all_people_f p WHERE v.person_id = p.person_id AND :eff_date BETWEEN p.effective_start_date AND p.effective_end_date;

All queries should be run in a reporting context given the aggregate nature of the view and its status filter.