Search Results visit_end_date




Overview

The IGSBV_PORT_OF_ENTRIES view is a read-only reporting object owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) module. It presents information about a person's port of entries, recorded as part of immigration and visit-history tracking. The view is defined with the WITH READ ONLY clause, ensuring that it functions strictly as a query surface and cannot be used to modify underlying data through DML operations. Its "BV" prefix conventionally denotes a business view intended for downstream consumption by forms, reports, APIs, or external integrations rather than for direct transactional processing. In practice, the view consolidates port-of-entry attributes—such as country entry form number, visit dates, remarks, and visa identifier—into a single denormalized projection. Because it is valid and shipped in the APPS schema, it can be queried by custom reports, concurrent programs, and integration extracts without requiring direct access to the base visit-history table.

Underlying Base Objects

The view is defined over a single documented base object:

  • IGS_PE_VISIT_HISTRY (alias PVH) — the person visit-history table that stores immigration visit records for individuals tracked within the Student System.

All columns in the view are sourced directly from this table, with the exception of the first column, which is a lookup-derived literal concatenation. That column resolves the port-of-entry display value through the IGS lookup set identified as IGS_LOOKUP_VALUES:PE_US_PORT_OF_ENTRY, using the lookup meaning mapped against the person's port-of-entry code. ETRM documentation for release 12.2.2 records no additional referenced base objects beyond this relationship, so the view should be treated as a lightweight, single-table projection over the visit-history entity.

Key Columns

  • "_LA:PORT_OF_ENTRY" — a literal-based, lookup-resolved column exposing the human-readable port-of-entry description derived from the IGS port-of-entry lookup values.
  • COUNTRY_ENTRY_FORM_NUMBER — the immigration country entry form number associated with the visit record.
  • VISIT_START_DATE — the date the person's visit began.
  • VISIT_END_DATE — the date the visit concluded, where recorded.
  • REMARKS — free-text notes attached to the port-of-entry record.
  • VISA_ID — the visa identifier tying the visit record to the person's visa information; this column is the attribute most directly associated with the user's search term.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Oracle audit columns recording record provenance and modification history.

Common Use Cases and Queries

Because the view is read-only and exposed in the APPS schema, it is well suited to reporting on student and applicant immigration history, visa tracking, and port-of-entry audits. A frequent scenario is locating all visit records associated with a given visa, which directly reflects the searched term visa_id:

  • Visa-based lookup: SELECT VISA_ID, COUNTRY_ENTRY_FORM_NUMBER, VISIT_START_DATE, VISIT_END_DATE FROM APPS.IGSBV_PORT_OF_ENTRIES WHERE VISA_ID = :p_visa_id;
  • Port-of-entry reporting: SELECT "_LA:PORT_OF_ENTRY", COUNTRY_ENTRY_FORM_NUMBER, VISIT_START_DATE FROM APPS.IGSBV_PORT_OF_ENTRIES WHERE VISIT_START_DATE BETWEEN :p_from AND :p_to;
  • Audit extraction: selecting the audit columns alongside VISA_ID to reconcile record changes for integration feeds.

Developers should note the quoted mixed-case column name for the port-of-entry attribute and apply standard EBS security conventions when surfacing the view through concurrent programs, OAF pages, or BI Publisher reports.