Search Results last_active_dt

Overview

IGF_GR_MRR is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Financial Aid module within the Oracle Student System / financial aid grantor reporting footprint (FND Design Data: IGF.IGF_GR_MRR). The object is registered as a multi-org view, meaning it is defined over a base entity that carries an ORG_ID discriminator and is filtered by the Multi-Org security model so that a query returns only rows belonging to the current operating unit. This behaviour allows institutions running multiple operating units to report Pell Grant and related Title IV grantor data on a per-operating-unit basis without exposing disbursement or origination records from other units.

The view presents the Master Record Report (MRR) style data set: grant origination and disbursement information exchanged between institutions and the Department of Education, keyed to a student and an institution Pell identifier. Because the naming and the presence of columns such as REQ_INST_PELL_ID, ORIG_AWD_AMT, DISB_ACCEPTED_AMT, TRAN_NUM and EFC correspond to the Common Origination and Disbursement (COD) record layout, the view is typically used as an integration and reconciliation surface rather than an operational data-entry form. The object status is VALID, confirming the view compiles successfully in the certified release.

Underlying Base Objects

The ETRM metadata for IGF_GR_MRR documents no referenced base objects, and the published dependency list contains only the view itself. No base tables are enumerated in the provided metadata, and the object carries no documented subobject name. Cautiously, the view is understood to be defined over the IGF grantor reporting base entity in the IGF schema segment (IGF_GR_MRR is prefixed with the IGF application short name), with the multi-org clause enforcing ORG_ID = the session operating unit.

After a database upgrade from 12.1.1 to 12.2.2, the view may become invalid if a base column changes; the standard APPS compilation utilities such as ADODDL or the concurrent program "Compile Invalid Objects" regenerate it. Since the metadata does not enumerate the base tables, treat the underlying relationships as documentation-limited and verify the view source directly in the database using DBMS_METADATA.GET_DDL or DBA_VIEWS before building dependent logic.

Key Columns

• ROW_ID / MRR_ID — ROWID pseudo-column and the numeric master record identifier used to join or uniquely address a report row.
• RECORD_TYPE — Distinguishes record variants within the MRR data set.
• REQ_INST_PELL_ID, MR_INST_PELL_ID, INST_PELL_ID — Institution Pell identifiers for the requesting, matched and reporting institutions.
• INST_NAME, INST_ADDR1, INST_ADDR2, INST_CITY, INST_STATE, ZIP_CODE — Institutional name and address details.
• STUD_ORIG_SSN and CURRENT_SSN — The student's Social Security Number at origination and the current SSN on file; CURRENT_SSN is the column most commonly used for identity matching against current records.
• STUD_LAST_NAME, STUD_FIRST_NAME, STUD_MIDDLE_NAME, STUD_DOB — Student name and date of birth attributes used for reporting and reconciliation.
• ORIG_AWD_AMT, SCHD_PELL_GRANT, DISB_ACCEPTED_AMT — Awarded, scheduled and accepted disbursement amounts in the report currency.
• EFC — Expected Family Contribution, the need-analysis figure associated with the award.
• ENRL_DT, ORIG_CREATION_DT, LAST_ACTIVE_DT, NEXT_EST_DISB_DT — Enrolment, origination, last activity and next estimated disbursement dates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent request tracking for records produced by a submission program.
• ORG_ID — Operating unit discriminator enforced by the multi-org view definition.

Common Use Cases and Queries

Typical uses include reconciling origination records against current student identifiers, resolving records where the origination SSN differs from the current SSN, and reviewing award versus accepted disbursement amounts per Pell identifier. The following queries are illustrative and should be validated against the customer's data model.

• Locate records where the current SSN has moved away from the origination SSN: SELECT MRR_ID, STUD_ORIG_SSN, CURRENT_SSN, STUD_LAST_NAME, STUD_FIRST_NAME FROM APPS.IGF_GR_MRR WHERE CURRENT_SSN <> STUD_ORIG_SSN;
• Report outstanding award versus disbursement amounts for the operating unit: SELECT INST_PELL_ID, MRR_ID, ORIG_AWD_AMT, DISB_ACCEPTED_AMT, EFC FROM APPS.IGF_GR_MRR WHERE ORIG_AWD_AMT > NVL(DISB_ACCEPTED_AMT,0);
• Identify records produced by a specific concurrent submission: SELECT MRR_ID, REQUEST_ID, TRAN_NUM, ORIG_CREATION_DT FROM APPS.IGF_GR_MRR WHERE REQUEST_ID = :req_id;
• Trace recent activity for an institution: SELECT MRR_ID, CURRENT_SSN, STUD_LAST_NAME, LAST_ACTIVE_DT, NEXT_EST_DISB_DT FROM APPS.IGF_GR_MRR WHERE INST_PELL_ID = :pell_id ORDER BY LAST_ACTIVE_DT DESC;

Because the view is multi-org enabled and the base objects are not documented in ETRM, all custom queries should be executed from an APPS-responsibility session (MO: Operating Unit secured) to ensure ORG_ID filtering is applied, and column-level existence should be confirmed against the deployed view definition in each environment.