Results for “igs_ps_usec_wlst_prf_u1”

6 results




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

Overview

The table IGS.IGS_PS_USEC_WLST_PRF is a transactional table within the Oracle E-Business Suite (EBS) IGS (Student Systems) schema. It stores the waitlist preferences associated with a unit section — the configuration that determines how a student's position on a waitlist is prioritized and ordered when a section is at or near capacity. The object is deployed in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, placing it in the transactional data tier rather than the index or seed data tier.

Its documented role is narrow and configuration-oriented: it captures preference codes and versions that qualify the waitlist priority assigned to a unit section. With a foreign key to IGS_PS_USEC_WLST_PRI via UNIT_SEC_WAITLIST_PRIORITY_ID, the table behaves as a subordinate detail table to the waitlist priority header.

Applying a Data Vault classification heuristic to the documented relationship structure, this table is satellite-leaning. Its primary key is a surrogate key (UNIT_SEC_WAITLIST_PREF_ID) rather than a natural business key, and its single foreign key points to a parent waitlist priority record. This suggests that the table is best modeled as a satellite hanging off the waitlist priority hub, carrying descriptive attributes such as preference order, code, and version. This classification is a modeling suggestion only; no Data Vault constructs exist in the physical schema.

Key Information Stored

Of the ten documented columns, the following are the most significant for understanding and querying the table.

  • UNIT_SEC_WAITLIST_PREF_ID — NUMBER(10). The surrogate primary key, enforced by the unique index IGS_PS_USEC_WLST_PRF_U1 and the primary key constraint IGS_PS_USEC_WLST_PRF_PK. It uniquely identifies each waitlist preference row.
  • UNIT_SEC_WAITLIST_PRIORITY_ID — NUMBER(10). The foreign key to IGS_PS_USEC_WLST_PRI, linking each preference to its parent waitlist priority record.
  • PREFERENCE_CODE — VARCHAR2(30). The unit section waitlist preference code; part of the second unique business-key candidate.
  • PREFERENCE_VERSION — VARCHAR2. The version qualifier for the preference; also part of the second unique key.
  • PREFERENCE_ORDER — NUMBER. The ordinal position of the preference, controlling sequencing where multiple preferences apply.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns supporting auditing and concurrency tracking.

Two unique indexes are documented. IGS_PS_USEC_WLST_PRF_U1 enforces uniqueness on the surrogate UNIT_SEC_WAITLIST_PREF_ID. IGS_PS_USEC_WLST_PRF_U2 enforces uniqueness on the composite business-key candidate (UNIT_SEC_WAITLIST_PRIORITY_ID, PREFERENCE_CODE, PREFERENCE_VERSION). The user's search term igs_ps_usec_wlst_prf_u2 corresponds directly to this second unique index, which is the natural key that prevents duplicate preference/version combinations within a single waitlist priority.

Common Use Cases and Queries

Typical usage centers on resolving which preferences apply to a given waitlist priority and in what order. A standard retrieval pattern joins the detail rows to the parent priority record:

SELECT p.UNIT_SEC_WAITLIST_PREF_ID
     , p.UNIT_SEC_WAITLIST_PRIORITY_ID
     , p.PREFERENCE_ORDER
     , p.PREFERENCE_CODE
     , p.PREFERENCE_VERSION
FROM   IGS.IGS_PS_USEC_WLST_PRF p
WHERE  p.UNIT_SEC_WAITLIST_PRIORITY_ID = :priority_id
ORDER  BY p.PREFERENCE_ORDER;

Because the unique index U2 covers the parent key and the preference identifiers, index-only access is possible when filtering or returning those columns, which is useful for high-volume waitlist processing jobs.

Reporting scenarios include auditing duplicate or conflicting preferences per priority, listing version history for a preference code, and reconciling waitlist configuration ahead of enrollment runs. A diagnostic query for version drift would group by UNIT_SEC_WAITLIST_PRIORITY_ID and PREFERENCE_CODE and select the distinct PREFERENCE_VERSION values.

Related Objects

  • IGS.IGS_PS_USEC_WLST_PRI — parent waitlist priority table; join on UNIT_SEC_WAITLIST_PRIORITY_ID. This is the only documented foreign key relationship.
  • IGS_PS_USEC_WLST_PRF_PK — primary key constraint over UNIT_SEC_WAITLIST_PREF_ID.
  • IGS_PS_USEC_WLST_PRF_U1 — unique index on the surrogate key.
  • IGS_PS_USEC_WLST_PRF_U2 — unique index on the composite business key.
  • The APPS synonym IGS_PS_USEC_WLST_PRF, which exposes the table to application code and concurrent programs.

No other database objects are documented as referencing this table. The table itself references no object other than the waitlist priority parent, confirming its position as the detail satellite within the unit section waitlist configuration model.