Search Results payee_party_number




Overview
Explore in AI Chat

Overview

IGSBV_PARTY_REFUNDS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data IGS.IGSBV_PARTY_REFUNDS. It is part of the Oracle Student System / Financials integration layer associated with the IGS (Student Systems) product family. The view exposes refund transactions generated when excess unapplied credits exist on a student or party account, providing a consolidated, denormalized picture of each refund event.

Because it is a BIS view rather than a transactional table, its primary role is read-only reporting and downstream integration. Operational users and integrators query it to review refund activity, trace voucher creation, confirm whether a refund has been reversed, and drive interfaces that transfer records into refund processing. The view surfaces descriptive context—party and payee names, calendar and fee type descriptions, and account code strings—alongside the underlying identifiers, which makes it suitable for ad hoc reporting without requiring joins to multiple base tables.

Underlying Base Objects

The ETRM metadata for this object does not document the referenced base tables. In practice, IGSBV_PARTY_REFUNDS is defined over the IGS refund processing structures that hold refund voucher records and their reversal entries, together with joined lookup tables that supply fee type, calendar, and party/payee attributes. Columns prefixed with the interface convention (for example, _LA:TRANSFER_STATUS) indicate that the view also derives values from interface-selection logic used by concurrent processes to identify records not yet transferred to the Refunds Interface.

The view is therefore best understood as a presentational layer: it aggregates the refund voucher header, its General Ledger distributions, the associated party and payee identity, and calendar-effectivity context into a single row per refund transaction. Because no base objects are documented, dependency analysis should be performed against the IGS schema in the target instance (for example, via ALL_DEPENDENCIES) before relying on any assumed lineage.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling refund vouchers against GL distributions, auditing reversals, monitoring the interface backlog, and extracting refund detail for student financials reporting.

Listing unreversed refunds for a party:

SELECT party_number, party_name, refund_amount, gl_date
FROM   apps.igsbv_party_refunds
WHERE  reversal_indicator IS NULL
AND    party_number = :party_number;

Auditing reversals and their reasons:

SELECT party_number, refund_amount, reversal_reason,
       reversal_gl_date, voucher_date
FROM   apps.igsbv_party_refunds
WHERE  reversal_indicator IS NOT NULL;

Monitoring records awaiting interface transfer:

SELECT charge_number, party_name, refund_amount
FROM   apps.igsbv_party_refunds
WHERE  "_LA:TRANSFER_STATUS" = 'TODO';

Queries against the _LA: prefixed column must quote the identifier exactly as defined. As with all APPS BIS views, access is governed by grants and row-level security; ensure the reporting responsibility or custom role holds the appropriate privileges.