Search Results date_of_entry




Overview
Explore in AI Chat

Overview

APPS.IGS_SV_EV_TRAVEL_BLK_V is a public Oracle E-Business Suite view owned by the APPS schema, registered under FND Design Data as IGS.IGS_SV_EV_TRAVEL_BLK_V with a status of VALID. It is documented as a view "for fetching legal informations for Exchange Visitor students," and its stated purpose is to support custom reporting and other data requirements where a consumer needs a consolidated, read-only projection of exchange visitor (J-1) legal and travel documentation. The name itself decomposes into the functional area (IGS_SV — Student and Scholar Services, the SEVIS-related module set), the entity (EV — Exchange Visitor), and the payload (TRAVEL_BLK — travel block data). It is not a transactional entry point; it is a reporting surface.

The view is significant in the SEVIS context because it presents the exact data elements that must accompany a batch submission of exchange visitor travel and entry records. Rather than requiring report authors to join the underlying batch and legal tables manually, the view pre-assembles them keyed by BATCH_ID and PERSON_ID.

Underlying Base Objects

The dependency metadata lists the following references: APPS.IGS_SV_BTCH_SUMMARY and IGS_SV_LEGAL_. IGS_SV_BTCH_SUMMARY supplies the batch-level context — the BATCH_ID that identifies a single run of the SEVIS process and the PRINT_FORM indicator controlling whether SEVIS is asked to produce a printed form. The IGS_SV_LEGAL_ object supplies the person-level legal and travel attributes, linked to the batch on PERSON_ID.

The presence of a trailing underscore on the legal object is consistent with the EBS convention of pairing a base table with a corresponding _ALL or staging table, and the view abstracts that naming from the caller. Because the view is a simple projection rather than an aggregation, it is generally safe to filter and join against it. Note that the view is described as public, which in ETRM terminology signals that it is exposed for customer reporting and customization without a formal support commitment to its internal definition.

Key Columns

The view exposes fifteen columns, all of which are relevant to a SEVIS exchange visitor travel record. BATCH_ID (NUMBER 14) and PERSON_ID (NUMBER 15) form the identifying keys. PRINT_FORM is a flag indicating whether form printing was requested.

Passport attributes are PSPRT_NUMBER, PSPRT_ISSUING_CNTRY_CODE, and PSPRT_EXP_DATE. Visa attributes are VISA_NUMBER, VISA_ISSUING_POST, VISA_ISSUING_CNTRY_CODE, VISA_ISSUE_DATE, and VISA_EXPIRATION_DATE. Entry-specific attributes are I94_NUMBER, PORT_OF_ENTRY, and the column the searcher asked about, DATE_OF_ENTRY.

DATE_OF_ENTRY is defined as VARCHAR2(10) and stores the date the student entered the country. This is a critical implementation detail: because it is character-typed rather than DATE-typed, it should not be compared against SYSDATE or used in date arithmetic without an explicit TO_DATE conversion. In practice these columns carry the SEVIS canonical date format. The same caveat applies to PSPRT_EXP_DATE, VISA_ISSUE_DATE, and VISA_EXPIRATION_DATE. REMARKS is a VARCHAR2(500) free-text field.

Common Use Cases and Queries

Typical uses are pre-submission audits of a SEVIS batch, reconciliation of entry dates against institutional records, and custom extracts. A minimal query follows the documented query text:

  • SELECT BATCH_ID, PERSON_ID, PRINT_FORM, PSPRT_NUMBER, PSPRT_ISSUING_CNTRY_CODE, PSPRT_EXP_DATE, VISA_NUMBER, VISA_ISSUING_POST, VISA_ISSUING_CNTRY_CODE, VISA_ISSUE_DATE, VISA_EXPIRATION_DATE, I94_NUMBER, PORT_OF_ENTRY, DATE_OF_ENTRY, REMARKS FROM APPS.IGS_SV_EV_TRAVEL_BLK_V;
  • Filter by batch: WHERE BATCH_ID = :batch_id to review one run of the SEVIS process.
  • Filter by person: WHERE PERSON_ID = :person_id to retrieve travel and visa history for one exchange visitor.
  • Date inspection: WHERE DATE_OF_ENTRY BETWEEN '20220101' AND '20221231' using the stored character format, or WHERE TO_DATE(DATE_OF_ENTRY,'YYYYMMDD') >= TRUNC(SYSDATE)-30.
  • Missing entry data: WHERE DATE_OF_ENTRY IS NULL OR PORT_OF_ENTRY IS NULL to flag records that would fail SEVIS validation.

Because the view is read-only and built for reporting, it should be consumed in SELECT statements only. Any correction to the underlying travel data must be made through the standard IGS_SV maintenance flows, not through statements against the view.