Search Results auto_correction

Overview

The IGF.IGF_AP_GEN_SETUP_ALL table belongs to the Oracle EBS Financial Aid (IGF) product family, which supports the administration of student aid within Oracle Student System and related modules. The object stores general setup information for the Financial Aid application, most notably the operating unit–level configuration flags that govern Financial Aid Base Record creation and Need Analysis processing. The ETRM metadata describes the table as "Obsolete," reflecting the fact that Oracle has superseded the functionality it once supported in later releases; however, in Oracle EBS 12.1.1 and 12.2.2 environments where the IGF schema remains present, the table is still a VALID database object and its contents may still be referenced by legacy customizations, data conversions, and integrations.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This means the table has no documented parent or child foreign-key relationships within the mined schema graph and therefore is best modeled as an independent satellite-like construct keyed on its own surrogate identifier, rather than as a link or hub integrated into a networked relationship model.

Key Information Stored

IGF_AP_GEN_SETUP_ALL contains twelve documented columns, of which the following are the most significant:

• GENST_ID (NUMBER(15), mandatory) — The surrogate primary key, enforced by the unique index IGF_AP_GEN_SETUP_PK. It uniquely identifies each general setup row.
• ORG_ID (NUMBER(15)) — The operating unit identifier, which determines the multi-org context in which the setup row applies. This is the primary business-key candidate alongside GENST_ID.
• SSN_REQUIRED (VARCHAR2(30)) — Indicates whether a Social Security Number is required for Financial Aid Base Record creation.
• AUTO_NA_COMPLETE (VARCHAR2(30)) — Indicates whether a user is permitted to update the Financial Aid Process Status to Need Analysis Complete for a student.
• AUTO_CORRECTION (VARCHAR2(30)) — Documented as obsolete; retained for backward compatibility.
• TRIGGER_WF (VARCHAR2(30)) — Documented as obsolete; historically related to workflow triggering.
• UPDATE_AWARD_STATUS (VARCHAR2(30)) — Documented as obsolete, and the column the user's search term referenced. Although superseded, it historically governed whether award status updates could be applied automatically during Financial Aid processing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "who" audit columns maintained by Oracle Application Object Library (FND) for every transactional and setup row.

The unique index IGF_AP_GEN_SETUP_PK on GENST_ID is the sole documented business-key candidate; no other unique constraints are recorded.

Common Use Cases and Queries

The most frequent operational use of this table is to read or update the operating-unit-level Financial Aid configuration flags. A typical query retrieving setup for a specific operating unit is:

• SELECT GENST_ID, ORG_ID, SSN_REQUIRED, AUTO_NA_COMPLETE, UPDATE_AWARD_STATUS FROM IGF.IGF_AP_GEN_SETUP_ALL WHERE ORG_ID = :org_id;
• Reporting on the population of obsolete columns such as UPDATE_AWARD_STATUS to determine whether legacy logic may still be active: SELECT ORG_ID, UPDATE_AWARD_STATUS FROM IGF.IGF_AP_GEN_SETUP_ALL WHERE UPDATE_AWARD_STATUS IS NOT NULL;
• Auditing who last modified setup: SELECT GENST_ID, ORG_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGF.IGF_AP_GEN_SETUP_ALL ORDER BY LAST_UPDATE_DATE DESC;

Because the table is obsolete, DBAs and developers generally restrict themselves to read-only extracts and do not extend the schema. Any DML should be performed through the supported IGF setup forms rather than direct SQL, to preserve downstream consistency.

Related Objects

The ETRM metadata records that IGF_AP_GEN_SETUP_ALL does not reference any database object, and that the only documented referencing object is the APPS synonym IGF_AP_GEN_SETUP_ALL, which exposes the table to the APPS schema. Because the mined schema shows no FK dependencies, the principal related objects are the APPS-layer synonyms and views used by Financial Aid forms, concurrent programs, and legacy conversions, rather than relational child tables. Joins to other IGF setup or operational tables are therefore typically made on ORG_ID rather than through a formal foreign key, and any such joins should be validated against the actual IGF data model in the target environment before being embedded in production code.