Search Results not_reqd_reason




Overview
Explore in AI Chat

Overview

The IGS_SV_EDT_PRGM_BLK_V view is a reporting and integration object within the Oracle E-Business Suite Student System (IGS) product family. It is owned by the APPS schema and holds VALID status in both the 12.1.1 and 12.2.2 releases. Its documented purpose is to supply the data required to construct the XML block that describes a student's edits to their program of study. In practice, this means the view acts as the extract layer for program-edit transactions that must be rendered into a structured XML payload, typically consumed by the Student System's self-service or admissions processing flows and by downstream reporting that needs the same edit information in relational form.

The view is narrow by design. It exposes a single class of records — program-edit actions — and returns them in a flattened shape suitable for direct feed into an XML generation routine or a reporting query, without the caller needing to join or filter the underlying transaction table.

Underlying Base Objects

The view is defined over a single base object, IGS_SV_PRGMS_INFO, aliased as PRGMS. The definition selects the relevant program-edit columns and applies one predicate: PRGMS.PRGM_ACTION_TYPE = 'EP'. This restricts the result set to program-edit actions, which is the specific business event the XML block is designed to describe.

The base table IGS_SV_PRGMS_INFO stores program information captured for a student within a processing batch, including major, minor, length of study, English proficiency attributes, and education level. Because the view references only this table and applies a static filter, it is a straightforward projection: no aggregation, no outer joins, and no derived expressions appear in the documented view text. The ETRM metadata lists no additional referenced base objects.

Key Columns

  • BATCH_ID — Identifier for the processing batch to which the program-edit record belongs.
  • PERSON_ID — The student (person) associated with the program edit.
  • PRINT_FORM — Indicator of the form to be printed for the record.
  • PRIMARY_MAJOR, SECONDARY_MAJOR, MINOR — The student's declared major(s) and minor as captured on the edit.
  • LENGTH_OF_STUDY — The length of study recorded for the program.
  • ENGLISH_REQUIRED — Source column ENGLISH_REQD; indicates whether an English requirement applies.
  • ENGLISH_REQMT_MET — Source column ENGLISH_REQD_MET; indicates whether the English requirement has been satisfied.
  • NOT_REQD_REASON — The reason recorded when a requirement is not required. This is the column most directly associated with the search term not_reqd_reason, and it carries the explanatory text or code justifying the waiver.
  • EDUC_LVL_REMARKS — Free-text remarks relating to the education level.
  • EDUCATION_LEVEL — The education level recorded for the student's program edit.

Common Use Cases and Queries

Typical use involves extracting a batch of program-edit records for XML generation or for verification of the English-requirement waiver logic. A minimal query retrieving all columns is:

SELECT batch_id, person_id, primary_major, secondary_major, minor, length_of_study, english_required, english_reqmt_met, not_reqd_reason, education_level FROM apps.igs_sv_edt_prgm_blk_v;

To isolate records where a requirement was waived, filter on the reason column:

SELECT person_id, not_reqd_reason FROM apps.igs_sv_edt_prgm_blk_v WHERE not_reqd_reason IS NOT NULL;

To restrict output to a specific processing batch, join or filter on BATCH_ID:

SELECT person_id, primary_major, education_level FROM apps.igs_sv_edt_prgm_blk_v WHERE batch_id = :p_batch_id;

Because the view already enforces the PRGM_ACTION_TYPE = 'EP' filter, callers do not need to repeat that condition. Performance is generally governed by the access path on IGS_SV_PRGMS_INFO, so queries constrained by BATCH_ID or PERSON_ID benefit most from the corresponding indexes on the base table.