Search Results auth_date




Overview
Explore in AI Chat

Overview

APPS.IGF_SE_EARNINGS_SUMMARY_V is a reporting view in the Oracle E-Business Suite Financials/Student Systems family, residing in the IGF (Grants/Financial Aid) schema. It consolidates award-level disbursement data into a summary of amounts awarded, amounts paid to date, remaining balances, and progress toward an award limit. The view is defined specifically for the Federal Work-Study (FWS) program, as evidenced by the filter AWD.FED_FUND_CODE = 'FWS', and is intended to support earnings monitoring, limit tracking, and downstream notification workflows for financial aid administrators. From an integration standpoint, the view presents a stable, denormalized projection that reporting tools, concurrent programs, or external consumers can query without needing to join award, disbursement, and calendar-instance tables directly.

The inclusion of the notification_sent column is significant in the context of the user search term. Although the column is populated as a literal NULL in the view definition, its presence signals that the view is designed as a template for earnings-limit notification logic, where a consumer or a derived query can overlay notification state (whether an alert has been sent, when, and under what authorization) onto computed earnings summary data.

Underlying Base Objects

The view is defined over three documented source objects:

Joins are performed on AWARD_ID between the award and disbursement objects, and on (CAL_TYPE, SEQUENCE_NUMBER) between the disbursement records and the calendar instance. The result set is grouped by BASE_ID, FUND_ID, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, and ALTERNATE_CODE, producing one summarized row per award-fund-period combination. No additional base objects are documented for this view in the ETRM metadata.

Key Columns

  • BASE_ID, FUND_ID — identify the award base record and the funding source.
  • LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_ALTERNATE_CODE — identify the loan/period calendar instance and its human-readable alternate code.
  • AWARD_AMOUNT — derived conditionally: if the sum of accepted disbursement amounts is zero, the sum of gross amounts is used; otherwise the sum of accepted amounts. This reflects the accepted-versus-gross distinction in disbursement accounting.
  • EARNINGS_TILL_DATE — the sum of DISB_PAID_AMT, representing amounts actually paid.
  • REMAINING_AMOUNT — computed as AWARD_AMOUNT minus EARNINGS_TILL_DATE.
  • PROGRESS_TO_LIMIT — computed as ROUND(EARNINGS_TILL_DATE/AWARD_AMOUNT) * 100, used to gauge utilization.
  • NOTIFICATION_SENT, NOTIFICATION_DATE, AUTH_ID, AUTH_DATE — exposed as NULL placeholders, reserved for notification tracking and authorization metadata.

Common Use Cases and Queries

Typical uses include monitoring FWS earnings against award limits, identifying awards nearing their limit, and driving notification routines. A representative query filters rows exceeding a utilization threshold:

  • SELECT base_id, fund_id, ld_alternate_code, award_amount, earnings_till_date, remaining_amount, progress_to_limit FROM apps.igf_se_earnings_summary_v WHERE progress_to_limit >= 80;
  • Aggregation by fund: SELECT fund_id, SUM(earnings_till_date) FROM apps.igf_se_earnings_summary_v GROUP BY fund_id;
  • Notification template selection: SELECT base_id, ld_alternate_code, notification_sent FROM apps.igf_se_earnings_summary_v;

Because NOTIFICATION_SENT is currently NULL, consumers typically join or union the view with a notification tracking table or apply their own state logic. Reporting users should treat the notification columns as placeholders pending underlying logic, and validate AWARD_AMOUNT arithmetic where accepted amounts are zero to avoid division issues in PROGRESS_TO_LIMIT.