Results for “igf_gr_rfms_batch”

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

Overview

The IGF_GR_RFMS_BATCH view is a Financial Aid (IGF) product database object owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It exposes batch-level records associated with the RFMS (Record Format Management System) interface used to transmit Title IV student financial aid data between Oracle EBS and the U.S. Department of Education's Common Origination and Disbursement (COD) system. The view presents metadata about each RFMS batch, including the batch identifier, processing and acknowledgement dates, acknowledgement batch identifiers, rejection reasons, and standard Oracle WHO columns for auditing and concurrent program tracking.

Functionally, the view acts as an application-level, operating-unit-secured presentation layer over the underlying batch table. It is primarily consumed by Financial Aid batch extracts, reconciliation reports, and integration routines that need to enumerate RFMS transmissions and their outcomes. Because it enforces multi-org access through the ORG_ID predicate, it is typically invoked in a session where CLIENT_INFO has been initialized through FND_CLIENT_INFO or an equivalent multi-org setup routine.

Underlying Base Objects

The view is defined over a single base object: IGF_GR_RFMS_BATCH_ALL. This base table is a multi-org (per-operating-unit) table, indicated by the "_ALL" suffix and the presence of the ORG_ID column. The view filters the base table with the standard Oracle multi-org security predicate:

• It compares RFMSBT.ORG_ID against the operating unit value parsed from USERENV('CLIENT_INFO'), specifically the first ten characters of CLIENT_INFO.
• When CLIENT_INFO is blank or null, the NVL/DECODE logic substitutes -99, meaning only rows with ORG_ID of -99 (or null, evaluated through the same path) are returned.
• ROW_ID is projected from the base table's ROWID, providing a pseudo-key for the view.

The view is read-only with respect to DML; any insert, update, or delete must be performed against IGF_GR_RFMS_BATCH_ALL. The ETRM metadata documents no additional referenced objects, so the view is a direct, single-table projection.

Key Columns

• ROW_ID — ROWID of the underlying row, useful for locating the base record.
• RFMB_ID — Primary identifier of the RFMS batch record.
• BATCH_ID — Business batch identifier used in RFMS transmissions.
• DATA_REC_LENGTH — Length of the data record within the batch.
• OPE_ID — Office of Postsecondary Education identifier for the institution.
• SOFTWARE_PROVIDOR — Software provider code (note the original spelling) associated with the batch.
• RFMS_PROCESS_DT — Date the batch was processed.
• RFMS_ACK_DT — Date the batch was acknowledged by the receiving system.
• RFMS_ACK_BATCH_ID — Batch identifier returned in the acknowledgement.
• REJECT_REASON — Reason code or text describing why a batch was rejected.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit (WHO) columns.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Concurrent program and request context columns.
• ORG_ID — Operating unit that owns the batch.

Common Use Cases and Queries

Typical uses include monitoring RFMS batch transmissions, identifying unacknowledged batches, and diagnosing rejections. A representative query lists unacknowledged batches for the current operating unit:

SELECT batch_id, rfmb_id, ope_id,
       rfms_process_dt, rfms_ack_dt, reject_reason
  FROM apps.igf_gr_rfms_batch
 WHERE rfms_ack_dt IS NULL
 ORDER BY rfms_process_dt;

Reconciliation reporting compares processed and acknowledged dates, while rejection analysis filters on REJECT_REASON. Because the view applies multi-org security automatically, the query above returns only rows visible to the session's operating unit. Scripts requiring cross-org access should query IGF_GR_RFMS_BATCH_ALL directly with an explicit ORG_ID predicate.