Results for “igs_en_inst_wlst_opt_all_u2”

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

Overview

IGS.IGS_EN_INST_WLST_OPT_ALL is a transaction table in the Oracle E-Business Suite Student Systems (IGS) product family, specifically within the enrolment (EN) subsystem. It describes institutional-level waitlist options that are defined per calendar instance, allowing an institution to control how waitlist processing behaves for a given enrolment calendar type. The table sits at the intersection of enrolment configuration and waitlist policy, and is therefore consulted whenever the enrolment engine determines whether a student may be placed on a waitlist for a program or unit attempt within a specific calendar instance.

Rows are owned by the IGS schema, physically stored in the APPS_TS_TX_DATA tablespace, and exposed to Oracle Applications through the FND Design Data definition IGS.IGS_EN_INST_WLST_OPT_ALL. Heuristic Data Vault modelling classifies this object as a standalone structure with no documented foreign key dependencies; in dimensional or Data Vault terms it behaves like a small configuration satellite keyed by its own identifier rather than a hub or link. This classification is a modelling suggestion only, derived from the absence of FK relationships in the ETRM metadata, and should be validated against the actual referential constraints in any given environment.

Key Information Stored

The table contains eleven documented columns. The most significant are those that define policy and identity:

• INST_WAITLIST_ID (NUMBER) — Surrogate primary key, defined by constraint IGS_EN_INST_WLST_OPT_ALL_PK. It uniquely identifies each institutional waitlist option record.
• CAL_TYPE (VARCHAR2, 10) — Business-key candidate, enforced by the unique index IGS_EN_INST_WLST_OPT_ALL_U2. Holds the name of the load calendar type to which the waitlist option applies.
• WAITLIST_ALWD (VARCHAR2) — Policy flag indicating whether waitlisting is permitted for the specified calendar type. When set to No, waitlist processing is not invoked during that enrolment calendar instance.
• SMLNES_WAITLIST_ALWD (VARCHAR2) — Flag controlling whether more than one student may wait for the same program or unit attempt within the calendar instance.
• SEQUENCE_NUMBER (NUMBER) — Previously used for internal waitlist sequencing; the ETRM metadata marks it Obsolete and it should not drive new logic.
• ORG_ID (NUMBER, 15) — Operating unit identifier, enabling multi-org security on waitlist policy rows.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

Note the presence of two unique indexes (U1 on INST_WAITLIST_ID and U2 on CAL_TYPE). U2 is effectively the natural/business key, confirming that at most one institutional waitlist option row exists per load calendar type.

Common Use Cases and Queries

The most common operational requirement is to determine, for a given calendar type, whether waitlisting is enabled and whether single-student-only rules apply. A simple lookup pattern is:

• SELECT WAITLIST_ALWD, SMLNES_WAITLIST_ALWD FROM IGS.IGS_EN_INST_WLST_OPT_ALL WHERE CAL_TYPE = :cal_type AND ORG_ID = :org_id;
• Reporting on which calendar types currently disallow waitlisting, to audit enrolment policy coverage.
• Integration checks that validate configuration before enrolment load jobs execute.

Because the table is small and configuration-oriented, reports typically join it to enrolment calendar and attempt tables to present a consolidated policy view per institution and operating unit.

Related Objects

The ETRM metadata states that IGS.IGS_EN_INST_WLST_OPT_ALL does not reference any database object directly and is referenced by dependent objects (the dependency excerpt is truncated). Practically, it is consumed by the waitlist processing logic within the IGS enrolment APIs and by configuration setup forms. Logical join relationships to consider include:

• Enrolment calendar instance tables (via CAL_TYPE / calendar instance) — defines the instance for which the option applies.
• Program and unit attempt tables — the objects against which waitlisting is enabled or disabled.
• Enrolment setup/validation APIs in the IGS_EN_* family — read these options during waitlist eligibility checks.

Because no physical FK is documented, integrators should rely on CAL_TYPE and ORG_ID as the logical join keys rather than assuming enforced referential integrity.