Results for “igs_pe_nonimg_stat_pk”

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

Overview

IGS_PE_NONIMG_STAT is a transactional table in the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It captures status-tracking information associated with non-image forms processed by the institution. In the ETRM metadata this object is classified as a link table under the heuristic Data Vault model — a suggestion that it resolves a many-to-many or event-based relationship between a form definition and a point-in-time status action, rather than standing alone as an independent hub or satellite. In practice, the table records the lifecycle of each non-image form: when an action was taken, what type of action it was, and the program period and termination context relevant to that form. The table resides in the IGS schema and is owned by the Student System footprint, meaning its use is tightly coupled to the higher-education enrollment and admissions flows delivered with the Oracle Student System.

Key Information Stored

The documented physical schema contains 15 columns. The most operationally significant are:

• NONIMG_STAT_ID — the surrogate primary key (IGS_PE_NONIMG_STAT_PK). It uniquely identifies each status row and is the column to use in joins to child or dependent records.
• NONIMG_FORM_ID — foreign key to IGS_PE_NONIMG_FORM. It ties each status record back to the specific non-image form it describes.
• ACTION_TYPE and ACTION_DATE — together with NONIMG_FORM_ID these form the business-key candidate IGS_PE_NONIMG_STAT_U1. ACTION_TYPE identifies the nature of the status event, while ACTION_DATE timestamps it.
• PRGM_START_DATE and PRGM_END_DATE — define the program period the form status applies to.
• TERMINATION_REASON — records the reason associated with a termination action, where applicable.
• REMARKS — free-text annotation for the status record.
• CANCEL_FLAG and PRINT_FLAG — indicator columns controlling cancellation status and whether the form is flagged for printing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns, identifying who created and last modified the row and when.

The distinction between the surrogate key (NONIMG_STAT_ID) and the unique business key (NONIMG_FORM_ID, ACTION_TYPE, ACTION_DATE) is important: the surrogate key should be used for referential joins, while the unique index enforces that a given form cannot have two identical action-type-and-date combinations.

Common Use Cases and Queries

The table is most commonly queried to report on the status history of non-image forms — for example, tracking admissions or enrollment forms through submission, processing, printing, and termination stages. A typical pattern joins back to the form definition:

• Status history per form: SELECT s.NONIMG_STAT_ID, s.ACTION_TYPE, s.ACTION_DATE, s.CANCEL_FLAG FROM IGS.IGS_PE_NONIMG_STAT s WHERE s.NONIMG_FORM_ID = :form_id ORDER BY s.ACTION_DATE;
• Terminated forms within a period: filter on TERMINATION_REASON IS NOT NULL and PRGM_END_DATE range.
• Print-queue reporting: filter on PRINT_FLAG = 'Y' and CANCEL_FLAG = 'N' to identify forms still awaiting output.
• Audit and reconciliation: expose CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to show who touched a form status and when.

Because the table is an event-style link, replicated reporting schemas often use it as the fact source for form-lifecycle dashboards.

Related Objects

• IGS_PE_NONIMG_FORM — the parent object referenced twice via NONIMG_FORM_ID. This is the primary join target and the most significant related table.
• IGS_PE_NONIMG_STAT_PK — the primary key constraint/index on NONIMG_STAT_ID.
• IGS_PE_NONIMG_STAT_U1 — the unique index on (NONIMG_FORM_ID, ACTION_TYPE, ACTION_DATE) enforcing the business key.
• Standard EBS audit and concurrent-program objects that consume CREATED_BY / LAST_UPDATED_BY values (for example, FND_USER) are commonly joined for name resolution in reporting.

Where the ETRM extract is limited, the FK evidence points to IGS_PE_NONIMG_FORM as the sole documented parent, so any wider relationship model should be validated against the site's actual IGS configuration before being relied upon.