Search Results program_end_date




Overview
Explore in AI Chat

Overview

The IGS_SV_EV_EXT_EV_BLK_V view is a reporting and integration construct owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product. Its documented purpose is to extend program information for an Exchange Visitor whose data is transmitted as XML to the Student and Exchange Visitor Information System (SEVIS). SEVIS is the United States government system used to track foreign exchange visitors and students; Oracle EBS integrates with it by assembling batch records into XML payloads that are submitted for processing.

The view is classified as VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. It does not store data; it is a filtered projection over an underlying program information table, exposing only those rows that represent an "extend program" action. In this way it isolates the subset of records relevant to extending an Exchange Visitor's program end date, converting the internal action code into a cleaner, purpose-specific result set for downstream XML generation and reporting.

Underlying Base Objects

The view is defined over a single documented base table: IGS_SV_PRGMS_INFO (aliased as PRGM in the view text). No additional referenced base objects are documented in the ETRM metadata, meaning the view is a direct, single-table projection rather than a multi-table join. The relationship is one of filtering and column mapping: every row returned by the view corresponds to one row in IGS_SV_PRGMS_INFO where the action type indicates an extension.

Restriction logic is applied through the predicate PRGM.PRGM_ACTION_TYPE = 'EE'. The literal 'EE' denotes the Exchange Visitor "extend" action. Because the view applies this filter internally, consumers do not need to know or code the internal action code, which reduces the risk of inconsistency across reports and integration programs that generate SEVIS-bound XML.

Key Columns

  • BATCH_ID — The batch identifier grouping related SEVIS records together. It is the natural driver for selecting the set of records that belong to a single transmission or processing run.
  • PERSON_ID — The unique identifier of the person (Exchange Visitor) associated with the program record. This links the record to person-level data elsewhere in the Student System.
  • PROGRAM_END_DATE — Exposed directly from the base column PRGM_END_DATE. This is the program end date being extended and is central to the view's purpose. Users frequently search for this attribute in the context of "program_end_date" to locate or report on extension activity.
  • EXTEND_REMARKS — Exposed from the base column REMARKS. It carries free-text remarks explaining or qualifying the extension request.

Common Use Cases and Queries

The view is most commonly used to build or inspect the extension records destined for SEVIS XML, and to audit program end date changes at the batch or person level. A typical query retrieves all extension rows for a given batch:

SELECT batch_id, person_id, program_end_date, extend_remarks
FROM apps.igs_sv_ev_ext_ev_blk_v
WHERE batch_id = :p_batch_id;

To examine the extension history for a specific Exchange Visitor:

SELECT batch_id, person_id, program_end_date, extend_remarks
FROM apps.igs_sv_ev_ext_ev_blk_v
WHERE person_id = :p_person_id
ORDER BY program_end_date DESC;

To identify extensions approaching or passing a threshold date:

SELECT batch_id, person_id, program_end_date
FROM apps.igs_sv_ev_ext_ev_blk_v
WHERE program_end_date >= :p_from_date
AND program_end_date < :p_to_date;

Because the view already restricts results to the 'EE' action type, no additional action filtering is required, making it a stable interface for both ad hoc reporting and programmatic XML assembly over the life of the EBS 12.1.1 and 12.2.2 releases.