Results for “fee_cal_inst_sequence_number”

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

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:

• IGS_FI_REFUNDS (aliased RE1) — the primary driver table holding refund transactions; also self-joined as RE2 via the outer join RE1.SOURCE_REFUND_ID = RE2.REFUND_ID(+) to relate reversal refunds back to the original refund.
• HZ_PARTIES — joined twice, as PA1 (refund person via RE1.PERSON_ID = PA1.PARTY_ID) and as PA2 (payee person via RE1.PAY_PERSON_ID = PA2.PARTY_ID).
• IGS_FI_FEE_TYPE_ALL — supplies the fee type description, keyed on FEE_TYPE.
• IGS_CA_INST_ALL — supplies the calendar instance (start date, end date, description, alternate code) via fee calendar type and sequence number.
• IGS_FI_INV_INT_ALL — supplies the invoice number for the refund.
• IGS_FI_ACC_ALL — joined twice (AC1 and AC2, outer) to resolve the debit and credit account code descriptions.
• GL_CODE_COMBINATIONS — joined twice (GCC1 and GCC2, outer) on DR_GL_CCID and CR_GL_CCID to supply the accounting flexfield combinations.

Key Columns

• REVERSAL_GL_DATE — the GL date assigned when a refund is reversed; directly relevant to the search term reversal_gl_date, and paired with REVERSAL_INDICATOR and REVERSAL_REASON to identify and contextualize reversed refunds.
• GL_DATE and VOUCHER_DATE — the accounting date and voucher date of the originating refund; a second VOUCHER_DATE is projected from RE2 for the source refund.
• REFUND_AMOUNT — the monetary value of the refund.
• FEE_TYPE, FEE_CALENDAR_TYPE, and FEE_CI_SEQUENCE_NUMBER — identify the fee and calendar instance to which the refund relates.
• DEBIT_ACCOUNT_CODE / CREDIT_ACCOUNT_CODE and DR_GL_CCID / CR_GL_CCID — the accounting distribution for the refund entry.
• PARTY_NUMBER / PARTY_NAME and PAYEE_PARTY_NUMBER / PAYEE_PARTY_NAME — identify the refunded party and the payee.
• REFUND_ID, SOURCE_REFUND_ID, PERSON_ID, PAY_PERSON_ID, INVOICE_ID — primary and foreign identifiers for integration.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

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.