Search Results major_unit_set_title1

Overview

IGS_DA_REQ_WIF_V is a supplementary view owned by the APPS schema within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It is registered under the FND Design Data identifier IGS.IGS_DA_REQ_WIF_V and holds a VALID status in the data dictionary. The object belongs to the Oracle Student System product family, as indicated by the IGS product prefix, which governs admissions, student records, enrollment, and related higher-education functionality.

The view exposes what-if request data. In the Oracle Student System, a "what-if" (WIF) inquiry allows a student or advisor to simulate an academic scenario — for example, testing how a change in program, major, minor, or track would affect progression or graduation requirements — without committing the change to the actual student record. IGS_DA_REQ_WIF_V consolidates the header and academic-structure attributes of a what-if request into a single, denormalized row for retrieval.

The view's type is documented as a supplementary view used to simplify forms coding. Oracle explicitly warns that this view should neither be queried nor modified directly for data maintenance, and that its definition may change dramatically in subsequent minor or major releases. Consequently it is intended for read-oriented display and integration support rather than as a stable, supported data-access interface.

Underlying Base Objects

No base objects are documented for this view in the ETRM 12.2.2 metadata; the dependency listing exposes only the view definition columns. The column set nevertheless implies a join across the what-if request batch entity (BATCH_ID), the what-if identifier entity (WIF_ID), and what-if detail records holding program, catalog, and unit-set attributes. Because the base objects are not documented, the view should be treated as an internal implementation of the forms layer. Any dependency analysis or impact assessment should rely on the recorded FND Design Data entry rather than on assumed table relationships.

Key Columns

• ROW_ID (ROWID): Row identifier for the underlying row.
• BATCH_ID (NUMBER): Request identifier grouping what-if records into a submission batch.
• WIF_ID (NUMBER): What-if identifier, the primary logical key of the simulated scenario.
• PROGRAM_CODE / PROGRAM_TITLE: Code and title of the what-if program being evaluated.
• CATALOG_CAL_TYPE, CATALOG_CI_SEQ_NUM, CATALOG_CAL_DESC, CATALOG_CAL_ALT_CODE: The what-if catalog's calendar type, sequence number, description, and alternate code.
• MAJOR_UNIT_SET_CD1..3 / MAJOR_UNIT_SET_TITLE1..3: First, second, and third simulated major unit sets and their titles.
• MINOR_UNIT_SET_CD1..3 / MINOR_UNIT_SET_TITLE1..3: First, second, and third simulated minor unit sets and their titles.
• TRACK_UNIT_SET_CD1..3 / TRACK_UNIT_SET_TITLE1..3: First, second, and third simulated track unit sets and their titles.

The repeating numbered suffixes reflect a fixed positional model, limiting each category to three entries per what-if record.

Common Use Cases and Queries

Typical use is display support within Oracle Student System forms, where a single query populates the what-if entry or inquiry block. Reporting use is discouraged because the view is unsupported, but read-only extraction for diagnostic or migration analysis is common. A representative query follows:

SELECT wif_id, batch_id, program_code, program_title, catalog_cal_type, major_unit_set_cd1, major_unit_set_title1, minor_unit_set_cd1, track_unit_set_cd1 FROM apps.igs_da_req_wif_v WHERE batch_id = :p_batch_id;

Because Oracle may alter the view in any release, integration code should never depend on its column list remaining constant.