Search Results terminate_reason




Overview
Explore in AI Chat

Overview

IGS_SV_EV_TRM_DPDNT_BLK_V — documented in the ETRM metadata as IGS_SV_EV_TRM_DPD_BLK_V — is a reporting view within the Oracle E-Business Suite IGS – Student System (Obsolete) product family. Its documented purpose is to present the Terminate dependent block for the Exchange Visitor. In the SEVIS-related exchange visitor (J-1) processing model, dependent records (spouses and children of the exchange visitor) carry their own SEVIS identifiers and must be maintained in step with the principal visitor's record. This view surfaces the subset of dependent records for which a termination action has been requested, packaging them into batch-oriented output suitable for downstream SEVIS reporting or interface processing.

The view is a filtered projection rather than a transactional entry point. It does not create, update, or delete data; it exposes rows from the dependent information store where the dependent action type equals 'T' (terminate). Because the object is documented as obsolete and is marked "Not implemented in this database," it should be treated as a legacy artifact. In 12.1.1 and 12.2.2 environments where it does exist, it functions primarily as a read-only reporting and integration surface used by batch programs that assemble SEVIS termination payloads for exchange visitor dependents.

Underlying Base Objects

The view text identifies a single documented base object: IGS_SV_DEPDNT_INFO, aliased as DPDT. All columns projected by the view are drawn from this table; the ETRM metadata lists no additional referenced base objects. The defining predicate is:

  • DPDT.DEPDNT_ACTION_TYPE = 'T' — restricting output to dependent records flagged for termination.

The relationship is therefore one of strict filtering and column aliasing: every row returned corresponds one-to-one with a qualifying row in IGS_SV_DEPDNT_INFO. Several columns are renamed during projection (for example, TERMINATION_REASON becomes TERMINATE_REASON, OTHER_REASON_REMARKS becomes OTHER_REASON, TERMINATION_EFFECT_DATE becomes EFFECTIVE_DATE, and REMARKS becomes COMMENTS), which standardizes the output shape for the consuming batch or interface program. Because no joins, unions, or aggregations appear in the documented view text, performance is governed almost entirely by the access path and indexing on IGS_SV_DEPDNT_INFO, particularly on the action type and batch columns.

Key Columns

  • BATCH_ID — Identifier grouping dependent termination records into a processing batch.
  • PERSON_ID — Party identifier of the individual associated with the dependent record.
  • DEPDNT_ID — Primary identifier of the dependent record in IGS_SV_DEPDNT_INFO.
  • TERMINATE_REASON — Source termination reason code (aliased from TERMINATION_REASON).
  • OTHER_REASON — Free-text remarks when the termination reason is "other" (aliased from OTHER_REASON_REMARKS).
  • EFFECTIVE_DATE — Effective date of the termination (aliased from TERMINATION_EFFECT_DATE).
  • COMMENTS — General remarks (aliased from REMARKS).
  • DEPDNT_SEVIS_ID — The dependent's SEVIS identifier. This is the column most closely associated with the user's search term "depdnt_sevis_id," and it is the key that ties the view's output back to the external SEVIS record for the dependent.

Common Use Cases and Queries

Typical usage centers on extracting pending dependent terminations for a batch run, for reconciliation between EBS and SEVIS, or for auditing. A representative query retrieves all termination rows for a given batch:

  • SELECT batch_id, person_id, depdnt_id, terminate_reason, effective_date, depdnt_sevis_id FROM igs_sv_ev_trm_dpd_blk_v WHERE batch_id = :batch_id;

To locate a specific dependent by SEVIS identifier — the scenario implied by the search term — query on the projected column directly:

  • SELECT person_id, depdnt_id, terminate_reason, effective_date FROM igs_sv_ev_trm_dpd_blk_v WHERE depdnt_sevis_id = :sevis_id;

Validation and audit queries frequently filter on effective date ranges or check for rows lacking a termination reason. Because the view is documented as obsolete and not implemented in all databases, implementations should verify its existence in the data dictionary before relying on it and should confirm that column names in custom code match the aliases shown above rather than the underlying base table names.