Search Results igf_ap_st_inst_appl_all

Overview

The table IGF_AP_ST_INST_APPL_ALL is a data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically designed for the now-obsolete IGF (Financial Aid) module. Its primary function is to store the specific answers provided by applicants to user-defined questions configured within the financial aid application process. This table operates as a transactional detail table, capturing the dynamic data entered by students against a defined set of institutional questions. It is a multi-organization table, as indicated by the "_ALL" suffix, meaning it stores data partitioned by the ORG_ID column for multiple operating units. The provided metadata explicitly states it is "Not implemented in this database," which typically indicates the table structure exists in the application but may not be populated or actively used in a given instance, often due to module decommissioning or specific implementation choices.

Key Information Stored

The table's structure is centered on linking a student's financial aid record to specific questions and their responses. The critical columns, as defined by its primary and unique keys, are INST_APP_ID (the surrogate primary key), BASE_ID (linking to the student's base financial aid record), QUESTION_ID (linking to the question definition), and APPLICATION_CODE (categorizing the application context). Other columns would typically include the actual answer value (potentially in a column like ANSWER_VALUE or similar, though not explicitly listed in the provided metadata), creation and last update dates, and the ORG_ID. The integrity of the data is enforced by a unique key constraint (IGF_AP_ST_INST_APPL_ALL_UK) on the combination of BASE_ID, QUESTION_ID, and APPLICATION_CODE, ensuring a student cannot have multiple answers for the same question within the same application code.

Common Use Cases and Queries

The primary use case for this table is reporting and decision logic based on custom institutional questions in the financial aid workflow. Administrators could query it to review applicant responses for audit purposes, populate need-analysis calculations, or filter applicants based on specific criteria. A typical SQL query would join this table to the student base record and question setup tables to produce a readable report. For example, to retrieve all answers for a specific application, one might use a pattern such as:

SELECT b.person_id, q.question_short_name, a.answer_value
FROM igf_ap_st_inst_appl_all a,
igf_ap_fa_base_rec_all b,
igf_ap_appl_setup_all q
WHERE a.base_id = b.base_id
AND a.question_id = q.question_id
AND a.application_code = 'INST_AWARD';

Data maintenance would typically occur through the application's user interface, not via direct SQL manipulation.

Related Objects

IGF_AP_ST_INST_APPL_ALL is a central component in a relational cluster within the Financial Aid module. Its documented foreign key relationships are as follows:

• IGF_AP_FA_BASE_REC_ALL: This is the foundational table for a student's financial aid record. The column IGF_AP_ST_INST_APPL_ALL.BASE_ID references this table, linking every question answer to a specific student and aid year.
• IGF_AP_APPL_SETUP_ALL: This table defines the configurable questions themselves. The column IGF_AP_ST_INST_APPL_ALL.QUESTION_ID references IGF_AP_APPL_SETUP_ALL, ensuring every stored answer corresponds to a valid, pre-defined question.
• Self-Reference (APPLICATION_CODE, BASE_ID): The metadata indicates a foreign key where the table references itself on the APPLICATION_CODE and BASE_ID columns. This suggests a possible hierarchical relationship between application codes or a validation constraint within an applicant's record set.

These relationships are essential for constructing complete joins to retrieve meaningful student, question, and answer data in a single query.