Results for “termination_reason”

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

Overview

The IGS_SV_EV_TERM_EV_BLK_V view belongs to the IGS (Student System) product family, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. Its purpose is narrowly scoped: it presents Exchange Visitor termination data that is formatted for inclusion in the XML file transmitted to SEVIS (the Student and Exchange Visitor Information System operated by the U.S. Department of Homeland Security). In practice, the view acts as a reporting layer that reshapes raw termination records into the exact field layout SEVIS expects, so downstream batch processes or concurrent programs can select the rows and marshal them into the outbound XML payload.

The view is not a general-purpose reporting object. It is a staging/formatting construct tied to the SEVIS batch submission workflow. Because it targets a specific interface file, its column set is deliberately minimal and closely mirrors the SEVIS schema rather than the broader Oracle student model.

Underlying Base Objects

Per the ETRM metadata, no referenced base objects are separately documented, but the embedded view text identifies a single source table: IGS_SV_PRGMS_INFO (aliased as PRGM). Every column in the view derives from that one table. The view is filtered with the predicate PRGM.PRGM_ACTION_TYPE = 'TR', meaning only rows representing a termination action are surfaced. The ETRM listing also notes "Not implemented in this database," indicating the view may be absent or invalid in a given environment, though its definition remains part of the documentation set.

Key Columns

• BATCH_ID — Identifier linking the termination record to a specific SEVIS batch submission.
• PERSON_ID — The individual (Exchange Visitor) whose record is being terminated.
• TERMINATION_REASON — The coded reason driving the termination event. This is the column directly relevant to the search term "termination_reason."
• TERMINATION_DATE — Aliased from PRGM.EFFECTIVE_DATE; the effective date of termination.
• TERMINATION_REMARKS — Populated from PRGM.REMARKS only when TERMINATION_REASON is not 'OTHER'.
• OTHER_REMARKS — Populated from PRGM.REMARKS only when TERMINATION_REASON equals 'OTHER'.

The two DECODE expressions implement a mutually exclusive routing of the free-text REMARKS value: non-OTHER reasons place remarks in TERMINATION_REMARKS, while OTHER reasons place them in OTHER_REMARKS. This split exists to satisfy the SEVIS file structure, which treats "other" explanations differently from standard coded reasons.

Common Use Cases and Queries

Typical usage centers on extracting termination records for a batch and verifying the reason/remarks mapping before transmission. A representative query follows:

• SELECT batch_id, person_id, termination_reason, termination_date, termination_remarks, other_remarks FROM igs_sv_ev_term_ev_blk_v WHERE batch_id = :p_batch_id; — retrieves all terminations for a given SEVIS batch.
• SELECT person_id, termination_reason, termination_date FROM igs_sv_ev_term_ev_blk_v WHERE termination_reason = 'OTHER'; — isolates records where the reason is "other," useful for reviewing free-text explanations held in OTHER_REMARKS.
• SELECT termination_reason, COUNT(*) FROM igs_sv_ev_term_ev_blk_v GROUP BY termination_reason; — summarizes the distribution of termination reasons across records.

Because the view is obsolete and environment-dependent, confirm its existence and validity in the target instance before relying on it for production reporting. Where available, it remains a concise, purpose-built source for Exchange Visitor termination data destined for SEVIS.