Search Results igsfv_party_refunds




Overview
Explore in AI Chat

Overview

The IGSFV_PARTY_REFUNDS view is a read-only reporting object in the Oracle E-Business Suite Student System (IGS) module. It presents refund transactions created when a student or party accrues excess unapplied credits and those credits are returned rather than applied against outstanding charges. The view consolidates refund header data with the associated party identity, fee type, calendar instance, invoice, and accounting flexfield information, providing a single denormalized row per refund transaction suitable for reporting and downstream integration.

The view is defined in the APPS schema with a status of VALID and is declared WITH READ ONLY, meaning no DML may be issued against it. Because the definition exposes descriptive flexfield and key flexfield pseudo-columns (for example, _DF:IGS:IGS_FI_REFUNDS_FLEX and the _KF:SQLGL:GL# account generators), it is designed primarily for use by Oracle Forms, OAF pages, and XML/reporting tools that can resolve these tokens at runtime. When queried directly through SQL*Plus or a BI publisher, the flexfield tokens must be expanded to their stored underlying column values.

Underlying Base Objects

The view is built over nine documented base objects joined in a single SELECT:

Key Columns

Common Use Cases and Queries

A typical reconciliation report lists reversed refunds and their accounting dates:

  • SELECT refund_id, party_name, fee_type, refund_amount, reversal_gl_date FROM igsfv_party_refunds WHERE reversal_indicator = 'Y' ORDER BY reversal_gl_date;
  • Refunds awaiting transfer, using the transfer status lookup: SELECT refund_id, party_name, refund_amount FROM igsfv_party_refunds WHERE transfer_status = 'PENDING';
  • Fee-level refund analysis by calendar instance: SELECT fee_type, fee_calendar_type, SUM(refund_amount) FROM igsfv_party_refunds GROUP BY fee_type, fee_calendar_type;

Because the view is read-only, all access is reporting or extract oriented, and any correction to refund data must be performed against the IGS_FI_REFUNDS base table through supported application flows.