Search Results transaction_num_desc

Overview

IGF_GR_RFMS_V is a reporting view within the Oracle E-Business Suite IGF (Financial Aid) product family. Its documented purpose is to expose RFMS (Recipient Financial Management System) data that must be transmitted to the external RFMS system. In the context of Oracle EBS 12.1.1 and 12.2.2, this view functions as a staging and extraction layer, consolidating origination, ISIR, enrollment, disbursement, and batch metadata into a single queryable structure suitable for outbound interface processing.

The view is classified under the IGF - Financial Aid module, which is marked as obsolete in the ETRM documentation. This obsolescence reflects the eventual retirement of the legacy financial aid integration model in favor of successor architectures. Nevertheless, in environments where the view remains deployed, it serves as the primary read interface for RFMS-bound Pell Grant and related Title IV data.

The ETRM metadata explicitly states the view is "Not implemented in this database," meaning it may exist only in specific installations where the RFMS integration was configured. Reference documentation should therefore treat it as an optional, configuration-dependent object rather than a core EBS view.

Underlying Base Objects

The documented ETRM metadata records no referenced base objects, and the owner is unspecified. The view text, however, reveals a multi-table join. The principal source is the RFMS table, aliased RFMS, which supplies the ROW_ID and the bulk of the transactional and origination columns. The view joins to a calendar instance table (aliased CI) via CI_CAL_TYPE and CI_SEQUENCE_NUMBER, drawing ALTERNATE_CODE, START_DT, and END_DT.

A second join references an ISIR table (aliased ISIR), using ORIGINAL_SSN, ORIG_NAME_ID, and TRANSACTION_NUM to construct a derived TRANSACTION_NUM_DESC string. A further join links RFMS.BATCH_ID to an RFMB batch table (aliased RFMB), which contributes BATCH_ID and RFMS_PROCESS_DT. Finally, a person table (aliased PE) is joined to expose PERSON_NUMBER and a formatted FIRST_NAME || ', ' || LAST_NAME concatenation.

Because the documented referenced-object list is empty, the precise physical table names (for example, the exact ISIR and person tables) cannot be confirmed from the ETRM record alone and should be verified against the deployment's data dictionary.

Key Columns

• RFMS.ROW_ID, ORIGINATION_ID — Primary identifiers for the RFMS staging record and its origination linkage.
• CI_CAL_TYPE, CI_SEQUENCE_NUMBER, START_DT, END_DT — Academic calendar context for the award period.
• SYS_ORIG_SSN, SYS_ORIG_NAME_CD, TRANSACTION_NUM — Origination identity and the ISIR transaction reference.
• EFC, SECONDARY_EFC, SECONDARY_EFC_CD — Expected Family Contribution values, decoded through IGF_AW_GEN.LOOKUP_DESC calls.
• PELL_AMOUNT, FT_PELL_AMOUNT, COA_AMOUNT, PENDING_AMOUNT — Award and cost-of-attendance monetary fields.
• ENROLLMENT_STATUS, ENROLLMENT_DT, ACADEMIC_CALENDAR, PAYMENT_METHOD — Enrollment and disbursement attributes, each accompanied by a lookup-decoded description.
• VER_STATUS_CODE, ORIG_ACTION_CODE, ORIG_STATUS_DT, ORIG_REJECT_CODE — Verification and origination status indicators.
• RFMB.BATCH_ID, RFMS_PROCESS_DT — Batch grouping and processing date for the outbound submission.
• PERSON_NUMBER — The person identifier for cross-referencing to HR or student records.

Several RFMS columns (such as VER_STATUS_CODE, SECONDARY_EFC_CD, ENROLLMENT_STATUS, ACADEMIC_CALENDAR, and PAYMENT_METHOD) are paired with lookup-decoded text via IGF_AW_GEN.LOOKUP_DESC, delivering both code and description in a single row.

Common Use Cases and Queries

The view is typically queried to audit or extract records awaiting RFMS transmission, and to reconcile batch contents before submission.

• Retrieve RFMS-bound records for a given batch: SELECT row_id, origination_id, transaction_num, pell_amount, enrollment_status FROM igf_gr_rfms_v WHERE batch_id = :batch;
• Identify records pending processing by inspecting RFMS_PROCESS_DT and PENDING_AMOUNT.
• Reconcile decoded values against raw codes to validate lookup configuration.

Given the object's obsolete status and absent base-object documentation, any query should be validated against the specific 12.1.1 or 12.2.2 instance data dictionary before being relied upon in production reporting.