Search Results reprint_rsn_code

Overview

The IGS.IGS_SV_DEPDNT_INFO table is a transactional data store within the Oracle E-Business Suite (EBS) Student System and Student Information (IGS) product family. It holds dependent information for foreign students and exchange visitors that is reported to the Student and Exchange Visitor Information System (SEVIS), the U.S. government system administered by the Department of Homeland Security for tracking F, M, and J visa holders. The table is owned by the IGS schema and is registered in FND Design Data as IGS.IGS_SV_DEPDNT_INFO, with a status of VALID in both EBS 12.1.1 and 12.2.2. It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a data modeling perspective, the heuristic Data Vault classification for this object is link. This reflects its role as an associative structure connecting a batch, a person, and a dependent identifier through its composite primary key, rather than acting as an independent hub of business keys or a purely descriptive satellite.

Key Information Stored

The table's physical schema as documented in ETRM 12.1.1 contains thirty-three columns. The primary key is defined by the unique index IGS_SV_DEPDNT_INFO_U1 over the columns BATCH_ID, PERSON_ID, and DEPDNT_ID, which together form the business-key candidate for the table. The primary key constraint is IGS_SV_DEPDNT_INFO_PK. A non-unique index, IGS_SV_DEPDNT_INFO_N1, supports lookups by PERSON_ID and DEPDNT_ID.

Key columns include:

• BATCH_ID (NUMBER 14) — Batch identifier used for the run of the SEVIS process; part of the unique index.
• PERSON_ID (NUMBER 15) — Person identifier associated with the record; part of the unique index and a foreign key to HZ_PARTIES.
• DEPDNT_ID (NUMBER 15) — Student dependent record identifier; part of the unique index.
• PERSON_NUMBER (VARCHAR2 30) — Person number of the dependent being reported to SEVIS.
• DEPDNT_SEVIS_ID (VARCHAR2 11) — SEVIS identifier assigned to the dependent.
• DEPDNT_ACTION_TYPE — Dependent action being taken on the record.
• VISA_TYPE — Visa classification held by the dependent.
• LAST_NAME, FIRST_NAME, MIDDLE_NAME, SUFFIX — Person name components for the dependent.
• BIRTH_DATE, GENDER — Demographic attributes transmitted to SEVIS.
• RELATIONSHIP — Relationship of the dependent to the student.
• TERMINATION_REASON — Reason code for termination of the dependent relationship.
• REPRINT_RSN_CODE and REPRINT_REMARKS — Reason code and remarks explaining a reprint request, which is the specific column the user searched for.
• PRINT_FORM — Flag indicating whether the form should be printed.
• BIRTH_CNTRY_RESN_CODE — Reason code recorded when the birth country is the U.S. or a U.S. territory.

Common Use Cases and Queries

The primary use case for this table is preparing, tracking, and auditing the dependent records that are transmitted to SEVIS during batch runs. A typical operational query retrieves all dependents for a given batch and person, joining to HZ_PARTIES to resolve the dependent identity:

• SELECT d.* FROM igs.igs_sv_depdnt_info d WHERE d.batch_id = :batch_id AND d.person_id = :person_id;
• Joining to IGS_SV_PERSONS on BATCH_ID to retrieve the student's SEVIS person record.
• Reporting on PRINT_FORM flags to determine which dependent forms require printing.
• Filtering on REPRINT_RSN_CODE to analyze reprinting activity and identify patterns in why forms are reprinted.

Reporting use cases include SEVIS compliance audits, dependent demographic extracts, and reconciliation of action types against submitted records.

Related Objects

The most significant related objects, derived from the documented foreign keys, include:

• HZ_PARTIES — Referenced via PERSON_ID; provides party-level identity data for the person associated with the dependent.
• IGS_SV_PERSONS — Referenced via BATCH_ID; supplies the parent SEVIS person record for the batch run.
• IGS_SV_DEPDNT_INFO_U1 and IGS_SV_DEPDNT_INFO_N1 — Indexes supporting batch, person, and dependent lookups.

Additional dependent data used during SEVIS processing is typically retrieved through joins on BATCH_ID and PERSON_ID to other IGS SEVIS tables, and the parent identity always resolves through HZ_PARTIES.