Results for “disb_ytd_amt”

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

Overview

The IGF_GR_RFMS_DISB_V view is a reporting and integration object within the Oracle E-Business Suite IGF — Financial Aid product, owned by the APPS schema. Its documented purpose is to expose recipient financial management system (RFMS) disbursement data, meaning the disbursement records that flow between a financial aid institution's grant management subsystem and the external recipient financial management system used to release and acknowledge funds. The view has a status of VALID and is available in both 12.1.1 and 12.2.2.

Because financial aid disbursements must be reconciled against batch processing and acknowledgement cycles, the view serves as a denormalized read model. It joins disbursement detail to its parent batch so that consumers can report on individual awards as well as the batch context in which they were transmitted. This makes the view well suited for extracts, interface programs, and operational reporting rather than for transactional data entry. The column PYMT_PRD_START_DT, which is the field the user searched for, represents the payment period start date carried on the disbursement record and is one of the period-identification attributes used to align funding to an academic or award payment window.

Underlying Base Objects

The view is defined over two documented base tables:

• IGF_GR_RFMS_DISB (aliased RFMD) — the primary disbursement detail table, supplying all core disbursement, acknowledgement, and audit columns.
• IGF_GR_RFMS_BATCH (aliased RFMB) — the parent batch table, supplying batch-level processing attributes.

The join is an outer join: WHERE RFMB.RFMB_ID(+) = RFMD.RFMB_ID. This is significant because it means every disbursement row is returned even when no matching batch exists, so batch columns such as BATCH_ID and RFMS_PROCESS_DT may be null for orphaned or not-yet-batched disbursements. Reporting logic must therefore handle nullable batch fields. The view exposes no aggregations or filters; it is a straight projection of selected columns from the two tables, preserving row-level grain at the disbursement level.

Key Columns

• ROW_ID, RFMD_ID — primary and surrogate identifiers for the disbursement record.
• ORIGINATION_ID, DISB_REF_NUM — origination reference and the disbursement reference number used for reconciliation with the external system.
• DISB_DT, DISB_AMT, DB_CR_FLAG — the disbursement date, amount, and debit/credit indicator.
• DISB_ACK_ACT_STATUS, DISB_STATUS_DT — acknowledgement action status and the date the status was set.
• ACCPT_DISB_DT, DISB_ACCPT_AMT, ACCPT_DB_CR_FLAG — the accepted disbursement date, accepted amount, and its debit/credit flag.
• PYMT_PRD_START_DT, ACCPT_PYMT_PRD_START_DT — the payment period start date on the original disbursement and on the accepted disbursement respectively.
• DISB_YTD_AMT, EDIT_CODE — year-to-date disbursement amount and any edit or validation code returned by RFMS processing.
• RFMB_ID, BATCH_ID, RFMS_PROCESS_DT — batch identity and RFMS processing date (nullable due to the outer join).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ED_USE_FLAGS — standard audit and extensibility columns.

Common Use Cases and Queries

Typical scenarios include reconciliation of disbursed versus accepted amounts, batch-level extraction to RFMS, and period-based funding analysis keyed on PYMT_PRD_START_DT.

SELECT d.disb_ref_num,
       d.disb_dt,
       d.pymt_prd_start_dt,
       d.disb_amt,
       d.disb_acct_amt,
       d.disb_ack_act_status,
       b.batch_id,
       b.rfms_process_dt
FROM   apps.igf_gr_rfms_disb_v d
WHERE  d.pymt_prd_start_dt BETWEEN :start_date AND :end_date
ORDER  BY d.pymt_prd_start_dt, d.disb_dt;

A second common pattern aggregates accepted amounts by batch to verify that transmitted and acknowledged totals agree:

SELECT b.batch_id,
       SUM(d.disb_amt)      total_disbursed,
       SUM(d.disb_acct_amt) total_accepted
FROM   apps.igf_gr_rfms_disb_v d,
       apps.igf_gr_rfms_batch   b
WHERE  d.rfmb_id = b.rfmb_id
GROUP  BY b.batch_id;

Because the view is a simple, non-aggregated projection, it can be queried directly without concern for grouping artifacts, though callers should remember that batch columns are outer-joined and may require null handling in reporting logic.