Results for “igs_sv_bio_info”

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

Overview

The IGS_SV_BIO_INFO table belongs to the IGS — Student System product family within Oracle E-Business Suite, and is documented as obsolete in ETRM for releases 12.1.1 and 12.2.2. It was designed to stage and retain biographical information for foreign students and exchange visitors whose data must be reported to the Student and Exchange Visitor Information System (SEVIS), the United States federal system administered for F, M, and J visa holders. The table captures records that are either newly created or updated, functioning as a working store of bio data prior to transmission or reconciliation with SEVIS.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is a reasonable suggestion because the table carries descriptive, person-attributed attributes (name, birth details, citizenship, visa type) keyed by PERSON_ID and BATCH_ID, rather than representing a pure hub or an association link between independent business entities. The composite primary key IGS_SV_BIO_INFO_PK is defined on (BATCH_ID, PERSON_ID), reinforcing the idea that a person's bio record is versioned or scoped by a processing batch. Note that the ETRM entry states the object is not implemented in this database, so it should be treated as a legacy or reference artifact rather than an active runtime table in current 12.1.1 / 12.2.2 environments.

Key Information Stored

The documented physical schema lists 24 columns owned by the IGS schema. The most significant attributes are:

• BATCH_ID — part of the composite primary key; identifies the processing batch or grouping under which the bio record was collected. It is also the foreign key column linking to IGS_SV_PERSONS in the documented relationship.
• PERSON_ID — the second component of the primary key and the identifier of the student or exchange visitor.
• LAST_NAME, FIRST_NAME, MIDDLE_NAME, SUFFIX — the person's name components as required by SEVIS reporting.
• BIRTH_DATE, BIRTH_CITY, BIRTH_CNTRY_CODE, BIRTH_CNTRY_RESN_CODE — birth data, including country of birth and reason code.
• CITIZEN_CNTRY_CODE, LEGAL_RES_CNTRY_CODE — citizenship and legal country of residence.
• GENDER and COMMUTER — demographic and commuting-status indicators.
• VISA_TYPE, POSITION_CODE, CATEGORY_CODE — classification attributes describing the visa and the individual's role or category.
• PRINT_FORM, REMARKS — control and free-text fields.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns.

The surrogate primary key is the composite (BATCH_ID, PERSON_ID). A unique index, IGS_SV_BIO_INFO_U1, is documented on the same (BATCH_ID, PERSON_ID) pair, serving as the business-key candidate. The table references IGS_SV_PERSONS through BATCH_ID.

Common Use Cases and Queries

Because the object is obsolete, practical use is largely historical, migration, or audit oriented. Typical scenarios include reconstructing SEVIS bio submissions for a given batch, validating completeness of foreign-student records, and comparing staged bio data against the master person record. A representative pattern joins the bio table to the persons table on the documented key:

• SELECT b.person_id, b.last_name, b.first_name, b.visa_type FROM igs_sv_bio_info b WHERE b.batch_id = :batch_id;
• SELECT b.*, p.* FROM igs_sv_bio_info b JOIN igs_sv_persons p ON b.batch_id = p.batch_id AND b.person_id = p.person_id;
• Completeness checks counting non-null CITIZEN_CNTRY_CODE, VISA_TYPE, or BIRTH_DATE per batch.
• Audit extraction filtered on LAST_UPDATE_DATE for change-tracking between batches.

Related Objects

The documented relationships identify the following significant dependents and references:

• IGS_SV_PERSONS — the primary referenced table, joined on BATCH_ID (and PERSON_ID in the composite key).
• IGS_SV_BIO_INFO_PK — the composite primary key constraint on (BATCH_ID, PERSON_ID).
• IGS_SV_BIO_INFO_U1 — the unique index on (BATCH_ID, PERSON_ID), the business-key candidate.

Additional SEVIS-oriented tables in the IGS schema (such as person, batch, and event staging tables) would conventionally support this object, but the ETRM metadata documents only the IGS_SV_PERSONS relationship as authoritative.