Search Results rfms_ack_dt

Overview

IGF_GR_RFMS_BATCH_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGF (Financial Aid) product family and validated as VALID in both release 12.1.1 and 12.2.2. The view presents details of RFMS batch records — that is, batches transmitted to and acknowledged by the federal RFMS (Recipient and Financial Management System) used for Title IV student financial aid processing. Its purpose is to expose batch-level processing and acknowledgement data in a stable, query-friendly shape for reporting, reconciliation, and integration consumption, without requiring callers to read the underlying transaction table directly. This is particularly relevant to searches such as "rfms_ack_dt", since the view projects the RFMS_ACK_DT column that records the date on which RFMS acknowledged a submitted batch. Because it is a pure projection view — a single SELECT from one table with no joins, filters, or aggregation — it imposes no additional logic and simply renames nothing; every column maps one-to-one to a base table column.

Underlying Base Objects

The view is defined entirely over the base table IGF_GR_RFMS_BATCH. The documented view text is a straightforward SELECT ... FROM IGF_GR_RFMS_BATCH listing all columns without WHERE, GROUP BY, or DISTINCT clauses. No other referenced base objects are documented, and the view adds no derived expressions. Consequently, row cardinality is identical to that of the base table, and all DML must be performed against IGF_GR_RFMS_BATCH; the view is intended strictly for query access. Standard EBS who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) are carried through unchanged, preserving full audit and request traceability.

Key Columns

• ROW_ID — surrogate identifier for the batch record.
• RFMB_ID — primary key of the RFMS batch row in IGF_GR_RFMS_BATCH.
• BATCH_ID — the batch identifier assigned to the submitted RFMS file or transmission.
• DATA_REC_LENGTH — length of the data record within the batch.
• OPE_ID — Office of Postsecondary Education identifier of the institution.
• SOFTWARE_PROVIDOR — software provider code associated with the batch submission.
• RFMS_PROCESS_DT — date the batch was processed.
• RFMS_ACK_DT — date RFMS acknowledged the batch; central to acknowledgement tracking and reconciliation queries.
• RFMS_ACK_BATCH_ID — acknowledgement batch identifier returned by RFMS.
• REJECT_REASON — reason code or text explaining why a batch was rejected.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Concurrent program columns — PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.

Common Use Cases and Queries

Typical uses include identifying batches still awaiting acknowledgement, isolating rejected transmissions for remediation, and correlating RFMS activity to the concurrent request that produced it. Queries commonly filter on RFMS_ACK_DT, join to request metadata via REQUEST_ID, or group by OPE_ID for institutional summaries. Because the view is unfiltered, always constrain on dates or identifiers to limit row counts on large institutions.

• Pending batches: SELECT RFMB_ID, BATCH_ID, RFMS_PROCESS_DT FROM IGF_GR_RFMS_BATCH_V WHERE RFMS_ACK_DT IS NULL;
• Acknowledgement date window: SELECT BATCH_ID, RFMS_ACK_DT, RFMS_ACK_BATCH_ID FROM IGF_GR_RFMS_BATCH_V WHERE RFMS_ACK_DT BETWEEN :p_start AND :p_end;
• Reject review: SELECT BATCH_ID, RFMS_ACK_DT, REJECT_REASON FROM IGF_GR_RFMS_BATCH_V WHERE REJECT_REASON IS NOT NULL;
• Request traceability: SELECT BATCH_ID, REQUEST_ID, PROGRAM_ID FROM IGF_GR_RFMS_BATCH_V WHERE REQUEST_ID = :p_request_id;