Search Results stdnt_first_name

Overview

IGS_SV_CRT_STDT_BIO_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to fetch biographic information for new Non-Immigrant records. The view is registered as VALID in the ETRM metadata for ETRM 12.2.2 and is equally applicable to Oracle EBS 12.1.1 and 12.2.2 environments, where the IGS schema objects are deployed identically at the database tier.

The view functions as a denormalized projection over a single base table, IGS_SV_BIO_INFO, and exposes a curated set of columns needed to identify a student and construct the biographical portion of a Non-Immigrant (SEVIS-related) record. The most notable transformation is the aliasing of BIO.LAST_NAME to the column name STDNT_LAST_NAME. This alias is the direct answer to the search term "stdnt_last_name": the physical column on the base table is LAST_NAME, but the view presents it as STDNT_LAST_NAME so that downstream processes, concurrent programs, and interface extracts can reference student-specific column names consistently. Because the view is owned by APPS, it is ordinarily queried without a schema prefix in custom reports and SQL*Plus sessions connected as the APPS user.

Underlying Base Objects

The ETRM metadata documents the view text explicitly: the view is defined entirely over the single base table IGS_SV_BIO_INFO, aliased BIO in the SELECT statement. No additional joins, unions, or inline views are present. Consequently, the documented referenced base object is IGS_SV_BIO_INFO, and the ETRM "referenced base objects" field is recorded as none documented — a common artifact when the dependency metadata was not harvested rather than an indication that the view is standalone. Every column in IGS_SV_CRT_STDT_BIO_V derives directly from a column of IGS_SV_BIO_INFO, with the exception of the column name aliasing applied to the student-related attributes. No filter predicates, WHERE clauses, or bind variables appear in the documented view text, so the view returns all rows present in IGS_SV_BIO_INFO at query time. This has performance implications: callers are expected to restrict results by BATCH_ID or PERSON_ID rather than relying on the view to pre-filter the "new" Non-Immigrant population.

Key Columns

• BATCH_ID — Identifier of the batch to which the biographic record belongs. Batch grouping supports bulk processing of Non-Immigrant records.
• PERSON_ID — The primary person identifier from the Oracle HR/person model, linking the biographic record to the student's core person record.
• STDNT_LAST_NAME — The student's last name, aliased from BIO.LAST_NAME. This is the column returned when searching for "stdnt_last_name".
• STDNT_FIRST_NAME, STDNT_MIDDLE_NAME, STDNT_SUFFIX — Additional name components for the student, aliased from FIRST_NAME, MIDDLE_NAME, and SUFFIX respectively.
• STDNT_BIRTH_DATE — Date of birth, sourced from BIO.BIRTH_DATE.
• STDNT_GENDER — Gender code for the student.
• STDNT_BIRTH_CNTRY_CODE — Country of birth code.
• STDNT_CITIZEN_CNTRY_CODE — Country of citizenship code.
• STDNT_COMMUTER — Commuter indicator used in Non-Immigrant reporting.
• STDNT_VISA_TYPE — Visa type associated with the Non-Immigrant record.

Common Use Cases and Queries

The view is typically consumed by concurrent programs, PL/SQL validation routines, and custom extracts that build Non-Immigrant (SEVIS) record payloads. A typical query locates the biographic details for a known person or batch:

• SELECT batch_id, person_id, stdnt_last_name, stdnt_first_name, stdnt_birth_date, stdnt_visa_type FROM apps.igs_sv_crt_stdt_bio_v WHERE batch_id = :p_batch_id;
• SELECT person_id, stdnt_last_name, stdnt_first_name FROM apps.igs_sv_crt_stdt_bio_v WHERE person_id = :p_person_id;
• SELECT COUNT(*) FROM apps.igs_sv_crt_stdt_bio_v WHERE batch_id = :p_batch_id AND stdnt_visa_type IS NOT NULL;

Because the view applies no filtering, all practical queries should include a predicate on BATCH_ID, PERSON_ID, or both. When extending or troubleshooting integration logic, developers should note that the student-related column names (STDNT_*) exist only at the view layer; the underlying IGS_SV_BIO_INFO table uses unsuffixed names such as LAST_NAME.