Results for “igs_en_orun_wlst_prf”

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

Overview

The IGS_EN_ORUN_WLST_PRF table is a core configuration object within the Oracle E-Business Suite IGS — Student System product family. It stores the waitlist preferences that are applied to each organization unit (academic unit) for a given waitlist priority. In practical terms, when a student is placed on a waitlist for an organization unit, the system consults this table to determine how the waitlist should behave for that unit at each priority level — for example, how many seats are reserved, and in what order candidates are considered.

The table resides in the IGS schema and is documented as VALID in the ETRM repository for both EBS 12.1.1 and 12.2.2. It is a relatively narrow table, consisting of ten documented columns, and its physical shape is consistent across the supported releases.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as satellite-leaning. This is a modeling suggestion rather than a physical property: the table hangs off the parent waitlist priority entity via a foreign key, carries descriptive preference attributes, and has a stable surrogate key, which is characteristic of a satellite structure attached to a parent hub/link combination.

Key Information Stored

The table is anchored by a surrogate primary key and a single foreign key, with the remaining attributes carrying the actual preference configuration.

• ORG_UNIT_WLST_PRF_ID — the surrogate primary key, defined by the constraint IGS_EN_ORUN_WLST_PRF_PK. It is also the column carried by the unique index IGS_EN_ORUN_WLST_PRF_U1, which effectively acts as the business-key candidate for the row.
• ORG_UNIT_WLST_PRI_ID — the foreign key referencing IGS_EN_ORUN_WLST_PRI. This ties each preference record to a specific waitlist priority within an organization unit.
• PREFERENCE_ORDER — controls the sequencing of preferences, i.e. the ranking applied when the waitlist is evaluated.
• PREFERENCE_CODE — the coded value identifying the type of preference being configured.
• PREFERENCE_VERSION — supports versioning of the preference definition, allowing changes to be tracked over time.
• CREATED_BY, CREATION_DATE — standard EBS who-columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns capturing the last modification user, timestamp, and login.

Together these columns describe how a waitlist preference is ordered, coded, and versioned for the parent priority record.

Common Use Cases and Queries

The primary use case is retrieving the configured waitlist preferences for an organization unit and priority, typically during admissions or enrollment processing. A representative query joining to the parent priority table is:

• SELECT p.ORG_UNIT_WLST_PRF_ID, p.PREFERENCE_ORDER, p.PREFERENCE_CODE, p.PREFERENCE_VERSION FROM IGS.IGS_EN_ORUN_WLST_PRF p WHERE p.ORG_UNIT_WLST_PRI_ID = :priority_id ORDER BY p.PREFERENCE_ORDER;
• Reporting on preference ordering across priorities to validate configuration consistency.
• Auditing configuration changes using CREATION_DATE and LAST_UPDATE_DATE.
• Extracting preference definitions for migration or comparison between environments.

Because the table is small and driven by the foreign key, queries should always filter on ORG_UNIT_WLST_PRI_ID to avoid full scans.

Related Objects

The most significant related object is the parent table referenced by the sole documented foreign key.

• IGS_EN_ORUN_WLST_PRI — the parent waitlist priority table, joined via IGS_EN_ORUN_WLST_PRF.ORG_UNIT_WLST_PRI_ID = IGS_EN_ORUN_WLST_PRI.ORG_UNIT_WLST_PRI_ID. This is the primary relationship and the anchor of the satellite model.
• Any view or API layered over organization-unit waitlist processing that resolves a student's waitlist standing will transitively read this table through the parent priority record.

Given the narrow scope of the documented metadata, these are the only directly evidenced relationships; additional dependents should be confirmed against the live IGS schema.