Search Results igs_fi_refunds_v




Overview

The IGS_FI_REFUNDS_V view belongs to the IGS – Student System product family within Oracle E-Business Suite, a module now classified as obsolete in ETRM. The view presents a consolidated, denormalized picture of refund transactions generated whenever excess unapplied credits exist on a student or third-party account. Rather than requiring a report or interface to join refund, party, calendar, invoice, and account lookups manually, IGS_FI_REFUNDS_V exposes a single flat record per refund row, enriched with the payee's identity and descriptive meaning for the transfer status.

From a reporting and integration standpoint, the view functions as a convenience layer over the IGS Financials refund model. It is typically consumed by refund inquiry screens, financial extracts, accounts payable interfaces, and custom reconciliation reports that need to trace the origin, GL impact, and payment disposition of a refund. Because refunds arise from unapplied credits, the view also serves as an audit trail linking student fee credits to the subsequent disbursement.

Underlying Base Objects

The view is defined over a join of eight base objects. The driving table is IGS_FI_REFUNDS RFND, which stores the refund transaction itself. Ancillary descriptive data is joined through:

Most joins are inner joins except the invoice and account lookups, which are outer joins (denoted by the (+) syntax), so refund rows are not lost when an invoice or account description is absent.

Key Columns

Common Use Cases and Queries

Typical usage includes refund reporting by payee, reconciliation against GL distributions, and extraction of refunds for a given fee calendar instance.

  • List refunds for a payee:

SELECT refund_id, voucher_date, full_name, refund_amount, payment_number FROM igs_fi_refunds_v WHERE pay_person_id = :p_person_id ORDER BY voucher_date;

  • Refunds by transfer status within a date range:

SELECT refund_id, person_number, refund_amount, meaning FROM igs_fi_refunds_v WHERE transfer_status = :status AND voucher_date BETWEEN :from_date AND :to_date;

Because the module is obsolete and the object is not implemented in the current database, references should be confirmed against the target instance before reliance.