Search Results nonimg_form_id




Overview
Explore in AI Chat

Overview

The IGS.IGS_PE_NONIMG_STAT table is a transactional data object within the Oracle E-Business Suite Student Systems (IGS) schema. It stores the status history of non-immigrant student forms recorded in the institution's student information model, capturing every action taken against a non-immigrant record — program starts, program ends, terminations, extensions, and cancellations. The table resides in the APPS_TS_TX_DATA tablespace, indicating transactional rather than reference or interface usage. It is registered in FND Design Data as IGS.IGS_PE_NONIMG_STAT and is marked VALID in the ETRM 12.1.1 repository.

From a data modeling perspective, the heuristic classification of this object is a link entity. It sits between an identified business subject (the non-immigrant form) and the set of dated action events that affect it. The row-level identity is carried by NONIMG_STAT_ID, while NONIMG_FORM_ID anchors the row to its parent form; the combination of form, action type, and action date forms a natural business key. This structure supports a link/satellite pattern in which status changes are append-only event records rather than overwritten attributes.

Key Information Stored

The table contains fifteen documented columns. The most operationally significant are:

  • NONIMG_STAT_ID — NUMBER(15), the surrogate primary key maintained by IGS_PE_NONIMG_STAT_PK. It uniquely identifies a single status event.
  • NONIMG_FORM_ID — NUMBER(15), the foreign key to IGS_PE_NONIMG_FORM. This is the first column of the unique index IGS_PE_NONIMG_STAT_U1, which enforces uniqueness across form, action type, and action date.
  • ACTION_TYPE — VARCHAR2, describing the nature of the status action (for example an extension, termination, or reinstatement).
  • ACTION_DATE — DATE, the effective date of the action taken.
  • PRGM_START_DATE and PRGM_END_DATE — the revised program window associated with the action, used when an action extends or alters program enrollment.
  • TERMINATION_REASON — VARCHAR2(30), the coded reason when the student's non-immigrant status has been terminated.
  • REMARKS — VARCHAR2(500), free-text commentary recorded by the user performing the action.
  • PRINT_FLAG — VARCHAR2, indicating whether correspondence must be printed for the event.
  • CANCEL_FLAG — VARCHAR2, indicating that a program extension associated with the event has been canceled.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — provide the audit trail and are populated automatically by the framework.

The surrogate key NONIMG_STAT_ID should not be mistaken for the business key. The unique index IGS_PE_NONIMG_STAT_U1 on (NONIMG_FORM_ID, ACTION_TYPE, ACTION_DATE) is the documented business-key candidate, preventing duplicate status events of the same type on the same date for a given form.

Common Use Cases and Queries

The primary use case is reconstructing the status timeline of a non-immigrant student. A typical reporting query retrieves all status events for a form in chronological order:

  • SELECT NONIMG_STAT_ID, ACTION_TYPE, ACTION_DATE, PRGM_START_DATE, PRGM_END_DATE, TERMINATION_REASON FROM IGS.IGS_PE_NONIMG_STAT WHERE NONIMG_FORM_ID = :form_id ORDER BY ACTION_DATE;
  • Tracking pending print actions: filter on PRINT_FLAG to identify correspondence queued for generation.
  • Auditing cancellations: filter on CANCEL_FLAG to report program extensions that were reversed.
  • Termination analysis: aggregate on TERMINATION_REASON and ACTION_DATE to produce regulatory or institutional trend reports.
  • Audit queries: join the WHO columns to FND_USER to attribute each action to a user and timestamp.

Because the table is append-oriented, consumers generally avoid updates and instead insert a new status row for each change, preserving the historical record.

Related Objects

The primary dependency is the parent form table:

  • IGS.IGS_PE_NONIMG_FORM — referenced through NONIMG_FORM_ID. This is the only documented foreign key target and the principal join path for all reporting.
  • APPS.IGS_PE_NONIMG_STAT — the APPS-level synonym/view through which application code and reports access the base table.
  • FND_USER — joined via CREATED_BY and LAST_UPDATED_BY for user attribution.
  • FND_ID_FLEX_STRUCTURES / lookup tables — commonly joined on ACTION_TYPE or TERMINATION_REASON where these values are drawn from Oracle lookups rather than coded values.

The table itself does not reference any further database objects, confirming its position as a leaf-level detail table beneath IGS_PE_NONIMG_FORM.