Search Results igf_ap_outcorr_wf

Overview

The IGF_AP_OUTCORR_WF table is a Financial Aid (IGF) module object within the Oracle E-Business Suite database, owned by the IGF schema and documented as VALID in ETRM for releases 12.1.1 and 12.2.2. It holds the transaction numbers for correction ISIR (Institutional Student Information Record) records that are not initiated by the school. Its functional purpose is to stage the data elements required to construct the message body for notifications dispatched through Oracle Workflow, enabling automated alerting when a student or external party submits a correction rather than the institution.

From a heuristic Data Vault classification mined from the foreign-key structure, the table is modeled as standalone, with no dependent relationships to other parent or child entities. In Data Vault terms this suggests a hub-like role anchored on a single business identifier, with no satellite or link dependencies implied by the current FK metadata.

Key Information Stored

The table contains ten documented columns. The surrogate primary key is OW_ID, enforced by the constraint IGF_AP_OUTCORR_WF_PK. A unique index, IGF_AP_OUTCORR_WF_U1, is also defined on OW_ID, making it both the technical key and the documented business-key candidate. The most significant data-bearing columns are:

• OW_ID — surrogate primary key and unique business-key candidate; the Workflow dispatch identifier for the correction notice.
• PERSON_NUMBER — the student or person identifier associated with the correction ISIR.
• GIVEN_NAMES — the name component used when populating the notification message body.
• TRANSACTION_NUMBER — the ISIR transaction number for the correction record, the core business value carried by the row.
• ITEM_KEY — the Oracle Workflow item key linking the row to its running workflow process instance.
• CREATED_BY, CREATION_DATE — standard audit columns recording row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the last modification and the login context.

The pair of audit column groups follows the conventional EBS WHO-column pattern, supporting traceability and concurrent-program reconciliation.

Common Use Cases and Queries

Because the table is a workflow-staging object, the primary operational use case is notification processing and troubleshooting. Typical queries include:

• Identifying outstanding correction notifications for a person: SELECT TRANSACTION_NUMBER, ITEM_KEY FROM IGF.IGF_AP_OUTCORR_WF WHERE PERSON_NUMBER = :person;
• Joining on ITEM_KEY to the Workflow runtime tables to determine notification status and confirm whether the message body was successfully built.
• Audit reporting on creation versus last-update timestamps to detect rows that were staged but never dispatched.
• Reconciliation against the originating correction ISIR records to confirm transaction numbers were staged exactly once, leveraging the UNIQUE index on OW_ID.

Reporting should generally treat the table as a transient queue rather than a permanent history, since rows exist to support notification construction.

Related Objects

The documented FK metadata classifies the table as standalone, so no enforced parent-child relationships are recorded. Practically, the most significant related objects are the Workflow runtime entities reached through ITEM_KEY, the correction ISIR data structures that supply TRANSACTION_NUMBER, and the person tables behind PERSON_NUMBER. Referential joins should therefore be made explicitly on documented columns rather than assumed foreign keys, and consumers should query IGF.IGF_AP_OUTCORR_WF with the IGF schema prefix to avoid synonym ambiguity in multi-org environments.