Search Results igs_da_req_wif_v




Overview
Explore in AI Chat

Overview

The view IGS_DA_REQ_WIF_V belongs to the Oracle EBS IGS — Student System product family, which is documented in the ETRM as obsolete in release 12.1.1 and 12.2.2. The view presents a denormalized, reporting-friendly projection over Degree Audit What-if requests. A what-if request allows an institution to model the effect of a hypothetical change — a different catalog year, program, major, minor, or track — against a student's academic record without committing that change to the live degree audit. The view collapses the raw request row and its associated program version and catalog instance into a single rectangular result set that includes human-readable titles and descriptions, making it suitable for concurrent-program extracts, OBIEE/XML Publisher reporting, and integration feeds. It is exposed as a read-only dictionary-style object; the ETRM entry records "Not implemented in this database" and documents no owner or referenced base objects, indicating the view was delivered by the product but is not present in every installation.

Underlying Base Objects

The view text joins three base tables:

The IGS_PS_VER join is deliberately constrained: the correlated subquery selects the version whose COURSE_STATUS matches a value flagged S_COURSE_STATUS = 'ACTIVE' in IGS_PS_STAT, limited by ROWNUM < 2. This yields at most one active version per program, which is what gives the view its one-row-per-request cardinality. The view also calls IGS_GE_GEN_004.GET_UNIT_SET_TITLE six to nine times to resolve unit set codes into descriptive titles for the major, minor, and track positions.

Key Columns

Common Use Cases and Queries

The view is typically used to report or extract what-if scenarios for a program and catalog year. A filtered query by batch is the most common access path:

  • SELECT WIF_ID, PROGRAM_CODE, PROGRAM_TITLE, CATALOG_CI_SEQ_NUM, MAJOR_UNIT_SET_TITLE1 FROM IGS_DA_REQ_WIF_V WHERE BATCH_ID = :p_batch_id ORDER BY WIF_ID;
  • SELECT WIF_ID, CATALOG_CAL_TYPE, CATALOG_CI_SEQ_NUM, CATALOG_CAL_DESC FROM IGS_DA_REQ_WIF_V WHERE PROGRAM_CODE = :p_program;
  • Incremental CDC extract: SELECT ROW_ID, WIF_ID, PROGRAM_CODE, CATALOG_CI_SEQ_NUM, LAST_UPDATE_DATE FROM IGS_DA_REQ_WIF_V WHERE LAST_UPDATE_DATE >= :p_since;

Because ROW_ID is exposed, the view can also support correction workflows that locate the base row before updating IGS_DA_REQ_WIF. Note that the repeated GET_UNIT_SET_TITLE calls impose per-row PL/SQL overhead; for high-volume extracts, joining directly to the unit set tables is preferable.