Results for “unit_sec_waitlist_priority_id”

46 results




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

Overview

The IGSFV_USEC_WAITLIST_PRIORITIES view is a full, read-only reporting object in the Oracle E-Business Suite Student System (IGS) product family, owned by the APPS schema. It presents waitlist priority definitions associated with a unit section, exposing the ordering rules that determine the sequence in which students are promoted from a waitlist into an enrolled place. In institution-specific implementations of Oracle Student System, waitlist processing is a core enrollment control: when a unit section reaches capacity, prospective students are queued, and the priority records described here govern the relative ranking applied within that queue.

As a view of type VIEW with status VALID, the object carries no physical storage of its own; it is a curated projection of an underlying transactional table. Its naming convention follows Oracle Student System standards, where IGSFV denotes a full (form-based) view within the IGS family. The description documented in ETRM is explicit: "This is the full view, which describes the Waitlist Priorities for a Unit Section."

The view plays a supporting role in reporting and integration. Because it is defined WITH READ ONLY, it is suitable for ad hoc inquiry, concurrent program data extraction, and interfaces requiring stable, non-mutating access to priority configuration. It should not be used for DML; waitlist priority maintenance is performed against the base table through the associated Student System forms or public APIs.

Underlying Base Objects

Per the documented view text, the view is defined exclusively over the base table IGS_PS_USEC_WLST_PRI, aliased as PRI. In Oracle EBS 12.1.1 and 12.2.2 the object is delivered as part of the IGS (Student System) schema deployment, with the APPS synonym or APPS-owned definition granting read access to authorized responsibilities. No other base objects are documented as referenced.

The mapping between the view and its base table is nearly one-to-one. The view renames and, in one case, decoratively transforms columns rather than joining or aggregating additional data. Specifically:

Key Columns

  • UNIT_SEC_WAITLIST_PRIORITY_ID — Primary key surrogate for the waitlist priority record; uniquely identifies each priority definition for a unit section.
  • USEC_WAITLIST_PRIORITY_NUMBER — Numeric rank assigned to the priority, derived from the base column PRIORITY_NUMBER. Lower or higher values (per institutional convention) determine ordering within the waitlist.
  • "_LA:USEC_WLST_PRIORITY_VALUE" — Descriptive lookup descriptor exposing the priority value's MEANING, resolved against the UNIT_WAITLIST lookup type in IGS_LOOKUP_VALUES. This is the human-readable priority category.
  • UNIT_SECTION_ID — The unit section (base UOO_ID) to which the priority definition belongs, joining to the unit offering option / section structure.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS who-columns supporting audit and change tracking.

Common Use Cases and Queries

Typical scenarios include validating that each unit section has an appropriate set of waitlist priorities configured, producing listings of priority categories for enrollment policy review, and extracting configuration for data migration or reconciliation between environments.

SELECT unit_section_id,
       usec_waitlist_priority_number,
       "_LA:USEC_WLST_PRIORITY_VALUE" priority_meaning
FROM   apps.igsfv_usec_waitlist_priorities
WHERE  unit_section_id = :p_unit_section_id
ORDER  BY usec_waitlist_priority_number;

To enumerate priority configurations across all sections, including audit context:

SELECT unit_sec_waitlist_priority_id,
       unit_section_id,
       usec_waitlist_priority_number,
       "_LA:USEC_WLST_PRIORITY_VALUE" priority_meaning,
       creation_date,
       last_update_date
FROM   apps.igsfv_usec_waitlist_priorities
ORDER  BY unit_section_id, usec_waitlist_priority_number;

Because the object is read-only and contains no joins, queries execute against a single base table and perform predictably for reporting and interface purposes in both 12.1.1 and 12.2.2. Note the quoted column name for the lookup descriptor when referencing it in SQL.