Results for “igs_sv_ev_edt_ev_blk_v”

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

Overview

IGS_SV_EV_EDT_EV_BLK_V is a reporting and integration view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product. Its documented description is "Edit Exchange Visitor Block View." It exposes the biographical and processing attributes required to construct or edit an Exchange Visitor (SEVIS) block — the structured data record submitted to the Student and Exchange Visitor Information System (SEVIS) for a non-immigrant exchange visitor — within the IGS Student System.

The view consolidates person-level identification from IGS_SV_PERSONS with biographical detail from IGS_SV_BIO_INFO, filtered to records that are current (RECORD_STATUS = 'C') and eligible for transmission. Because SEVIS submissions are batched, the view restricts output to persons whose batch summary rows carry a SEND administrative action for the SV_BIO or SV_US_ADDR tag. This makes the view a direct feeder for the Exchange Visitor batch edit and submission process rather than a general-purpose person directory.

Underlying Base Objects

The view is defined over the following documented base objects: IGS_SV_PERSONS, IGS_SV_BIO_INFO, and IGS_SV_BTCH_SUMMARY. The documented DBA view definition shows a join between IGS_SV_PERSONS and an inline subquery that selects from IGS_SV_BIO_INFO joined to IGS_SV_BTCH_SUMMARY and a second reference to IGS_SV_PERSONS (aliased PRS).

• IGS_SV_PERSONS — the primary driving table, supplying BATCH_ID, PERSON_ID, PRINT_FORM, PDSO_SEVIS_ID, SEVIS_USER_ID, RECORD_NUMBER, REPRINT_RSN_CODE, and REPRINT_REMARKS.
• IGS_SV_BIO_INFO — the biographical source, supplying name components, birth data, gender, birth city, country codes, position code, and remarks.
• IGS_SV_BTCH_SUMMARY — the batch control table, supplying TAG_CODE and ADM_ACTION_CODE, which the view uses both in the inner subquery (TAG_CODE = 'SV_BIO', ADM_ACTION_CODE = 'SEND') and in an EXISTS clause (TAG_CODE IN ('SV_BIO','SV_US_ADDR')).

The ETRM 12.2.2 metadata records no additional referenced base objects beyond those named in the view text.

Key Columns

• BATCH_ID, PERSON_ID — the composite identifier linking each row to its SEVIS batch and person record.
• LAST_NAME, FIRST_NAME, MIDDLE_NAME, SUFFIX — biographical name fields sourced from IGS_SV_BIO_INFO.
• BIRTH_DATE, GENDER, BIRTH_CITY, BIRTH_CNTRY_CODE — demographic and birth information required on the SEVIS record.
• CITIZEN_CNTRY_CODE, PERM_RES_CNTRY_CODE — citizenship and permanent residence country codes (the latter derived from LEGAL_RES_CNTRY_CODE).
• US_ADDRESS_LINE1/2, US_CITY, US_STATE, US_POSTAL_CODE, US_POSTAL_ROUTING_CODE — exposed as NULL literals; US address data is expected to arrive through the separate SV_US_ADDR tagged path.
• POSITION_CODE, REMARKS, BIRTH_CNTRY_RESN_CODE — exchange visitor position, free-text remarks, and birth country reason code.
• PRINT_FORM, PDSO_SEVIS_ID, SEVIS_USER_ID, RECORD_NUMBER — SEVIS transmission and principal designated school official identifiers.
• PERSON_NUMBER, PERSON_ID_LONG — zero-padded renderings of PERSON_ID for formatted output.
• REPRINT_REASON, REPRINT_REMARKS, OTHER_REMARKS — a DECODE pair that routes reprint remarks based on REPRINT_RSN_CODE = '05'.

Common Use Cases and Queries

Typical use is validating which exchange visitor records are staged for SEVIS submission, or extracting biographical data for a batch before transmission. A representative query returns all persons pending a biographical send in a given batch:

SELECT person_id, person_number, last_name, first_name, birth_date, gender, position_code
FROM apps.igs_sv_ev_edt_ev_blk_v
WHERE batch_id = :p_batch_id;

A second scenario checks reprint routing, since the view splits REPRINT_REMARKS into REPRINT_REMARKS and OTHER_REMARKS when the reason code is '05'. Analysts also join the view back to IGS_SV_PERSONS or IGS_SV_BTCH_SUMMARY on BATCH_ID and PERSON_ID to reconcile transmitted records against batch status. Because the view already enforces RECORD_STATUS = 'C' and ADM_ACTION_CODE = 'SEND', consumers should not re-apply those predicates unless auditing the exclusion logic itself.