Results for “correction_status”

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

Overview

IGF_AP_ISIR_CORR_ALL is a Financial Aid module table in Oracle EBS 12.1.1 and 12.2.2 that stores ISIR (Institutional Student Information Record) correction records. In the ISIR processing lifecycle, the U.S. Department of Education transmits ISIR data to institutions for each student applicant, and when corrections are requested or applied to that data—either by the student or by the institution—those changes are captured in this table. Each row represents a single field-level correction associated with a specific ISIR record, preserving the original value, the corrected value, and the status of the correction transaction. In the ETRM 12.1.1 metadata the object is documented under the IGF product with an "Obsolete" designation, and the implementation note states "Not implemented in this database," indicating that the table exists in the data model for historical or reference purposes even where it has not been physically created in a given environment.

Because this table holds the intersection between an ISIR (the matched student record) and an academic calendar instance, the ETRM relationship metadata suggests a Data Vault classification of link. In Data Vault modeling terms, a link resolves a many-to-many association between business entities and carries descriptive context. IGF_AP_ISIR_CORR_ALL fits that pattern by connecting an ISIR (through ISIR_ID) and an academic calendar instance (through CI_CAL_TYPE and CI_SEQUENCE_NUMBER), with the correction specifics as dependent attributes.

Key Information Stored

The table is documented with 19 columns. The most significant are summarized below; the surrogate primary key is distinct from the business-key candidates defined by unique indexes.

• ISIRC_ID — Surrogate primary key (IGF_AP_ISIR_CORR_ALL_PK); a system-generated identifier for the correction row. It is also carried by the unique index IGF_AP_ISIR_CORR_ALL_U1.
• ISIR_ID — Foreign key to IGF_AP_ISIR_MATCHED_ALL; identifies the ISIR record to which the correction applies.
• CI_CAL_TYPE and CI_SEQUENCE_NUMBER — Foreign key to IGS_CA_INST_ALL; together they identify the academic calendar instance associated with the correction.
• SAR_FIELD_NUMBER — The SAR (Student Aid Report) field number being corrected, linking the row to a specific ISIR data element.
• ORIGINAL_VALUE and CORRECTED_VALUE — The pre-correction and post-correction values, preserving an audit trail of the change.
• CORRECTION_STATUS — The processing state of the correction; combined with ISIR_ID and SAR_FIELD_NUMBER in unique index IGF_AP_ISIR_CORR_ALL_U2.
• BATCH_ID — Groups corrections submitted or received together as a batch.
• ORG_ID — Operating unit identifier, supporting multi-org security and reporting filters.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns that identify the process that created or last modified the row.

The business key is effectively (ISIR_ID, SAR_FIELD_NUMBER, CORRECTION_STATUS), as documented by U2, while ISIRC_ID serves as the technical primary key.

Common Use Cases and Queries

Typical usage focuses on correction auditing and reconciliation between the institution and the Department of Education. Common patterns include:

• Retrieving all corrections for a specific ISIR: SELECT isirc_id, sar_field_number, original_value, corrected_value, correction_status FROM igf_ap_isir_corr_all WHERE isir_id = :p_isir_id;
• Listing pending or rejected corrections by status: SELECT * FROM igf_ap_isir_corr_all WHERE correction_status = :p_status AND org_id = :p_org_id;
• Reporting corrections by academic calendar instance: join on CI_CAL_TYPE and CI_SEQUENCE_NUMBER to IGS_CA_INST_ALL.
• Auditing concurrent processing: grouping by REQUEST_ID and BATCH_ID to trace corrections produced by a specific run.

Because the object is marked obsolete and not implemented in the database, these patterns are primarily relevant for historical data migration, documentation of legacy behavior, and impact analysis when upgrading between 12.1.1 and 12.2.2.

Related Objects

The documented relationships anchor this table to the following objects:

• IGF_AP_ISIR_MATCHED_ALL — joined via ISIR_ID; the parent matched-ISIR record whose corrections are stored here.
• IGS_CA_INST_ALL — joined via CI_CAL_TYPE and CI_SEQUENCE_NUMBER; provides the academic calendar instance context.

In a functional ISIR correction implementation, related access is typically performed through the ISIR matching and correction APIs and concurrent programs that populate IGF_AP_ISIR_MATCHED_ALL and its correction detail. Any DBA or developer querying IGF_AP_ISIR_CORR_ALL should first confirm physical existence, since the ETRM record explicitly states the table is not implemented in the documented database.