Search Results ow_id

Overview

The IGF.IGF_AP_OUTCORR_WF table is a transaction staging and workflow-support table within the Oracle E-Business Suite Financial Aid module (IGF, based on the former Student Financial Aid / ISIR processing product line). It is owned by the IGF schema and resides in the APPS_TS_TX_DATA tablespace, with its unique index in APPS_TS_TX_IDX. The table holds transaction numbers for correction ISIR (Institutional Student Information Record) records that are not initiated by the school, storing the data elements required to construct message bodies for notifications dispatched through Oracle Workflow. In effect, it acts as an outbound correction workflow queue that bridges financial aid ISIR correction data and the Workflow notification infrastructure.

From a Data Vault modeling perspective, the heuristic classification is standalone. The table neither references nor is referenced by other database objects via foreign keys, and its single unique business candidate is the primary key column OW_ID. This suggests that IGF_AP_OUTCORR_WF behaves like a self-contained hub-like record set rather than a link or satellite dependent on other entities; it may be modeled as an independent hub in a Data Vault design, with no documented parent relationships in the ETRM metadata.

Key Information Stored

The table comprises ten documented columns. The most significant are:

• OW_ID (NUMBER 15) — Sequence-generated primary key identifier, serving both as the surrogate primary key (via IGF_AP_OUTCORR_WF_PK) and the unique business-key candidate (via unique index IGF_AP_OUTCORR_WF_U1). It is the primary join and correlation key for this object.
• PERSON_NUMBER (VARCHAR2 30) — The person number to whom the correction ISIR belongs, typically a student identifier.
• GIVEN_NAMES (VARCHAR2 301) — Name of the student associated with the correction ISIR.
• TRANSACTION_NUMBER (VARCHAR2 13) — Unique identifier for the ISIR transaction, used to correlate the correction record with ISIR processing.
• ITEM_KEY (VARCHAR2 80) — Holds the Workflow item key value used to attach data attributes to the notification message body, linking the record to a Workflow process instance.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and update metadata.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying outbound correction ISIRs awaiting Workflow notification, retrieving the person and name details for a given transaction, and reconciling Workflow notifications against their source correction records. A common query retrieves the notification-relevant attributes for a specific transaction:

• SELECT ow_id, person_number, given_names, transaction_number, item_key FROM igf.igf_ap_outcorr_wf WHERE transaction_number = :txn; — locates the record by ISIR transaction number.
• SELECT ow_id, person_number, item_key FROM igf.igf_ap_outcorr_wf WHERE person_number = :person; — lists pending corrections for a student.
• Joining ITEM_KEY to Oracle Workflow tables (WF_ITEMS, WF_NOTIFICATIONS) enables auditing of notification delivery for each outbound correction, supporting operational monitoring and reconciliation reporting.

Related Objects

The ETRM metadata documents that IGF_AP_OUTCORR_WF does not reference any database object and is referenced only by the synonym APPS.IGF_AP_OUTCORR_WF, which exposes it to the APPS schema for use by forms, concurrent programs, and Workflow background processes. Because no foreign keys are documented, joins are effectively logical rather than enforced. Significant related objects to consider when working with this table include:

• APPS.IGF_AP_OUTCORR_WF — the APPS-schema synonym through which application code accesses the table.
• Oracle Workflow tables (WF_ITEMS, WF_NOTIFICATIONS) — joined via ITEM_KEY to trace notification message bodies and delivery status.
• ISIR processing tables in the IGF schema — logically associated through TRANSACTION_NUMBER and PERSON_NUMBER for correction ISIR reconciliation.
• Workflow notification APIs (WF_NOTIFICATION.Send / WF_ENGINE) — the consumers that build and dispatch messages using the data staged in this table.

Because the object is classified as standalone and is documented as VALID in both ETRM 12.1.1 and 12.2.2 lineage, it can be queried directly without regard to referential integrity constraints.