Search Results batch_year_num

Overview

IGF_AP_ISIR_INTS is a view owned by the APPS schema within the IGF (Financial Aid) product family of Oracle E-Business Suite, and it carries a VALID status in both 12.1.1 and 12.2.2. Its documented purpose is to serve as the ISIR Interface view for holding Institutional Student Information Records (ISIRs) received from the Central Processing System (CPS). In the financial aid lifecycle, the CPS returns ISIRs to institutions after a student submits a Free Application for Federal Student Aid (FAFSA); this view is the staging surface through which that inbound data is made available to the Oracle Financial Aid application and to any downstream reporting or integration processes.

Functionally, the view presents one row per ISIR record with a wide, flattened column set covering student identity data, citizenship and selective service information, marital and dependency status, enrollment status across academic terms, and detailed parental and student income/asset figures. Because it is a view rather than a table, it also exposes a synthetic ROW_ID column derived from ROWID for use by Oracle Forms and generic maintenance frameworks.

Underlying Base Objects

The view text is a single SELECT statement. It projects columns directly (SI_ID, BATCH_YEAR_NUM, TRANSACTION_NUM_TXT, and many others) rather than performing joins or aggregations, and the ETRM metadata for 12.2.2 records no referenced base objects and no owner beyond the APPS schema. No ON clause, WHERE clause, or subordinate table reference appears in the documented view text, indicating a straightforward projection layer over a single physical ISIR staging table.

Practically, this means the view is a stable, read-oriented access point: the physical staging table holds the CPS payload, and IGF_AP_ISIR_INTS normalizes the column naming and surfaces the data for the financial aid modules and for ad hoc SQL. Because no base objects are documented, the actual underlying table name is not fixed in ETRM and should be confirmed by querying ALL_VIEWS / DBA_VIEWS on the target instance before any DML-dependent design is undertaken.

Key Columns

• SI_ID — Student Identifier (person/student record key) tying the ISIR to the aid applicant.
• BATCH_YEAR_NUM — The award/batch year associated with the ISIR load; the term the user searched for and the primary grouping key for annual processing.
• TRANSACTION_NUM_TXT — CPS transaction number distinguishing successive ISIR corrections for the same student.
• Identity columns — CURRENT_SSN_TXT, ORIGINAL_SSN_TXT, SSN_NAME_CHANGE_TYPE, LAST_NAME, FIRST_NAME, MIDDLE_INITIAL_TXT, BIRTH_DATE.
• CITIZENSHIP_STATUS_TYPE, ALIEN_REG_NUMBER_TXT, SELECTIVE_SERVICE_REG_FLAG — eligibility-determining attributes.
• S_MARITAL_STATUS_TYPE, S_MARRIED_FLAG, LEGAL_DEPENDENTS_FLAG, P_FAMILY_MEMBERS_NUM, P_IN_COLLEGE_NUM — independence and household-size factors.
• Enrollment columns — SUMM_ENRL_STATUS_TYPE, FALL_ENRL_STATUS_TYPE, WINTER_ENRL_STATUS_TYPE, SPRING_ENRL_STATUS_TYPE, SUMM2_ENRL_STATUS_TYPE.
• Need-analysis amounts — S_ADJUSTED_GROSS_INCOME_AMT, F_INCOME_WORK_AMT, M_INCOME_WORK_AMT, P_ADJUSTED_GROSS_INCOME_AMT, S_INVESTMENT_NETWORTH_AMT, S_BUSI_FARM_NETWORTH_AMT.

Common Use Cases and Queries

Typical uses include confirming that an ISIR was received and staged for a given year, reconciling CPS transaction versions, and feeding downstream packaging or verification logic. A representative query lists staged ISIRs for a batch year:

• SELECT si_id, batch_year_num, transaction_num_txt, last_name, first_name FROM igf_ap_isir_ints WHERE batch_year_num = :p_year ORDER BY si_id, transaction_num_txt;
• SELECT COUNT(*) FROM igf_ap_isir_ints WHERE batch_year_num = :p_year; — volume check per load cycle.
• SELECT row_id, si_id, current_ssn_txt FROM igf_ap_isir_ints WHERE ssn_name_change_type IS NOT NULL; — flag SSN/name corrections.

Because the view derives ROW_ID from ROWID, queries used by the Forms layer typically retrieve ROW_ID alongside the business keys.