Search Results igs_da_req_wifmnrs_u2




Overview

The IGS.IGS_DA_REQ_WIFMNRS table is a Degree Audit (DA) request staging object in the Oracle E-Business Suite Student Systems (IGS) schema. It stores the "What-If Minors" selections captured when a student requests a degree audit simulation against a set of minor program selections. Per the ETRM metadata, the object is documented as Obsolete and its purpose is limited: What-If minor selection data is only permitted for Single Request Types, not Batch Request Types.

From a heuristic Data Vault modeling perspective, this table behaves as a satellite attached to the degree audit request hub. Its business keys (BATCH_ID, PROGRAM_CODE, MINOR_SEQ_NUM, MAJOR_SEQ_NUM) reference request and program context, while the descriptive attributes (minor unit set, version, catalog, calendar type, and organization unit) represent the point-in-time state of the What-If minor selection. The table is classified as standalone, with no foreign keys documented in the mined structure.

Key Information Stored

The primary key is PRIMARY_SEQ_NUM, a surrogate NUMBER column that uniquely identifies each row, enforced by index IGS_DA_REQ_WIFMNRS_U1. This is the column most directly associated with the user's search term and is the authoritative row-level identifier.

The second unique index, IGS_DA_REQ_WIFMNRS_U2, is the business-key candidate and comprises:

  • BATCH_ID – unique identifier for the degree audit request.
  • PROGRAM_CODE – program against which the minor is evaluated.
  • MINOR_SEQ_NUM – programmatic sequence on insertion, expected to range from 1 to 3 per program code or major sequence combination.
  • MAJOR_SEQ_NUM – up to three minor unit sets may be tied to each major sequence number; it may be null depending on institutional setup.

Descriptive attributes captured for each selection include MINOR_UNIT_SET, MINOR_VERSION, MINOR_CATALOG, MINOR_CAL_TYPE, MINOR_CI_SEQ_NUM, and ORG_UNIT_MINOR. These identify the minor unit set, its version and catalog effective date, the associated calendar type and calendar instance, and the owning organizational unit. Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) provide audit lineage.

Common Use Cases and Queries

The most frequent query pattern resolves a What-If request to its minor selections by batch:

  • Retrieve all minors for a request: SELECT PROGRAM_CODE, MINOR_SEQ_NUM, MAJOR_SEQ_NUM, MINOR_UNIT_SET, MINOR_VERSION FROM IGS_DA_REQ_WIFMNRS WHERE BATCH_ID = :batch_id;
  • Locate a specific row using the surrogate: SELECT * FROM IGS_DA_REQ_WIFMNRS WHERE PRIMARY_SEQ_NUM = :seq;
  • Audit stale or duplicate business keys: SELECT BATCH_ID, PROGRAM_CODE, MINOR_SEQ_NUM, MAJOR_SEQ_NUM, COUNT(*) FROM IGS_DA_REQ_WIFMNRS GROUP BY 1,2,3,4 HAVING COUNT(*) > 1;
  • Report minor unit-set delivery across an institution term using MINOR_CAL_TYPE and MINOR_CI_SEQ_NUM.

Because the object is marked Obsolete, reporting against it should be treated as historical; production use is generally superseded by current Degree Audit request tables.

Related Objects

Logical relationships can be inferred from shared business keys rather than declared foreign keys: