Results for “rfms_ack_batch_id”

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

Overview

The IGF_GR_RFMS_BATCH_ALL table belongs to the IGF (Financial Aid) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores details of RFMS (Records and File Management System) batch records, acting as the header-level container that groups individual RFMS disbursement and record transactions under a common batch identifier. RFMS is the U.S. Department of Education's system for exchanging Title IV student financial aid data; in Oracle EBS, this table captures the metadata that accompanies each batch transmitted to or received from that external system, including acknowledgement dates, reject reasons, and the software provider that generated the file. The ETRM metadata classifies this product as Obsolete and notes the table is not implemented in the reference database, meaning it appears primarily in historical or legacy financial aid implementations rather than active installations.

From a Data Vault modeling perspective, the FK structure mined from the ETRM metadata yields a hub-leaning classification. The table functions as the anchor for the RFMB_ID business key, with two downstream tables referencing it via foreign keys. This suggests it is best treated as a hub entity, with its descriptive attributes (dates, reject reasons, provider information) modeled as satellite data in a dimensional or Data Vault design.

Key Information Stored

The table contains 19 documented columns. The single-column surrogate primary key IGF_GR_RFMS_BATCH_ALL_PK is defined on RFMB_ID, and a unique index IGF_GR_RFMS_BATCH_ALL_U1 also exists on RFMB_ID, making it both the surrogate key and the sole business-key candidate.

• RFMB_ID — Primary key and unique business key; identifies each RFMS batch record.
• BATCH_ID — External or internal batch identifier used to correlate the record with the transmitted file.
• OPE_ID — Identifier for the Office of Postsecondary Education (OPE) code associated with the institution.
• SOFTWARE_PROVIDOR — Name or identifier of the software provider that generated the RFMS file.
• RFMS_PROCESS_DT — Date the batch was processed by RFMS.
• RFMS_ACK_DT — Date the batch acknowledgement was received from RFMS.
• RFMS_ACK_BATCH_ID — Batch identifier returned in the RFMS acknowledgement, used for reconciliation.
• REJECT_REASON — Reason code or text explaining why a batch was rejected.
• DATA_REC_LENGTH — Length of the data record, relevant to fixed-width file parsing.
• ORG_ID — Operating unit identifier, enabling multi-org data segregation.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID — support concurrency control and concurrent program traceability.

Common Use Cases and Queries

Typical reporting scenarios centre on batch reconciliation, acknowledgement tracking, and rejection analysis. A common pattern joins the batch header to its disbursement and record detail tables to reconstruct the full transmission history.

• Identify batches awaiting acknowledgement: SELECT rfmb_id, batch_id, rfms_process_dt FROM igf_gr_rfms_batch_all WHERE rfms_ack_dt IS NULL;
• Aggregate rejection reasons for a given operating unit: SELECT reject_reason, COUNT(*) FROM igf_gr_rfms_batch_all WHERE org_id = :org_id GROUP BY reject_reason;
• Reconcile acknowledged batches by matching BATCH_ID to RFMS_ACK_BATCH_ID.
• Trace batch processing to the concurrent request that created it via REQUEST_ID and PROGRAM_ID.

Related Objects

The ETRM metadata documents two FK relationships in which other tables reference this object's RFMB_ID primary key:

• IGF_GR_RFMS_DISB_ALL.RFMB_ID → IGF_GR_RFMS_BATCH_ALL.RFMB_ID — disbursement detail lines belonging to each batch.
• IGF_GR_RFMS_ALL.RFMB_ID → IGF_GR_RFMS_BATCH_ALL.RFMB_ID — the parent RFMS record header linked to the batch.

These two child tables should be treated as the primary dependents for any join, reporting, or data-migration effort involving this batch header.