Search Results birth_cntry_code




Overview
Explore in AI Chat

Overview

The view IGS_SV_EV_EDT_DPD_BLK_V belongs to the IGS – Student System product family within Oracle E-Business Suite. This module is documented as obsolete in ETRM metadata for both 12.1.1 and 12.2.2, meaning it is no longer actively shipped or supported in current implementations, though the underlying metadata, view definitions, and historical references remain catalogued. The view's description — "Edit dependent block for the Exchange Visitor" — identifies its purpose: it supplies the data set required to display and maintain dependent (family member) records associated with an Exchange Visitor (J-1 visa holder) in the Student System's SEVIS-related functionality.

Functionally, the view presents a filtered, presentation-ready block of dependent information. Rather than exposing every dependent row in the base table, it restricts output to records where the dependent action type equals 'U', which in the Student System convention typically denotes an update or unchanged/no-change action within the SEVIS batch reporting cycle. This allows the editing form or concurrent process to operate only on dependents requiring attention in the current batch.

Underlying Base Objects

The view is defined over a single documented base table: IGS_SV_DEPDNT_INFO (aliased DPDT in the view text). No other referenced base objects are documented in the ETRM metadata. Every column in the view is derived either directly from columns of this dependent-information table or through SQL expressions applied to DPDT.DEPDNT_ID. The filtering predicate WHERE DPDT.DEPDNT_ACTION_TYPE = 'U' governs row inclusion, and no joins, unions, or aggregation are present. Because the base table stores Exchange Visitor dependents for SEVIS processing, the view is tightly coupled to that table's structure and inherits its obsolete status.

Key Columns

Note the alias mismatches: the column named CITIZENSHIP_CNTRY_CODE maps from CITIZEN_CNTRY_CODE, and PERM_RESIDENCY_CODE maps from LEGAL_RES_CNTRY_CODE. Consumers should reference the view-level names.

Common Use Cases and Queries

Typical usage involves retrieving dependent data for a specific person or batch during SEVIS preparation, or auditing dependents pending update. For example, to retrieve all dependents in a batch:

  • SELECT person_id, last_name, first_name, birth_cntry_code, relationship FROM igs_sv_ev_edt_dpd_blk_v WHERE batch_id = :p_batch_id;
  • SELECT depdnt_id, person_number, person_id_long, depdnt_sevis_id FROM igs_sv_ev_edt_dpd_blk_v WHERE person_id = :p_person_id;
  • SELECT birth_cntry_code, citizenship_cntry_code, perm_residency_code FROM igs_sv_ev_edt_dpd_blk_v WHERE relationship = 'SPOUSE';

Because the base module is obsolete, these queries are appropriate only for legacy reporting, migration extraction, or historical data reconciliation. Implementations on 12.1.1 or 12.2.2 should verify that IGS_SV_DEPDNT_INFO and this view exist in their schema before relying on them, as ETRM notes no implementation in the current database for the documented environment.