Search Results ev_create_reason




Overview
Explore in AI Chat

Overview

The IGS_SV_PERSONS table is a core transactional table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Student and Exchange Visitor Information System (SEVIS) functionality. Owned by the IGS (iGrants) schema, it serves as a staging and processing table for student records that are queued for submission to the U.S. government's SEVIS database in a batch request. Its primary role is to hold the key identifying and status information for each person (student or exchange visitor) included in a specific batch run, linking the batch processing engine to the core person data and numerous supporting detail tables.

Key Information Stored

The table stores a combination of batch context, person identifiers, SEVIS-specific data, and processing status. The primary key is a composite of BATCH_ID and PERSON_ID. Critical columns include BATCH_ID (links to the parent IGS_SV_BATCHES table), PERSON_ID (foreign key to HZ_PARTIES), and RECORD_STATUS (indicating if the record is for an update or creation in SEVIS). The table also holds SEVIS identifiers (PDSO_SEVIS_ID, SEVIS_USER_ID), reason codes (ISSUING_REASON, EV_CREATE_REASON), and key date fields for academic sessions. Notably, the column EV_FORM_NUM, which was the subject of the user's search, is present in the metadata, indicating it stores the Exchange Visitor form number associated with the person for the SEVIS transmission.

Common Use Cases and Queries

This table is central to SEVIS batch reporting, troubleshooting, and data validation processes. Common operational queries involve identifying all persons in a specific batch, checking the status of records pending submission, or joining to detail tables to build a complete submission view. For instance, to find all exchange visitor records in a batch with a specific form number, one might use:

  • SELECT p.* FROM igs.igs_sv_persons p WHERE p.batch_id = :batch_id AND p.ev_form_num = :form_number;

Another typical use case is generating a pre-submission report by joining with related info tables (e.g., IGS_SV_PRGMS_INFO) via the BATCH_ID and PERSON_ID keys to validate the completeness of data for each person in the queue.

Related Objects

The IGS_SV_PERSONS table has defined relationships as a child and parent table within the SEVIS data model. It references the following tables via foreign keys:

  • IGS_SV_BATCHES via BATCH_ID (the controlling batch header).
  • HZ_PARTIES via PERSON_ID (the core Trading Community Architecture person record).
  • HZ_PARTIES via PDSO_SEVIS_PERSON_ID (the person responsible for the student).

It is directly referenced as a parent table by numerous SEVIS detail tables, which store supplementary information for the batched person. These child tables, all joined on BATCH_ID and PERSON_ID, include: