Results for “wif_program_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_DA_REQ_STDNTS_V is a reporting and integration view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It is defined over the IGS_DA_REQ_STDNTS base table, which stores Degree Audit request records generated for students, and enriches each row with descriptive attributes assembled from institutional reference data. The view is available in both EBS 12.1.1 and 12.2.2 with identical documented structure.

The view's primary role is to denormalize Degree Audit request data for downstream consumption by concurrent programs, XML Publisher reports, OAF pages, and external integration interfaces. Rather than forcing a consuming process to perform multiple joins against course version, lookup, unit set, and party tables, the view presents program descriptions, lookup meanings, unit set titles, and party name and number inline. This makes it particularly suitable for batch extracts and audit reporting where readability of the output is valued over raw normalization.

The user's search term, wif_program_code, corresponds directly to a column exposed by this view. WIF stands for "What-If" and the column carries the alternate program code used when a student requests a Degree Audit against a hypothetical program of study rather than their declared program.

Underlying Base Objects

The view is defined as an inner join between the base table IGS_DA_REQ_STDNTS (aliased DARS) and HZ_PARTIES (aliased PE), joined on DARS.PERSON_ID = PE.PARTY_ID. Because this is an equi-join without an outer modifier, any Degree Audit request whose PERSON_ID has no matching HZ_PARTIES record will be excluded from the view. The PERSON_ID column therefore acts as both the student identifier and the join key into the Trading Community Architecture party model.

Beyond the two joined base objects, the view text embeds three correlated scalar subqueries and one function call that reference further objects: IGS_PS_VER provides course titles for both PROGRAM_CODE and WIF_PROGRAM_CODE; IGS_LOOKUP_VALUES supplies the meaning for SPECIAL_PROGRAM_CODE from the lookup type IGS_DA_SPCL_PRGMS; and the function IGS_GE_GEN_004.GET_UNIT_SET_TITLE resolves the major unit set code to a title. Each of these is protected by a DECODE that returns NULL when the underlying code is NULL, preventing unnecessary lookups and avoiding accidental matches.

Key Columns

• ROW_ID — the base table ROWID, useful for direct row access and debugging.
• BATCH_ID — identifies the batch run under which the Degree Audit request was submitted.
• IGS_DA_REQ_STDNTS_ID — primary key of the request record.
• PERSON_ID / PERSON_NUMBER / PERSON_NAME — the student, sourced from HZ_PARTIES via the join.
• PROGRAM_CODE / PROGRAM_CODE_DESC — the student's declared program and its title from IGS_PS_VER.
• WIF_PROGRAM_CODE / WIF_PROGRAM_CODE_DESC — the "What-If" program code and its title; populated only for what-if degree audits.
• SPECIAL_PROGRAM_CODE / SPECIAL_PROGRAM_CODE_DESC — special program indicator code and its lookup meaning from IGS_DA_SPCL_PRGMS.
• MAJOR_UNIT_SET_CD / MAJOR_UNIT_SET_CODE_DESC — major unit set code and its resolved title.
• PROGRAM_MAJOR_CODE — combined program and major designation.
• WIF_ID — identifier linking the request to the stored what-if scenario.
• REPORT_TEXT — the generated Degree Audit report content.
• ERROR_CODE — error status returned when the audit could not be generated.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The most frequent use of this view is retrieving what-if Degree Audit requests for a given student, including the resolved description of the hypothetical program.

• What-if audit listing — filter on WIF_PROGRAM_CODE IS NOT NULL to isolate hypothetical program requests.
• Batch monitoring — group by BATCH_ID and ERROR_CODE to identify failed audit generation runs.
• Program participation reporting — aggregate by PROGRAM_CODE_DESC or WIF_PROGRAM_CODE_DESC to measure demand for particular programs.

A representative query:

SELECT person_number, person_name, program_code_desc, wif_program_code_desc, error_code, creation_date FROM apps.igs_da_req_stndts_v WHERE person_number = :p_person AND wif_program_code IS NOT NULL ORDER BY creation_date DESC;

A second query showing request volume by batch:

SELECT batch_id, COUNT(*) total_requests, SUM(CASE WHEN error_code IS NOT NULL THEN 1 ELSE 0 END) error_count FROM apps.igs_da_req_stndts_v GROUP BY batch_id ORDER BY batch_id;

Because the view performs correlated lookups per row, queries returning large volumes of data should be filtered on indexed columns such as PERSON_ID or BATCH_ID to avoid full scans of the base table and repeated title resolution.