Search Results mrr_code2

Overview

IGF_GR_MRR is an Oracle E-Business Suite view in the APPS schema belonging to the IGF (Financial Aid) product family. It is a reporting and integration layer over the Pell Grant multiple reporting record (MRR) data captured during the financial aid process, presenting the MRR information in a flattened, ready-to-consume form for the institution. In EBS 12.1.1 and 12.2.2 the object exists with status VALID and follows the standard multi-org security pattern used by financial aid objects, meaning it is a secured view over a corresponding _ALL table rather than a base table itself.

Because the view exposes Pell Grant MRR information — award amounts, disbursement data, eligibility flags, institution information, and student identifiers — it serves as the primary source for extracts used to report to the U.S. Department of Education and for internal reconciliation of Pell grant activity. It is read-only and is not intended as a maintenance or update target.

Underlying Base Objects

The view text is defined over the single base object IGF_GR_MRR_ALL, aliased as GRMRR. The _ALL suffix and the presence of ORG_ID confirm that this is a multi-org enabled table and that the view applies the operating unit filter automatically. The documented base object list in the ETRM metadata is limited to this table, and no other joins are present in the view definition, so all columns originate from IGF_GR_MRR_ALL.

The security filter uses the standard EBS pattern based on USERENV('CLIENT_INFO'). The predicate pulls the first ten characters of the client info string and compares it to the ORG_ID column, defaulting to -99 where no value is available. As a result, rows returned depend on the operating unit set in the session, and callers querying outside an initialized multi-org context will see only the default ORG_ID rows.

Key Columns

• ROW_ID / MRR_ID — ROW_ID is the physical row identifier from the base table; MRR_ID is the logical primary key for the reporting record.
• RECORD_TYPE, MRR_CODE1, MRR_CODE2 — Classify the MRR record and its processing status.
• STUD_ORIG_SSN, CURRENT_SSN, STUD_LAST_NAME, STUD_FIRST_NAME, STUD_MIDDLE_NAME, STUD_DOB — Student identifiers and demographic data as received from the origination record.
• INST_PELL_ID, INST_NAME, INST_ADDR1, INST_ADDR2, INST_CITY, INST_STATE, ZIP_CODE — Institution identity and address used in the MRR submission.
• SCHD_PELL_GRANT, ORIG_AWD_AMT, DISB_ACCEPTED_AMT, TRAN_NUM — Scheduled and awarded Pell amounts, the disbursement amount accepted, and transaction sequencing.
• EFC, ENRL_DT, ELIGIBILITY_USED, ED_USE_FLAGS — Expected Family Contribution, enrollment date, and Department of Education eligibility indicators.
• ORIG_CREATION_DT, LAST_ACTIVE_DT, NEXT_EST_DISB_DT — Lifecycle dates used for reconciliation and forecasting.
• FAA_NAME, FAA_TEL, FAA_FAX, FAA_INTERNET_ADDR — Contact details of the financial aid administrator on record.
• ORG_ID — Operating unit; drives the multi-org security predicate.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the concurrent request context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also exposed.

Common Use Cases and Queries

The view is typically used to drive Pell MRR extracts, reconcile reported amounts against disbursements, and audit records by operating unit. A representative query retrieving the current operating unit's records for a given institution follows.

• Extracting all MRR records for the session operating unit: SELECT MRR_ID, RECORD_TYPE, STUD_ORIG_SSN, INST_NAME, SCHD_PELL_GRANT, ORIG_AWD_AMT, ORIG_CREATION_DT FROM IGF_GR_MRR ORDER BY ORIG_CREATION_DT DESC;
• Filing a Pell MRR extract for a specific institution: SELECT MRR_ID, STUD_LAST_NAME, STUD_FIRST_NAME, STUD_ORIG_SSN, TRAN_NUM, DISB_ACCEPTED_AMT, EFC FROM IGF_GR_MRR WHERE INST_PELL_ID = :p_inst_pell_id;
• Identifying recent active records for reconciliation: SELECT MRR_ID, LAST_ACTIVE_DT, NEXT_EST_DISB_DT, ELIGIBILITY_USED FROM IGF_GR_MRR WHERE LAST_ACTIVE_DT >= :p_from_date;

Because multi-org security is embedded in the view definition, no additional ORG_ID predicate is required; callers should ensure the correct operating unit is initialized in the session before executing queries.