Results for “visit_start_date”

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

Overview

The view APPS.IGSFV_PORT_OF_ENTRIES is a read-only reporting object within the Oracle E-Business Suite IGS — Student System product family. Its documented purpose is to present information about a person's port of entries — the border crossing or point of entry through which a student, applicant, or affiliated party entered a country, typically in the context of international admissions, visa tracking, and student immigration compliance. In Oracle EBS 12.1.1 and 12.2.2, the view is exposed in the APPS schema with a status of VALID, where it serves as a denormalized read layer that simplifies developer and end-user access to the underlying visit-and-visa history model.

Because the view is defined WITH READ ONLY, it is intended strictly for query, reporting, and integration consumption. It shields consumers from the multi-table join logic required to associate visit history, visa detail, and party identity, and it exposes an Oracle globalization placeholder label (_LA:PVH.PORT_OF_ENTRY) that maps to a lookup on IGS_LOOKUP_VALUES using the lookup type PE_US_PORT_OF_ENTRY keyed by MEANING. This design is characteristic of Oracle EBS views that support both functional reporting and translation-aware display of lookup-driven attributes.

Underlying Base Objects

The view is defined over three joined base tables, each owned by the APPS schema in the Student System data model:

• IGS_PE_VISIT_HISTRY (PVH) — the driving table and source of entry-form number, visit start and end dates, remarks, visa identifier, and audit metadata. It represents historical records of a party's visits and port-of-entry events.
• IGS_PE_VISA (PEV) — joined to IGS_PE_VISIT_HISTRY on VISA_ID. It supplies visa type and visa issue date and links the visit to a specific visa record.
• HZ_PARTIES (HZP) — joined to IGS_PE_VISA on PARTY_ID = PERSON_ID. It provides the person's party number, which is the canonical identifier used across the Trading Community Architecture (TCA) model.

The documented ETRM metadata for this object lists no explicitly documented referenced base objects; the relationships above are derived from the view text itself, which is the authoritative definition. The join path is visa-centric: a visit record must resolve to a visa, and the visa must resolve to a TCA party, for a row to appear.

Key Columns

• "_LA:PORT_OF_ENTRY" — the localized label column, resolving the port-of-entry lookup meaning from IGS_LOOKUP_VALUES (PE_US_PORT_OF_ENTRY).
• COUNTRY_ENTRY_FORM_NUM — the country entry form or number associated with the visit, typically correlating to the immigration document presented at entry.
• VISIT_START_DATE / VISIT_END_DATE — the effective dates bracketing the person's visit, used for period-of-stay reporting and compliance monitoring.
• REMARKS — free-text annotations recorded against the visit history.
• PERSON_NUMBER — the TCA party number uniquely identifying the person.
• VISA_TYPE / VISA_ISSUE_DATE — visa classification and issuance date derived from IGS_PE_VISA.
• VISA_ID — the linking key between visit history and visa records.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS audit columns for traceability and incremental extraction.

Common Use Cases and Queries

Typical scenarios include international admissions review, visa and immigration compliance reporting, port-of-entry auditing, and data extraction for regulatory or governmental submissions. Because the view is read-only and pre-joined, it is well suited to OBIEE/BI Publisher datasets, Oracle Reports, and inbound integrations that require visit-visa-party alignment.

A simple retrieval by person would resemble:

SELECT person_number, "COUNTRY_ENTRY_FORM_NUM", visit_start_date,
       visit_end_date, visa_type, visa_issue_date, remarks
FROM   apps.igsfv_port_of_entries
WHERE  person_number = :p_party_number
ORDER  BY visit_start_date DESC;

For compliance monitoring over a date range:

SELECT person_number, visa_type, visit_start_date, visit_end_date
FROM   apps.igsfv_port_of_entries
WHERE  visit_start_date BETWEEN :p_from_date AND :p_to_date;

Because the view is defined WITH READ ONLY, INSERT, UPDATE, and DELETE operations are not permitted; consumers requiring maintenance must write to the base tables IGS_PE_VISIT_HISTRY and IGS_PE_VISA through supported Student System APIs rather than the view.