Results for “igs_sv_persons”

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

Overview

IGS_SV_PERSONS is a Student System table in Oracle EBS that stores information about students submitted in a batch request for a SEVIS (Student and Exchange Visitor Information System) processing run. The table functions as the batch roster for the SEVIS batch submission process; each row represents a single student included in a given batch. The IGS product line is documented as obsolete in the current release, meaning the table is retained for historical and upgrade purposes but is not actively implemented in a fresh 12.1.1 or 12.2.2 database. The ETRM documentation explicitly notes that the object is "Not implemented in this database."

From a data modeling perspective, the FK structure suggests this table behaves as a hub-leaning entity. Its role as the parent of numerous dependent information tables and its two-part primary key (BATCH_ID plus PERSON_ID) give it the cardinality and referential weight of a hub within a Data Vault model, where the composite key acts as the business key that other satellites and links attach to.

Key Information Stored

The table is documented with 32 columns. The most significant are outlined below, distinguishing the primary key from the business-key candidates.

• BATCH_ID — Part of the composite primary key (IGS_SV_PERSONS_PK). Identifies the SEVIS batch run. Also part of the unique business-key candidate IGS_SV_PERSONS_U1.
• PERSON_ID — Part of the composite primary key and the unique index. References HZ_PARTIES, linking the row to the individual's party record.
• PDSO_SEVIS_PERSON_ID — Foreign key referencing HZ_PARTIES. Likely the Principal Designated School Official associated with the student's record.
• RECORD_NUMBER — Sequenced record identifier within the batch submission.
• RECORD_STATUS and STATUS_CODE — Track the processing status or disposition of the student record within the batch.
• PERSON_NUMBER — Business-visible person identifier, distinct from the numeric PERSON_ID surrogate.
• SEVIS_USER_ID and PDSO_SEVIS_ID — SEVIS-side identifiers for the student and the official.
• FORM_ID and PRINT_FORM — Identify the SEVIS form type and its print preference.
• ISSUING_REASON, OTHER_REASON, and EV_CREATE_REASON — Business reasons for issuing or creating the record.
• CURR_SESSION_END_DATE, NEXT_SESSION_START_DATE, INIT_PRGM_START_DATE — Session and program date tracking.
• SEVIS_ERROR_CODE and SEVIS_ERROR_ELEMENT — Capture errors returned by SEVIS during submission.
• NO_SHOW_FLAG, LAST_SESSION_FLAG, ADJUDICATED_FLAG — Status flags governing the student's batch outcome.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns.

Common Use Cases and Queries

The primary use case is reviewing and troubleshooting batch SEVIS submissions. Administrators and interfaces query this table to identify which students were included in a batch and to determine submission outcomes.

Typical query patterns include joining to IGS_SV_BATCHES to retrieve batch metadata for a given person, or filtering on SEVIS_ERROR_CODE to identify failed records. A representative query might select BATCH_ID and PERSON_ID from IGS_SV_PERSONS where RECORD_STATUS indicates an error, then join to the dependent tables (IGS_SV_BIO_INFO, IGS_SV_FINANCE_INFO, and so on) on both BATCH_ID and PERSON_ID to reconstruct the full submission payload for a student. Reporting use cases center on batch reconciliation — confirming which students received a successful SEVIS acknowledgment — and on error trend analysis by SEVIS_ERROR_CODE or ISSUING_REASON.

Related Objects

The table is centrally positioned, with one parent batch table and multiple dependent child tables keyed on (BATCH_ID, PERSON_ID).

• IGS_SV_BATCHES — Parent table; IGS_SV_PERSONS.BATCH_ID references it.
• HZ_PARTIES — Referenced twice: via PERSON_ID and via PDSO_SEVIS_PERSON_ID.
• IGS_SV_BIO_INFO — Child table joined on BATCH_ID and PERSON_ID; holds biographical data.
• IGS_SV_CONVICTIONS — Child table joined on BATCH_ID and PERSON_ID.
• IGS_SV_DEPDNT_INFO — Child table for dependent information.
• IGS_SV_EMPL_INFO — Child table for employment data.
• IGS_SV_FINANCE_INFO — Child table for financial data.
• IGS_SV_LEGAL_INFO — Child table for legal information.
• IGS_SV_OTH_INFO — Child table for other supplemental data.
• IGS_SV_PRGMS_INFO — Child table for program information.

Together these tables form the complete SEVIS batch submission record set, with IGS_SV_PERSONS acting as the hub that ties each student to their batch and to the associated detail records.