Results for “bio_info”

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 in the Oracle E-Business Suite Student System (the IGS schema, delivered under the APPS synonym). It supports the SEVIS (Student and Exchange Visitor Information System) event-processing and batch-edit workflow, specifically the editing of event blocks derived from biographical and U.S. address data collected for international students and exchange visitors. The view consolidates person-level records from the SEVIS staging area with denormalized biographical detail so that downstream processes — batch review, edit validation, and SEVIS file generation — can consume a single flattened row per person per batch.

Functionally, the view answers the ETRM search term "bio_info" by joining the SEVIS persons staging table to an inline biographical subquery built on the SEVIS bio_info staging table. Only records in a completed state (record_status = 'C') whose associated batch summary carries a tag code of SV_BIO or SV_US_ADDR and an administrative action code of SEND are surfaced, ensuring that the view exposes only those persons eligible for transmission to SEVIS.

Underlying Base Objects

The view is not documented with a formal base-object list in the ETRM metadata, but its view text identifies the following IGS tables directly:

• IGS_SV_PERSONS — aliased pers, the primary SEVIS person staging table providing batch, person, form, SEVIS user, record number, and reprint attributes.
• IGS_SV_BIO_INFO — aliased bio, the biographical detail staging table supplying names, birth data, gender, citizenship, and residence country information.
• IGS_SV_BTCH_SUMMARY — aliased bioSumm/summ, the batch summary table used to filter by tag code and administrative action.

The join is an outer join (pers.person_id = bio_info.person_id (+) and pers.batch_id = bio_info.batch_id (+)), so persons with no matching biographical record still return, with bio columns null.

Key Columns

• batch_id, person_id — the composite key identifying the person within a specific SEVIS batch.
• last_name, first_name, middle_name, suffix — name attributes sourced from bio_info.
• birth_date, gender, birth_city, birth_cntry_code — demographic and birth-location data.
• citizen_cntry_code, perm_res_cntry_code, BIRTH_CNTRY_RESN_CODE — citizenship, legal permanent-residence country, and birth-country reason code.
• us_address_line1/2, us_city, us_state, us_postal_code, us_postal_routing_code — exposed as NULL placeholders in this view, signifying that U.S. address detail is carried elsewhere.
• print_form, pdso_sevis_id, sevis_user_id, record_number — SEVIS transmittal and identification attributes.
• person_number, person_id_long — zero-padded character renderings of the person identifier.
• REPRINT_REASON, reprint_remarks, other_remarks — reprint-handling columns where remarks are split between standard and "other" remarks based on reprint reason code '05'.

Common Use Cases and Queries

Typical usage is to list persons ready for SEVIS biographical transmission, or to review the bio and reprint detail for a given batch. For example:

• Reporting all eligible persons in a batch: SELECT person_id, last_name, first_name, birth_date FROM apps.igs_sv_ev_edt_ev_blk_v WHERE batch_id = :batch_id;
• Identifying records with reprint remarks: SELECT person_number, REPRINT_REASON, reprint_remarks FROM apps.igs_sv_ev_edt_ev_blk_v WHERE reprint_remarks IS NOT NULL;
• Auditing citizenship data for validation: SELECT person_id, citizen_cntry_code, perm_res_cntry_code FROM apps.igs_sv_ev_edt_ev_blk_v WHERE batch_id = :batch_id;

Because the view filters on completed records with SEND administrative actions, it is suited to pre-generation validation and reconciliation reporting rather than to transactional maintenance.