Search Results igf_gr_rfms_disb




Overview

The view IGF_GR_RFMS_DISB belongs to the Oracle EBS IGF – Financial Aid product family, a module that has since been classified as Obsolete within the E-Business Suite documentation set. The view exposes disbursement records associated with the Real-time Financial Management System (RFMS) integration used by the former financial aid solution. Its name decomposes into an "IGF" product prefix, a grants/RFMS grouping ("GR_RFMS"), and a "DISB" suffix denoting disbursement-level detail. In practical terms, the view presents a reporting-friendly projection over the disbursement staging table IGF_GR_RFMS_DISB_ALL, applying a Multi-Org security predicate so that only rows belonging to the caller's current operating unit are visible.

The ETRM documentation explicitly records "Not implemented in this database" for this object in the source environment, meaning the view must be validated against the actual target instance rather than assumed to exist. Where it is deployed, it functions as a security-bound read layer rather than as a data-generating mechanism.

Underlying Base Objects

The view text defines a single-source select from IGF_GR_RFMS_DISB_ALL, aliased as RFMD. There are no joins, unions, or subqueries; the only transformation applied is the row-level operating unit filter embedded in the WHERE clause. The filter uses USERENV('CLIENT_INFO'), extracting the first ten bytes and converting them to a number, compared against ORG_ID. The default sentinel value -99 is applied when no client information is available.

Because the view is defined over an _ALL table, it is a Multi-Org secured ("_V" style) view. Conceptually it is paired with an unsecured or differently scoped variant, but the ETRM summary does not document a sibling IGF_GR_RFMS_DISB base view, only the secured wrapper shown here. No other referenced base objects are documented beyond IGF_GR_RFMS_DISB_ALL.

Key Columns

Common Use Cases and Queries

Typical usage involves reconciliation of financial aid disbursements, audit reporting, and troubleshooting of RFMS acknowledgement failures. Because the view is org-secured, queries must be executed in a session where CLIENT_INFO is populated (for example, through a concurrent program or a Forms session).

List recent disbursements for the current organization:

  • SELECT rfmd_id, disb_ref_num, disb_dt, disb_amt, disb_ack_act_status FROM igf_gr_rfms_disb WHERE disb_dt >= SYSDATE - 30 ORDER BY disb_dt DESC;

Aggregate accepted versus original amounts by edit code to locate RFMS validation problems:

  • SELECT edit_code, COUNT(*) rows_ct, SUM(disb_amt) disb_total, SUM(disb_accpt_amt) accepted_total FROM igf_gr_rfms_disb GROUP BY edit_code;

Join to the RFMS batch header to review disbursements by batch, using RFMB_ID. Organisations that have retired the Financial Aid module should treat this object as historical only; because ETRM records it as obsolete and "not implemented in this database," existence checks against DBA_VIEWS and dependency queries against DBA_DEPENDENCIES are recommended before relying on it in any migration or custom report.