Search Results igs_da_req_wifmjrs




Overview
Explore in AI Chat

Overview

The IGS_DA_REQ_WIFMJRS table is a core data object within the Oracle E-Business Suite Student System (IGS). It serves as the transactional storage table for "What-If" majors selections made by a student during a Degree Audit request. A Degree Audit is a critical academic process that evaluates a student's completed coursework against the requirements of a specific academic program. The "What-If" functionality allows students or advisors to model how their credits would apply to different majors or programs without officially changing their academic plan. As explicitly noted in its documentation, the data in this table is only populated and valid for single, ad-hoc Degree Audit requests; it is not used for batch request processing.

Key Information Stored

The table's structure is designed to link a specific Degree Audit request to one or more hypothetical major selections. Its primary key is a composite of three columns, ensuring uniqueness for each major entry within a request context. The critical columns include:

  • BATCH_ID: Links the record to a specific Degree Audit request, forming part of the foreign key relationship to the parent request table (IGS_DA_REQ_WIFPRGS).
  • PROGRAM_CODE: Identifies the academic program (e.g., B.Sc. in Computer Science) for which the "What-If" scenario is being run. This is also part of the primary and foreign keys.
  • MAJOR_SEQ_NUM: A sequence number that orders or differentiates between multiple majors selected for the same program within a single audit request, completing the primary key.

Additional columns, implied by the table's purpose but not detailed in the provided metadata, would typically store identifiers for the specific major(s) selected and potentially the student's identifier, though the latter is more likely housed in the parent request table.

Common Use Cases and Queries

The primary use case is supporting the interactive "What-If" analysis in the Student Self-Service or Advisor portals. When a user runs a new scenario, the application inserts records into this table. Common reporting and query patterns involve joining to the parent request table to analyze historical scenario trends. A fundamental query retrieves all majors considered for a specific student's audit request:

SELECT wm.program_code, wm.major_seq_num FROM igs_da_req_wifmjrs wm JOIN igs_da_req_wifprgs wp ON wm.batch_id = wp.batch_id AND wm.program_code = wp.program_code WHERE wp.student_id = :student_id AND wp.request_date = :req_date;

Data integrity operations are also crucial, such as identifying orphaned "What-If" major records not linked to a valid parent request, which should be purged as per the single-request lifecycle rule.

Related Objects

IGS_DA_REQ_WIFMJRS has defined dependencies within the Student System schema. The most significant relationship is its foreign key dependency on the IGS_DA_REQ_WIFPRGS table, which stores the header information for the "What-If" program request itself. This enforces referential integrity, ensuring every major selection is tied to a valid audit request. The table is also protected by its primary key constraint (IGS_DA_REQ_WIFMJRS_PK). In a full application context, it is accessed by PL/SQL packages in the IGS_DA (Degree Audit) module that drive the "What-If" engine and user interface, and it may be referenced by views designed for academic reporting on student planning behavior.