Results for “award_fmly_contribution_type”

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

Overview

IGF_AP_FA_BASE_REC is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the IGF (Financial Aid) product family. Its documented purpose is to hold summarized information for all financial aid processes associated with a single student for a given academic year. Rather than forcing reports and integrations to traverse the numerous transactional financial aid tables individually, the view consolidates the key status, need-analysis, verification, and packaging indicators into a single denormalized projection keyed primarily by base record identifier and student.

The view is defined as VALID in both the 12.1.1 and 12.2.2 releases, and is identified in ETRM as an APPS-owned VIEW. Its role is fundamentally read-oriented: it serves as the semantic layer over the financial aid base record, supporting institutional reporting, downstream data extracts, and integration surfaces that need a consolidated academic-year snapshot of a student's aid processing state.

Underlying Base Objects

The ETRM metadata for this object documents no explicitly referenced base tables, and the view's projection is sourced from a single aliased relation designated FABASE. The view text is therefore best understood as a SELECT over one underlying financial aid base record table, aliased FABASE, with the view exposing that table's columns alongside ROWID passthrough and two projected NULL placeholders. Because the documented metadata lists no referenced base objects, DBAs and developers should confirm the physical dependency by inspecting ALL_DEPENDENCIES and ALL_VIEWS in the target instance, as the base relation may be a table or another view within the IGF schema. The view remains in the APPS schema, so all references must be fully qualified as APPS.IGF_AP_FA_BASE_REC.

Key Columns

The projection exposes a broad set of financial aid attributes. Identity and key columns include BASE_ID, PERSON_ID, CI_CAL_TYPE, and CI_SEQUENCE_NUMBER, which together anchor a student's record to an academic calendar context, plus ORG_ID for multi-org partitioning and ROWID for row-level addressing. Need-analysis values are carried by EFC_F, EFC_I, NEED_F, and NEED_I. Verification and ISIR tracking are represented by VERIFICATION_PROCESS_RUN, INST_VERIF_STATUS and its date, FED_VERIF_STATUS and its date, MANUAL_VERIF_FLAG, NSLDS_ELIGIBLE, NSLDS_DATA_OVERRIDE_FLG, ISIR_STATUS, ISIR_CORR_STATUS, and their associated dates, along with EDE_CORRECTION_BATCH_ID and PAYMENT_ISIR_ID.

Cost of attendance and packaging information are exposed through COA_F, COA_I, COA_PELL, COA_FIXED, COA_PENDING, COA_CODE_I, PACKAGING_STATUS, PACKAGING_STATUS_DATE, PROF_JUDGEMENT_FLG, TOTAL_PACKAGE_OFFERED, and TOTAL_PACKAGE_ACCEPTED. Administrative and structural attributes include ADMSTRUCT_ID with ADMSEGMENT_1 through ADMSEGMENT_20, PACKSTRUCT_ID with PACKSEGMENT_1 onward, TARGET_GROUP, DISBURSEMENT_HOLD, FA_PROCESS_STATUS, FA_PROCESS_STATUS_DATE, and NOTIFICATION_STATUS. Two columns are projected as NULL and carry no functional data in this view.

Common Use Cases and Queries

Typical usage centers on academic-year snapshots of aid status and on integration extracts. A reporting query might retrieve a student's need and packaging state for a term:

• SELECT base_id, person_id, ci_cal_type, ci_sequence_number, efc_f, need_f, packaging_status, total_package_offered FROM apps.igf_ap_fa_base_rec WHERE person_id = :person_id AND ci_cal_type = :cal_type;
• SELECT person_id, isir_status, fed_verif_status, inst_verif_status, nsfds_eligible FROM apps.igf_ap_fa_base_rec WHERE org_id = :org_id AND packaging_status = 'A';
• Disbursement-hold and verification exception reporting keyed on DISBURSEMENT_HOLD, MANUAL_VERIF_FLAG, and the verif status dates.
• Admissions and packaging structure analysis using ADMSTRUCT_ID, PACKSTRUCT_ID, and their segment columns.

Because the view is denormalized and exposed in APPS, it is well suited to read-only reporting and extract jobs, but it should not be used as a target for DML. Consumers should confirm current column availability against their specific patch level, as financial aid objects are subject to regulatory-tracking updates.