Results for “schema_version”

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

Overview

IGS_SV_BATCHES is the master control table for each batch run executed by the Oracle Student System (IGS) when gathering information about Foreign Students and Exchange Visitors for SEVIS (Student and Exchange Visitor Information System) processing. SEVIS is the United States Department of Homeland Security system through which institutions must report and track F, M, and J visa holders; IGS_SV_BATCHES provides the operational header that groups all persons and events processed within a single reporting run. The table resides in the IGS schema and is owned by the IGS - Student System product, with a status of VALID in the documented ETRM repository for EBS 12.1.1 and 12.2.2.

From a modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This reflects the table's role as an attribute-bearing structure attached to the SEVIS batch process rather than a pure business hub. Each row represents one batch execution, keyed by a surrogate identifier, with descriptive attributes describing the batch status, type, and processing timestamps. Because it consolidates attributes rather than serving purely as a key or relationship record, it behaves like a satellite anchored to the batch identifier.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• BATCH_ID — the surrogate primary key (IGS_SV_BATCHES_PK) and the sole unique business-key candidate, defined by unique index IGS_SV_BATCHES_U1.
• BATCH_STATUS — the current processing state of the batch, indicating whether it is staged, in progress, completed, or in error.
• BATCH_TYPE — classifies the nature of the batch run (e.g., outbound submission versus inbound acknowledgement).
• SEVIS_USER_ID and SEVIS_SCHOOL_ID — the SEVIS-assigned identifiers for the submitting user and the school.
• SEVIS_SCHOOL_ORG_ID — foreign key to HZ_PARTIES, identifying the school organization party.
• SEVIS_USER_PERSON_ID — foreign key to HZ_PARTIES, identifying the responsible person.
• SEVIS_ERROR_CODE — captures the error returned by SEVIS when a batch fails validation or transmission.
• XML_GEN_DATE — the timestamp when the batch XML payload was generated for submission.
• INBOUND_PROCESS_DATE — the timestamp when an inbound SEVIS response was processed.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• SCHEMA_VERSION — the version of the SEVIS XML schema used for the batch.

The primary key is the purely technical BATCH_ID; the business identity of a run is derived through its timestamps, type, and school context rather than through a natural composite key.

Common Use Cases and Queries

SEVIS administrators and reporting developers query this table to monitor batch activity, diagnose transmission failures, and reconcile person-level records against the controlling run. A typical monitoring query lists recent batches and their status:

• SELECT batch_id, batch_type, batch_status, xml_gen_date FROM igs_sv_batches ORDER BY creation_date DESC;
• Filtering failed runs: WHERE batch_status = 'ERROR' OR sevis_error_code IS NOT NULL.
• Joining to person detail to trace which students were included: SELECT b.batch_id, p.* FROM igs_sv_batches b JOIN igs_sv_persons p ON p.batch_id = b.batch_id.
• Retrieving aggregate outcome metrics: SELECT s.batch_id, s.* FROM igs_sv_batches b JOIN igs_sv_btch_summary s ON s.batch_id = b.batch_id.
• Resolving the school and submitting user against HZ_PARTIES via SEVIS_SCHOOL_ORG_ID and SEVIS_USER_PERSON_ID for reporting and audit trails.

Related Objects

The FK metadata shows IGS_SV_BATCHES both references and is referenced by other SEVIS objects:

• HZ_PARTIES — referenced twice: via SEVIS_SCHOOL_ORG_ID (school organization) and SEVIS_USER_PERSON_ID (submitting person).
• IGS_SV_PERSONS — child table; its BATCH_ID column references this table, holding person-level SEVIS records within each batch.
• IGS_SV_BTCH_SUMMARY — child table; its BATCH_ID references this table, holding aggregate counts and result metrics per batch.
• IGS_SV_BATCHES_PK / IGS_SV_BATCHES_U1 — the primary key constraint and unique index enforcing BATCH_ID uniqueness.

Together these objects form the SEVIS batch framework, in which IGS_SV_BATCHES acts as the controlling header coordinating person records, summaries, and party references across each reporting cycle.