Search Results igs_ps_exp_wl_pk

Overview

The IGS_PS_EXP_WL table is a core setup object within the Oracle E-Business Suite Student System (IGS) product family. It stores configuration data describing the expected workload associated with a given calendar category, providing the baseline against which student workload commitments are measured and validated. In release 12.1.1 and 12.2.2, the table resides in the IGS schema and is owned entirely by the Student System module; it is not a transactional or enrollment table but a reference table that governs how workload rules are applied across an institution's academic calendar.

From a Data Vault modeling perspective, the FK structure mined from the documented relationships suggests a hub-leaning classification. Because the table's primary key is a single business attribute (CALENDAR_CAT) and it is referenced by dependent tables rather than acting as a large transaction accumulator, it behaves conceptually like a hub of calendar-category workload definitions, with satellite-style descriptive attributes attached.

Key Information Stored

The physical schema documented in the ETRM repository contains eight columns. The most significant are:

• CALENDAR_CAT — the calendar category code. This column serves as both the surrogate primary key (IGS_PS_EXP_WL_PK) and the unique business key (IGS_PS_EXP_WL_UK), making it the definitive identifier for each expected-workload row.
• EXPECTED_WL — the expected workload value defined for the associated calendar category.
• CONTROL_NUM — a control or sequence number used for ordering or batch identification within the setup.
• CREATED_BY, CREATION_DATE — standard Oracle EBS WHO-column audit fields capturing the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the corresponding audit fields that record the most recent modification user, date, and login session.

Note that because CALENDAR_CAT is defined as both the primary key and a unique key, there is no separate meaningless surrogate identifier in the documented schema; the business key and primary key coincide.

Common Use Cases and Queries

Typical reporting and validation scenarios include confirming that every calendar category has a defined expected workload and joining that baseline to student enrollment category rules. A representative query:

• SELECT e.CALENDAR_CAT, e.EXPECTED_WL, c.CAL_CAT_CODE FROM IGS_PS_EXP_WL e, IGS_PS_EMP_CATS_WL c WHERE e.CALENDAR_CAT = c.CAL_CAT_CODE;
• Setup verification: SELECT CALENDAR_CAT, EXPECTED_WL, LAST_UPDATE_DATE FROM IGS_PS_EXP_WL ORDER BY CALENDAR_CAT;
• Audit reporting on recently changed workload definitions using CREATION_DATE and LAST_UPDATE_DATE ranges.

These patterns are useful for functional analysts validating calendar configuration and for conversion or data-migration extract scripts.

Related Objects

The documented foreign key relationship identifies the primary dependent object:

• IGS_PS_EMP_CATS_WL — references IGS_PS_EXP_WL via CAL_CAT_CODE pointing to CALENDAR_CAT. This table defines employee/student category workload rules and depends on the expected-workload baseline defined here.

Related calibration and setup tables in the IGS Student System family (such as calendar category and workload definition objects) typically join through CALENDAR_CAT, while the WHO audit columns follow standard EBS conventions. Because the documented ETRM metadata lists only this single inbound FK, IGS_PS_EXP_WL is best characterized as a parent reference table whose principal downstream dependency is IGS_PS_EMP_CATS_WL.