Results for “igffv_stu_inst_applications”

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

Overview

The view IGFFV_STU_INST_APPLICATIONS (Student Institution Applications) belongs to the Oracle Financial Aid product family, identified under the IGF module. The ETRM metadata explicitly classifies IGF – Financial Aid as Obsolete, meaning the object is retained for historical, migration, or archival reference rather than for active functional use in Oracle EBS 12.1.1 or 12.2.2. The view exposes the responses submitted by applicants to institution-defined, user-configurable questions captured during the financial aid application process. Its documented purpose is to contain the values for all user-defined questions, presenting the question text, the associated award year (institution calendar instance), and the corresponding answer.

The view is defined as a read-only construct, enforced by the trailing WITH READ ONLY clause in its definition, and is joined across five base tables rather than materialized independently. This makes it a reporting-oriented object: it consolidates party identity, application instance data, question setup, and answer values into a single denormalized presentation layer suitable for queries, extracts, and integration views. The metadata also records that the view is not implemented in this database, indicating availability depends on the installation of the IGF product and its dependent schema objects.

Underlying Base Objects

The view text identifies the following referenced base objects:

• IGF_AP_ST_INST_APPL_ALL (aliased SIA) — the student institution application records holding the question-to-answer assignments, application codes, and audit columns. This is the primary driving table.
• IGF_AP_FA_BASE_REC_ALL (aliased FA_DETAIL) — the financial aid base record linked via BASE_ID, supplying the person identifier.
• HZ_PARTIES (aliased HP) — the Trading Community Architecture party registry, supplying PARTY_NAME and PARTY_NUMBER.
• IGF_AP_APPL_SETUP_ALL (aliased IAS) — application setup mapping the question identifier and application code to a calendar type and sequence number.
• IGS_CA_INST_ALL (aliased CI) — the institution calendar instance defining the award year, providing alternate code and description.

Joins are established on BASE_ID (SIA to FA_DETAIL), PERSON_ID to PARTY_ID (FA_DETAIL to HZ_PARTIES), QUESTION_ID and APPLICATION_CODE (SIA to IAS), and calendar type/sequence number (IAS to CI).

Key Columns

• PERSON_NAME / PERSON_NUMBER — Party name and party number from HZ_PARTIES, identifying the applicant.
• QUESTION — The text of the user-defined question from the application setup.
• QUESTION_VALUE — The applicant-supplied answer to the corresponding question; the column most directly associated with the user's search term.
• AWARD_YEAR / AWARD_YEAR_DESCRIPTION — Alternate code and description of the institution calendar instance.
• INST_APP_ID, BASE_ID, QUESTION_ID — Surrogate keys linking the answer to its application, base record, and question definition.
• APPLICATION_CODE — Identifier of the application setup context.
• PERSON_ID — Internal party identifier.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical usage involves retrieving applicant responses for institution-specific questions, filtered by award year or applicant. For example:

SELECT person_name, person_number, question, question_value
FROM igffv_stu_inst_applications
WHERE application_code = :application_code
AND award_year = :award_year;

Because the view is read-only, it supports reporting and downstream integration extracts only. Given the Obsolete product designation, any consumption should be validated against the specific 12.1.1 or 12.2.2 environment, since the metadata confirms the object may not be implemented in every database.