Search Results override_reason




Overview
Explore in AI Chat

Overview

IGS.IGS_PS_WL_OVER_RESN is a reference (lookup) table within the Oracle E-Business Suite IGS schema, which supports the Student Systems / Higher Education product family in releases 12.1.1 and 12.2.2. The table stores institution-defined override reasons that are applied when a student's expected workload is manually overridden. In this capacity it functions as a controlled vocabulary of justification codes, ensuring that any deviation from a calculated or default expected workload is accompanied by a valid, auditable explanation.

The object carries a VALID status and is registered under the FND Design Data identifier IGS.IGS_PS_WL_OVER_RESN. Physically it resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its unique index is held separately in APPS_TS_TX_IDX. Under the heuristic Data Vault classification supplied in the metadata, this table is identified as hub-leaning: it encapsulates a stable, uniquely identified business concept (the override reason) that other transaction-shaped tables reference by key. The modeling suggestion is therefore to treat OVERRIDE_REASON as a hub key, with descriptive attributes such as DESCRIPTION and CLOSED_IND behaving as lightweight satellite content.

Key Information Stored

The table contains eight documented columns. The most significant are:

  • OVERRIDE_REASON (VARCHAR2, 30) — Institution-defined override reason. This is both the primary key (IGS_PS_WL_OVER_RESN_PK) and the single-column business key enforced by the unique index IGS_PS_WL_OVER_RESN_U1 (NORMAL, UNIQUE, APPS_TS_TX_IDX). In this table the surrogate and business key coincide on the same column.
  • DESCRIPTION (VARCHAR2, 80) — A human-readable description of the override reason, used in list-of-values (LOV) displays and reporting output.
  • CLOSED_IND (VARCHAR2) — Indicator determining whether a given override reason is currently valid (open) or has been retired. This drives the availability of the value in transaction entry screens.

The remaining documented columns are the standard WHO audit attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These are maintained automatically and are not intended for user entry, but they are essential for audit trails and incremental (delta) extraction of changed reference data.

Common Use Cases and Queries

The primary use case is populating pick-lists and validating user input when an expected workload override is captured. Administrators maintain reason codes here; downstream transaction tables store only the OVERRIDE_REASON value, keeping the definition centralized.

A typical LOV population query restricts to open reasons only:

  • SELECT override_reason, description FROM igs.igs_ps_wl_over_resn WHERE closed_ind = 'N' ORDER BY override_reason;

A reporting query joining the reason to the overriding transaction, to produce workload override justifications by reason:

  • SELECT f.override_reason, r.description, COUNT(*) FROM igs.igs_ps_fac_ovr_wl f JOIN igs.igs_ps_wl_over_resn r ON f.override_reason = r.override_reason GROUP BY f.override_reason, r.description;

Because CLOSED_IND is not part of the unique key, closed reasons may still be referenced by historical records. Analysts should therefore avoid inner-joining strictly on open status when reconciling historical override activity. For delta loads, filter on LAST_UPDATE_DATE.

Related Objects

The relationship data identifies one direct referencing table, making this a hub-style reference object:

  • IGS_PS_FAC_OVR_WL — references this table via OVERRIDE_REASON (FK: IGS_PS_FAC_OVR_WL.OVERRIDE_REASON → IGS.IGS_PS_WL_OVER_RESN). This is the principal consumer, storing expected-workload override transactions whose reason must resolve here.
  • The base table IGS.IGS_PS_WL_OVER_RESN as exposed under the APPS synonym is the primary interface used by concurrent programs, forms, and reports running with APPS credentials.

No dependencies from this table to other database objects are documented; it is a leaf-level reference table. Its significance lies entirely in providing governed, auditable override justification codes for the workload override process within Oracle Student Systems.