Search Results sevis_user_person_id

Overview

The IGS_SV_BATCHES table is a core data object within the Oracle E-Business Suite (EBS) Student Information System, specifically for the SEVIS (Student and Exchange Visitor Information System) integration. It functions as the master table for tracking each batch run of the SEVIS data gathering process. Its primary role is to log and manage the lifecycle of batches that compile information on foreign students and exchange visitors for submission to the U.S. government's SEVIS database. This includes storing batch identifiers, status, type, associated school and user details, and timestamps for generation and processing, serving as the central control point for SEVIS reporting activities in EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores metadata and control information for SEVIS batch processing. Key columns include the unique BATCH_ID (the primary key), BATCH_TYPE (distinguishing between foreign student and exchange visitor requests), and BATCH_STATUS (tracking the batch's progress). Critical identifiers for SEVIS integration are SEVIS_SCHOOL_ID (the SEVIS-assigned school identifier) and SEVIS_USER_ID (the Designated School Official or DSO identifier). The table also holds the corresponding internal EBS party IDs via SEVIS_SCHOOL_ORG_ID and SEVIS_USER_PERSON_ID, linking to the Trading Community Architecture (TCA) registry. Other significant columns track the XML_GEN_DATE, INBOUND_PROCESS_DATE, any returned SEVIS_ERROR_CODE, and standard EBS "Who" columns for auditing.

Common Use Cases and Queries

Common use cases involve monitoring batch status, troubleshooting errors, and generating audit reports for SEVIS compliance. Administrators frequently query this table to check on active or failed batches, identify batches for a specific school or DSO, or analyze processing timelines. Sample SQL patterns include retrieving all batches in an error state for a specific school, or listing recent batches with their key attributes.

• To find failed batches for a specific SEVIS School ID:

  SELECT batch_id, batch_status, sevis_error_code, creation_date, xml_gen_date
  FROM igs.igs_sv_batches
  WHERE sevis_school_id = 'SCH123456'
  AND batch_status = 'ERROR';

• To list all batches processed within a date range with their type and associated DSO:

  SELECT b.batch_id, b.batch_type, b.sevis_user_id, b.creation_date, b.inbound_process_date
  FROM igs.igs_sv_batches b
  WHERE b.creation_date BETWEEN :p_start_date AND :p_end_date
  ORDER BY b.creation_date DESC;

Related Objects

The IGS_SV_BATCHES table is central to the SEVIS data model, with defined relationships to both the TCA foundation and subordinate SEVIS tables. Its primary key is referenced by child tables that store the detailed batch contents. Documented relationships are:

• Primary Key: IGS_SV_BATCHES_PK (BATCH_ID)
• Foreign Keys (Outgoing References):
  • SEVIS_SCHOOL_ORG_ID references HZ_PARTIES.PARTY_ID (TCA party record for the school).
  • SEVIS_USER_PERSON_ID references HZ_PARTIES.PARTY_ID (TCA party record for the DSO).
• Foreign Keys (Incoming References):
  • IGS_SV_BTCH_SUMMARY.BATCH_ID references IGS_SV_BATCHES.BATCH_ID.
  • IGS_SV_PERSONS.BATCH_ID references IGS_SV_BATCHES.BATCH_ID.

These relationships indicate that IGS_SV_BATCHES provides the controlling batch header, while IGS_SV_BTCH_SUMMARY and IGS_SV_PERSONS store the aggregated and individual person-level data, respectively, for each batch.