Results for “visa_expiry_date”

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

Overview

The view IGS_SV_EDT_TRAVEL_V belongs to the Oracle EBS IGS – Student System product family, a module that is documented as obsolete in the ETRM reference set for releases 12.1.1 and 12.2.2. Its stated purpose is to fetch modified legal information for non-immigrant persons, exposing passport, visa, and admission details required for regulatory reporting and downstream travel or immigration processing.

In the context of Oracle EBS reporting and integration, this view functions as a filtered presentation layer over the core legal-information table. Rather than returning all legal records, it restricts output to those rows associated with a batch summary entry whose tag code is SV_LEGAL and whose admission action code is SEND. This design supports the typical Student System workflow in which legal and immigration data changes are staged in a batch and then released for transmission to external agencies or interfaces. A user searching for visa_expiry_date will find that concept surfaced here under the alias VISA_EXPIRY_DATE.

Underlying Base Objects

The view is defined over two base tables documented in the view text:

• IGS_SV_LEGAL_INFO (aliased LGL) – the source of passport, visa, I-94, port-of-entry, and remarks data.
• IGS_SV_BTCH_SUMMARY (aliased TRAVELSUMM) – the batch control table that supplies the tag code and admission action code used for filtering.

The join is an equi-join on both PERSON_ID and BATCH_ID, ensuring that each legal information row is matched to its corresponding batch summary record. The filter predicates TRAVELSUMM.TAG_CODE = 'SV_LEGAL' and TRAVELSUMM.ADM_ACTION_CODE = 'SEND' narrow the result set to legal records earmarked for transmission.

The ETRM metadata notes that this object is not implemented in this database, and no referenced base objects are separately documented for the 12.2.2 metadata set. Consequently, the view text itself remains the authoritative definition. Because the owning module is obsolete, the view may be absent or unsupported in a given 12.1.1 or 12.2.2 instance.

Key Columns

The view exposes thirteen columns, several of which are renamed from their base-table equivalents:

• PERSON_ID – identifier of the person to whom the legal record belongs.
• BATCH_ID – identifier of the batch through which the record is processed.
• PSPRT_NUMBER – passport number.
• PSPT_ISSUING_CNTRY – passport issuing country (aliased from PSPT_ISSUING_CNTRY_CODE).
• PSPT_EXPIRY_DATE – passport expiration date (aliased from PSPRT_EXP_DATE).
• VISA_NUMBER – visa number.
• VISA_ISSUING_CNTRY – visa issuing country (aliased from VISA_ISSUING_CNTRY_CODE).
• VISA_EXPIRY_DATE – visa expiration date, aliased from VISA_EXPIRATION_DATE; this is the column most directly associated with the visa_expiry_date search term.
• ADMISSION_NUMBER – I-94 admission number (aliased from I94_NUMBER).
• PORT_OF_ENTRY – port of entry into the country.
• DATE_OF_ENTRY – date of entry.
• REMARKS – free-text remarks attached to the legal record.
• VISA_ISSUE_DATE – date the visa was issued.

Common Use Cases and Queries

Typical scenarios include identifying non-immigrant students or scholars whose visas are nearing expiration, auditing legal information pending transmission, and feeding external immigration interfaces. A representative query listing visa expiration data for a person is:

• SELECT person_id, visa_number, visa_expiry_date, visa_issuing_cntry FROM igs_sv_edt_travel_v WHERE person_id = :person_id;
• SELECT person_id, psprt_number, pspt_expiry_date FROM igs_sv_edt_travel_v WHERE pspt_expiry_date < SYSDATE + 90;
• SELECT batch_id, person_id, visa_expiry_date, admission_number FROM igs_sv_edt_travel_v WHERE batch_id = :batch_id ORDER BY person_id;

Because the view already restricts results to SV_LEGAL batches with an admission action of SEND, callers need not repeat those predicates. Users on a release where the obsolete Student System objects are not installed should expect an invalid-object or object-not-found error and must confirm availability against their specific 12.1.1 or 12.2.2 installation before relying on the view.