Search Results voucher_date




Overview
Explore in AI Chat

Overview

IGS_FI_REFUND_INT is a public APPS-schema view in the Oracle E-Business Suite Student System (IGS) product family. It serves as an interface view for transferring student refund data to Oracle Payables, presenting refund transactions in a structure suitable for generating accounts payable invoices and payments. The view is catalogued as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its primary integration role is to expose refund records—including debit and credit accounting flexfield combinations, refund amounts, fee attributes, and payment instructions—so that downstream Oracle Payables processes can create supplier invoices, credit memos, and payments for student refunds.

The column DR_GL_CCID, which the user searched for, is a core element of this view: it carries the debit General Ledger Code Combination ID (CCID) that determines the accounting entry generated on the debit side of a refund. Its counterpart CR_GL_CCID carries the credit side. Together they drive the accounting distribution written to Oracle Payables and subsequently to Oracle General Ledger.

Underlying Base Objects

Per documented view text, IGS_FI_REFUND_INT is defined over the base table IGS_FI_REFUND_INT_ALL. The view selects ROWID and a defined column list from that single base object. No additional referenced base objects are documented in ETRM metadata, so the view's data set is derived entirely from IGS_FI_REFUND_INT_ALL, which itself is multipurpose (the _ALL suffix indicating an org-striped table governed by ORG_ID and, in some deployments, row-level security via MO or a similar operating-unit policy). Consequently, IGS_FI_REFUND_INT exposes the same rows as its base table, filtered by whatever security context is applied to the base object. Because the view is a straightforward projection without joins or transformations, its cardinality and refresh characteristics mirror IGS_FI_REFUND_INT_ALL exactly. The view does not cache data; it reflects the base table in real time.

Key Columns

Common Use Cases and Queries

Typical use cases include reconciling refunds headed to Payables, verifying debit/credit CCID assignments, and diagnosing accounting issues. A representative query to inspect debit CCID assignments is:

SELECT refund_id, dr_gl_ccid, cr_gl_ccid,
       dr_account_cd, cr_account_cd, refund_amount
FROM   apps.igs_fi_refund_int
WHERE  org_id = :p_org_id;

To audit refunds awaiting payment, filter by refund amount and payment attributes:

SELECT refund_id, pay_person_id, refund_amount,
       payment_number, payment_mode, gl_date
FROM   apps.igs_fi_refund_int
WHERE  refund_amount > 0
AND    gl_date BETWEEN :start_date AND :end_date;

For integration troubleshooting, join DR_GL_CCID to GL_CODE_COMBINATIONS to confirm the account string resolves correctly:

SELECT r.refund_id, r.dr_gl_ccid,
       g.segment1||'.'||g.segment2 AS dr_account_string
FROM   apps.igs_fi_refund_int r,
       apps.gl_code_combinations g
WHERE  r.dr_gl_ccid = g.code_combination_id;