Search Results control_num

Overview

IGS_PS_EXP_WL_V is a reporting view within the Oracle E-Business Suite Student System (IGS) product family. In ETRM documentation the object is classified as belonging to the IGS — Student System module and is explicitly flagged as obsolete. Its documented purpose is to store and expose setup data regarding excepted workload in a given calendar category. In practical terms, the view acts as a denormalized read layer over the base transaction table IGS_PS_EXP_WL, enriching each row with the human-readable meaning of the associated calendar category rather than forcing report authors and integrators to resolve the lookup code manually.

Because the object is not implemented in the reference database environment documented by ETRM, it exists as documented metadata and view text rather than as a queryable artifact in every 12.1.1 or 12.2.2 instance. Its role in EBS reporting and integration is nonetheless representative of the standard IGS pattern: a master table holding coded configuration values, joined to the shared lookup infrastructure so downstream consumers receive both the code and its display meaning.

Underlying Base Objects

ETRM lists no referenced base objects in its structured metadata, but the view text itself is definitive. The definition selects from two sources:

• IGS_PS_EXP_WL EW — the primary base table holding excepted workload setup rows, including the control number, calendar category code, and expected workload value, along with standard EBS WHO columns.
• IGS_LOOKUPS_VIEW LKUP — the lookup view used to translate the coded calendar category into a displayed meaning.

The join is an inner join on LKUP.LOOKUP_CODE = EW.CALENDAR_CAT, restricted by LKUP.LOOKUP_TYPE = 'CAL_CAT'. This means rows whose calendar category code has no active lookup entry of type CAL_CAT will not surface through the view, a behavior worth noting when reconciling record counts between the view and the underlying table.

The view additionally projects EW.ROWID as ROW_ID, a convention that lets consumers identify the physical row in the base table for troubleshooting or for constructing update paths. The absence of an owner and of documented base objects in ETRM reflects the obsoleted status of the IGS product line rather than any structural ambiguity.

Key Columns

• ROW_ID — the ROWID of the corresponding IGS_PS_EXP_WL row, useful as a unique physical identifier.
• CONTROL_NUM — the control number that ties the excepted workload setup to its governing control record.
• CALENDAR_CAT — the coded calendar category value stored on the base table and used as the join key to the lookup view.
• CALENDAR_CAT_MEANING — the descriptive meaning of the calendar category, resolved from IGS_LOOKUPS_VIEW where the lookup type is CAL_CAT.
• EXPECTED_WL — the excepted (expected) workload quantity defined for the calendar category.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit (WHO) columns inherited from the base table, supporting traceability and change analysis.

Common Use Cases and Queries

Typical usage centers on reporting excepted workload configuration by calendar category, validating that every configured category resolves to a valid CAL_CAT lookup, and joining workload setup to other student-record data through CONTROL_NUM. A representative query is:

• SELECT control_num, calendar_cat, calendar_cat_meaning, expected_wl FROM igs_ps_exp_wl_v ORDER BY calendar_cat;
• SELECT control_num, expected_wl FROM igs_ps_exp_wl_v WHERE calendar_cat = :category;
• SELECT calendar_cat, calendar_cat_meaning, SUM(expected_wl) FROM igs_ps_exp_wl_v GROUP BY calendar_cat, calendar_cat_meaning;

Because the object predates and outlives active IGS support, integrations should treat it as a legacy configuration source and verify its presence in the target instance before relying on it.