Search Results rfms_process_dt




Overview
Explore in AI Chat

Overview

IGF_GR_RFMS_BATCH_V is a reporting and integration view in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, owned by the APPS schema. The IGF prefix places it within the Oracle Grants Accounting (formerly Oracle Grants Management) product family, while the RFMS component indicates the Federal grantee subsystem used for the Recipient Financial Management System reporting interface. The view presents batch-level metadata for data transmissions exchanged between an EBS Grants installation and an external sponsor or federal agency RFMS system.

The view is defined as a simple projection over the base table IGF_GR_RFMS_BATCH. According to the ETRM metadata, the documented view text is a straight SELECT of all columns from that table with no joins, filters, or expressions. Its principal role is therefore to provide a stable read-consistent interface for concurrent programs, OBIEE reports, and external integrations that need to inspect transmission batch state — for example, to determine which batches have been acknowledged by the recipient system and which were rejected. Presenting the columns as a view allows Oracle to change the underlying table structure without breaking downstream reporting code.

Underlying Base Objects

The single documented base object is the table IGF_GR_RFMS_BATCH. No join tables, indexes, or synonyms appear in the ETRM metadata beyond the schema qualification of APPS. Because the view references exactly one base table with no WHERE clause, the row count and column set of the view match the base table one-for-one.

Partitioning, indexes, and referential constraints on IGF_GR_RFMS_BATCH are not captured in the metadata provided. The transaction control columns at the end of the select list (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) are the standard EBS "who columns," populated automatically by the Forms and Concurrent Manager runtime.

Key Columns

  • ROW_ID — ROWID-based identifier used internally by Oracle for row addressing.
  • RFMB_ID — Primary key of the batch record; the natural identifier referenced by child transmission detail rows.
  • BATCH_ID — Business batch identifier assigned by the RFMS process or by the grantee system.
  • DATA_REC_LENGTH — Length, in characters or bytes, of the data record contained in the batch.
  • OPE_ID — Identifier of the operating unit or organization / operating entity that owns the batch. This is the column most frequently used to scope queries to a specific business unit when the EBS Grants module spans multiple organizations.
  • SOFTWARE_PROVIDOR — Name of the software provider that generated the transmission; note the historical spelling preserved in the base table.
  • RFMS_PROCESS_DT — Date the batch was processed by the RFMS receiving application.
  • RFMS_ACK_DT — Date the acknowledgement was received, distinguishing pending from completed transmissions.
  • RFMS_ACK_BATCH_ID — Batch identifier returned in the acknowledgement; useful for correlation when the outbound and inbound identifiers differ.
  • REJECT_REASON — Free-text or coded reason the receiving system rejected the batch; null when the batch was accepted.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID support lineage tracing back to the concurrent request that touched the row.

Common Use Cases and Queries

The most common scenario is monitoring the state of outbound federal grant transmissions. Reporting users filter on OPE_ID to constrain results to a single operating unit and use RFMS_ACK_DT to separate acknowledged batches from those still outstanding.

SELECT batch_id,
       rfms_process_dt,
       rfms_ack_dt,
       rfms_ack_batch_id,
       reject_reason
FROM   apps.igf_gr_rfms_batch_v
WHERE  ope_id = :p_ope_id
  AND  rfms_ack_dt IS NULL
ORDER BY rfms_process_dt DESC;

A second pattern identifies rejected batches requiring remediation:

SELECT batch_id, ope_id, software_providor, reject_reason
FROM   apps.igf_gr_rfms_batch_v
WHERE  reject_reason IS NOT NULL
  AND  rfms_process_dt BETWEEN :p_from AND :p_to;

Integrators use the view to pull acknowledgement data into an external reconciliation store, joining BATCH_ID and RFMS_ACK_BATCH_ID. Finally, support analysts trace an unexpected batch back to its originating concurrent request via REQUEST_ID combined with FND_CONCURRENT_REQUESTS, and confirm who last modified the row through LAST_UPDATED_BY. Because the view carries no filters, queries against large Grants installations should always restrict on OPE_ID or date columns to avoid full-table scans.