Search Results igs_ps_wl_over_resn




Overview
Explore in AI Chat

Overview

IGS_PS_WL_OVER_RESN is a reference (lookup) table within the Oracle E-Business Suite Student System (IGS) product family. It stores the set of valid override reasons that may be selected when an expected workload value is overridden for a student or faculty workload record. In the 12.1.1 and 12.2.2 releases the table is owned by the IGS schema and reports a VALID status in the data dictionary.

The object functions as a controlled vocabulary: rather than permitting free-text justification, workload maintenance forms and concurrent processes validate the override reason against the values held here. The table therefore sits behind the workload override transaction rather than participating in it directly, acting as a parent in a conventional master–detail relationship.

Relationship metadata classifies the object as hub-leaning under a heuristic Data Vault model. In practical terms this is a modelling suggestion only: the table behaves as a stable code list keyed by a single business attribute, with descriptive attributes attached. It is not a transactional or history-accumulating satellite, although it does carry standard audit columns.

Key Information Stored

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

  • OVERRIDE_REASON — the business key. It is the column of the IGS_PS_WL_OVER_RESN_PK primary key constraint and is additionally protected by the unique index IGS_PS_WL_OVER_RESN_U1. Every child workload override record points to a valid value in this column.
  • DESCRIPTION — the human-readable text presented to users in the list of values and printed on workload reports.
  • CLOSED_IND — enables effective retirement of a reason. When set to the closed state, the value remains available for historic records but is excluded from new selection, preserving referential integrity without deleting data.
  • CREATED_BY, CREATION_DATE — standard WHO audit columns recording the user and timestamp of insertion.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns recording the most recent modification and its author.
  • LAST_UPDATE_LOGIN — the login identifier associated with the last update, used for session-level auditing.

The metadata documents no surrogate sequence-generated identifier; the primary key is the business attribute itself.

Common Use Cases and Queries

Typical usage includes populating the override reason list of values on the faculty workload override form, validating inbound interface data, and reporting on the distribution of override justifications. A simple lookup of active reasons is:

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

Analysing override activity by reason requires joining to the transactional table:

  • SELECT r.override_reason, r.description, COUNT(*) FROM igs.igs_ps_fac_ovr_wl w, igs.igs_ps_wl_over_resn r WHERE w.override_reason = r.override_reason GROUP BY r.override_reason, r.description;

Because the primary key column also carries a unique index, single-row retrievals by OVERRIDE_REASON are highly selective and suitable for validation routines in PL/SQL APIs and data conversions.

Related Objects

The documented foreign key relationship identifies IGS_PS_FAC_OVR_WL as the principal dependent object. That table stores the faculty workload override records themselves, and its OVERRIDE_REASON column references IGS_PS_WL_OVER_RESN.OVERRIDE_REASON, making this reference table a parent in a one-to-many relationship. No other foreign keys referencing this table are documented in the ETRM metadata for 12.1.1. Workload and faculty reporting views within the IGS module that display override justifications will also depend on this table through that join path.