Search Results igs_sv_ev_amd_prg_blk_v

Overview

The IGS_SV_EV_AMD_PRG_BLK_V view belongs to the Oracle E-Business Suite Student System (IGS) product and supports the SEVIS (Student and Exchange Visitor Information System) integration used by institutions in the United States. SEVIS requires certifying institutions to report specific events concerning Exchange Visitors (J-1 visa holders) through an XML file transmitted to the Department of Homeland Security. This view isolates the segment of that XML payload that conveys amendment information for an existing program of study, specifically the amendment of program dates and related remarks.

The object carries a status of VALID in the APPS schema. Its role is narrowly integration-focused: rather than presenting a broad reporting surface, it extracts a single action-coded subset of program records so that concurrent program logic can render the correct XML block. Because the view name includes "AMD" (amendment) and "PRG_BLK" (program block), it is functionally paired with related SEVIS program and event views that together build the complete regulatory file.

Underlying Base Objects

Per the documented view text, the view is defined over a single base object: IGS_SV_PRGMS_INFO. No additional tables or views are joined, and no other base objects are documented in the ETRM metadata. The WHERE clause restricts output to rows in which PRGM.PRGM_ACTION_TYPE equals 'AP'. This action-type filter is the defining characteristic of the view: it is essentially a projection over IGS_SV_PRGMS_INFO with an implicit amendment predicate applied.

IGS_SV_PRGMS_INFO stores program-level information collected for SEVIS processing, keyed by batch and person. By carrying BATCH_ID through the projection, the view preserves the grouping attribute that allows the XML generation process to associate each amendment record with the correct transmission batch.

Key Columns

• BATCH_ID — Identifier for the SEVIS processing batch to which the program amendment record belongs. Used to group records during XML assembly.
• PERSON_ID — The internal identifier of the Exchange Visitor whose program record is being amended. Joins to person-level data elsewhere in the Student System.
• PROGRAM_START_DATE — Exposed from IGS_SV_PRGMS_INFO.PRGM_START_DATE; the revised start date of the program of study. This is the column most frequently located by users searching for "program_start_date."
• PROGRAM_END_DATE — Exposed from PRGM_END_DATE; the revised end date of the program. Together with the start date it defines the amended program duration reported to SEVIS.
• AMEND_PROGRAM_REMARKS — Exposed from the REMARKS column; free-text remarks accompanying the program amendment.

Common Use Cases and Queries

The principal use case is diagnostic and integration support: confirming which records will be included in the amendment program block of the SEVIS XML file, and validating the dates and remarks that will be transmitted. A representative query retrieving amendment records for a given batch follows:

• SELECT batch_id, person_id, program_start_date, program_end_date, amend_program_remarks FROM apps.igs_sv_ev_amd_prg_blk_v WHERE batch_id = :batch_id;
• Locating program start dates for a person across amendment batches: SELECT person_id, program_start_date, program_end_date FROM apps.igs_sv_ev_amd_prg_blk_v WHERE person_id = :person_id ORDER BY program_start_date;
• Auditing remarks carried on amendments: SELECT batch_id, person_id, amend_program_remarks FROM apps.igs_sv_ev_amd_prg_blk_v WHERE amend_program_remarks IS NOT NULL;

Because the view filters internally on PRGM_ACTION_TYPE = 'AP', queries against it should not re-apply that predicate; doing so is redundant. For rows with action types other than 'AP', the underlying base object IGS_SV_PRGMS_INFO must be queried directly.