Search Results major_unit_set_cd1

Overview

The IGS_DA_REQ_WIF table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, residing in the IGS (iGrants) schema. It serves as the primary repository for storing detailed academic program and unit set configurations associated with a "what-if" analysis request. In the context of student systems, a what-if request allows for the modeling and evaluation of a student's academic progress against hypothetical changes to their program of study, majors, minors, or tracks. This table is designated as a public view, indicating its intended accessibility for custom reporting and data integration purposes outside the standard application forms.

Key Information Stored

The table's columns are logically grouped to capture the essential components of a what-if scenario. The primary key is a composite of BATCH_ID and WIF_ID, where BATCH_ID relates to the overarching request and WIF_ID provides a unique identifier for each specific what-if record within that batch. The core academic data includes the PROGRAM_CODE, CATALOG_CAL_TYPE, and CATALOG_CI_SEQUENCE_NUM, which define the proposed academic program and its governing catalog. The table accommodates up to three proposed specializations each for majors, minors, and tracks through columns such as MAJOR_UNIT_SET_CD1-3, MINOR_UNIT_SET_CD1-3, and TRACK_UNIT_SET_CD1-3. Standard Oracle WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present for auditability.

Common Use Cases and Queries

The primary use case is extracting data for audit reports or feeding downstream systems with the results of what-if analyses. A common query pattern involves joining this table to the main request batch table (likely keyed by BATCH_ID) to get a complete request picture. For example, to retrieve all what-if scenarios for a specific program code created after a certain date:

• SELECT wif.BATCH_ID, wif.WIF_ID, wif.PROGRAM_CODE, wif.CATALOG_CAL_TYPE, wif.MAJOR_UNIT_SET_CD1, wif.CREATION_DATE FROM IGS.IGS_DA_REQ_WIF wif WHERE wif.PROGRAM_CODE = 'BSC-CS' AND wif.CREATION_DATE > TO_DATE('01-JAN-2023', 'DD-MON-YYYY') ORDER BY wif.BATCH_ID, wif.WIF_ID;

Another typical scenario is generating a list of all distinct majors or minors proposed across what-if requests for trend analysis, utilizing the unit set code columns.

Related Objects

The table's dependencies and indexes indicate its relationships within the application. The unique primary key index, IGS_DA_REQ_WIF_PK, enforces data integrity on the BATCH_ID and WIF_ID combination. The non-unique indexes IGS_DA_REQ_WIF_N1 (on PROGRAM_CODE) and IGS_DA_REQ_WIF_N2 (on CATALOG_CAL_TYPE, CATALOG_CI_SEQ_NUM) are designed to optimize queries filtering on these academic attributes. The table is fundamentally linked to a parent table storing the BATCH_ID, which is not explicitly named in the provided metadata but is central to the request structure. As a public view, it is a key source for custom integrations with reporting tools or data warehouses.