Results for “pe_us_port_of_entry”

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

Overview

IGS_PE_VISIT_HISTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, supplied by the Oracle Student System / Student Information (IGS) product family. It consolidates visa-related information for a person with the history of physical visits across a national border, most notably entries into the United States. The view answers the operational question implied by the search term pe_us_port_of_entry: at which U.S. port did a given person enter, on which dates, and under which visa. It is designed for inquiry, reporting, and integration rather than for transactional data entry, so it is read-only in nature and can be joined freely to other person-centric views.

Because the view resolves the raw lookup code in the visit history to its user-facing meaning, it is particularly useful for printing visa and entry data on student records, SEVIS-related extracts, and immigration compliance reports.

Underlying Base Objects

• IGS_PE_VISIT_HISTRY (VV) — the driving table, holding one row per border-crossing or visit event, including the port-of-entry lookup code, entry form number, visit start and end dates, remarks, and twenty descriptive flexfield attribute columns.
• IGS_PE_VISA (PV) — joined on PV.VISA_ID = VV.VISA_ID, supplying the person identifier, visa type, number, issue and expiry dates, category, issuing post, and passport identifier.
• IGS_LOOKUP_VALUES (L1) — outer-joined to resolve VV.PORT_OF_ENTRY against LOOKUP_TYPE = 'PE_US_PORT_OF_ENTRY', yielding the descriptive meaning.

The join between visit history and visa is mandatory (inner join), so a visit row only appears when its visa record exists. The lookup join is denormalized with the outer-join operator (+), ensuring that visits with an unresolvable port code are still returned, with a null meaning.

Key Columns

• ROW_ID — the ROWID of the underlying visit history row, used for identifying a specific record.
• PORT_OF_ENTRY / PORT_OF_ENTRY_M — the coded port and its decoded meaning, the latter derived from the PE_US_PORT_OF_ENTRY lookup type.
• CNTRY_ENTRY_FORM_NUM — the country entry form number (for example, the I-94 or arrival record number).
• PERSON_ID, VISA_ID, PASSPORT_ID — the person, visa, and passport keys that link the record to the wider person model.
• VISA_TYPE, VISA_NUMBER, VISA_CATEGORY, VISA_ISSUING_POST, VISA_ISSUE_DATE, VISA_EXPIRY_DATE — the visa descriptor set inherited from IGS_PE_VISA.
• VISIT_START_DATE, VISIT_END_DATE — the effective period of the visit or authorized stay.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the descriptive flexfield segments for client-specific extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view supports immigration tracking for international students and scholars, visa compliance reporting, and reconciliation of entry events against visa validity dates. A typical query lists all U.S. entries for a person.

SELECT person_id, visa_number, port_of_entry_m, cntry_entry_form_num, visit_start_date, visit_end_date
FROM apps.igs_pe_visit_histry_v
WHERE person_id = :p_person_id;

A compliance query identifies visits occurring after the visa expiry date, or visits whose port code failed to resolve, which indicates a missing lookup value:

SELECT person_id, visa_number, port_of_entry, port_of_entry_m, visit_start_date
FROM apps.igs_pe_visit_histry_v
WHERE visit_start_date > visa_expiry_date
OR port_of_entry_m IS NULL;

For reporting integrations, the view can be joined to person and student views on PERSON_ID, and the attribute flexfield columns can be queried when a descriptive flexfield context is defined on the visit history entity.