Search Results unit_waitlist




Overview
Explore in AI Chat

Overview

The view APPS.IGS_EN_OR_UNIT_WLST_PRI_V is a reporting-oriented database view belonging to the Oracle E-Business Suite Student System (also referred to as Oracle Student System or IGS) schema. It exposes information about unit waitlist priorities — the ranked ordering that governs how students are promoted from a waitlist into an academic unit (course or module) offering when capacity becomes available.

Because it is a view rather than a base table, it does not store data independently. Instead it presents a denormalized, joined projection of the underlying priority records together with their human-readable lookup meanings. The name components reflect this purpose: IGS_EN denotes the Student System Enrollment module, OR indicates the Organizational Unit (offering) context, UNIT_WLST abbreviates "unit waitlist," and PRI denotes priority, with the trailing _V marking it as a view.

Its role in reporting and integration is to provide a stable, join-ready source for queries, reports, and interfaces that need to display not only the raw priority code but also its descriptive meaning, without requiring the consuming tool to join to the lookup infrastructure itself.

Underlying Base Objects

The view text documented in the ETRM metadata is defined over two data sources through a simple equi-join:

  • IGS_EN_ORUN_WLST_PRI (aliased UWP) — the primary base table holding the actual unit waitlist priority rows, including numeric priority ordering and the priority value code.
  • IGS_LOOKUPS_VIEW (aliased LV) — the maintained lookup view that resolves lookup codes into their user-facing meanings.

The join conditions are LV.LOOKUP_TYPE = 'UNIT_WAITLIST' and LV.LOOKUP_CODE = UWP.PRIORITY_VALUE. This constrains the lookup side to the single UNIT_WAITLIST lookup type and matches each priority row's PRIORITY_VALUE to the corresponding lookup code, thereby attaching the descriptive DSP_PRIORITY_MEANING.

It is worth noting that the ETRM metadata records no additional documented base objects beyond these two, and no alternate owners are listed. The join is an inner join by implication, meaning priority rows whose PRIORITY_VALUE does not resolve to a valid UNIT_WAITLIST lookup code would not be returned by the view.

Key Columns

The view projects the following columns, each sourced as indicated in the view text:

  • ROW_ID — the ROWID of the underlying IGS_EN_ORUN_WLST_PRI row, useful for uniquely identifying records for update or diagnostic purposes.
  • ORG_UNIT_WLST_PRI_ID — the primary key of the priority record.
  • ORG_UNIT_WLST_ID — foreign key linking the priority to its parent unit waitlist definition.
  • PRIORITY_NUMBER — the numeric rank assigned within the waitlist ordering.
  • PRIORITY_VALUE — the coded priority value that maps to the UNIT_WAITLIST lookup.
  • DSP_PRIORITY_MEANING — the display-ready, human-readable meaning obtained from IGS_LOOKUPS_VIEW.
  • Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard Oracle who-columns tracking record provenance and modification history.

The pairing of PRIORITY_VALUE with DSP_PRIORITY_MEANING is the principal convenience this view offers, since it removes the need for downstream consumers to perform the lookup join themselves.

Common Use Cases and Queries

Typical scenarios include institutional reporting on waitlist ranking rules, configuration review by administrators, and data extracts feeding enrollment processing or integration interfaces. A representative query listing priorities with their meanings is:

SELECT org_unit_wlst_pri_id, org_unit_wlst_id, priority_number, dsp_priority_meaning
FROM apps.igs_en_or_unit_wlst_pri_v
ORDER BY org_unit_wlst_id, priority_number;

To inspect priorities for a specific waitlist definition, a filter on ORG_UNIT_WLST_ID is appropriate:

SELECT priority_number, priority_value, dsp_priority_meaning
FROM apps.igs_en_or_unit_wlst_pri_v
WHERE org_unit_wlst_id = :p_wlst_id
ORDER BY priority_number;

The view is also suitable as a source for joins to related waitlist and offering entities using ORG_UNIT_WLST_ID, and its ROW_ID and audit columns support traceability and change-audit reporting. As with all IGS views, queries should be executed with the APPS schema context, and performance is generally governed by the lookup and base table indexes rather than by the view definition itself.