Search Results pe_us_visa_issue_loc

Overview

The view APPS.IGS_PE_VISA_V belongs to the Student System (IGS) schema of Oracle E-Business Suite, specifically the People (PE) module, which manages person, passport, and visa records for students, applicants, and related parties. The view presents a consolidated, denormalized picture of visa data held in the core person visa entity, enriched with descriptive attributes drawn from organization, person, passport, lookup, and territory sources. Its principal purpose is to make visa information readily reportable without requiring consumers to reconstruct the numerous outer joins themselves.

The user search term pe_us_visa_issue_loc is significant here: it corresponds to the lookup type PE_US_VISA_ISSUE_LOC, which the view joins to in order to resolve the VISA_ISSUING_POST code into its readable VISA_ISSUING_POST_M meaning. This view is therefore the standard access path for reporting on United States visa issuing locations alongside visa and passport details.

Underlying Base Objects

Based on the documented view text, the view is defined over the following objects using Oracle outer-join syntax ((+)):

• IGS_PE_VISA (alias PV) — the driving table containing the core visa record.
• IGS_OR_INST_ORG_BASE_V (alias OU) — supplies organization unit name and start date for the visa agent organization.
• IGS_PE_PERSON_BASE_V (alias PE) — supplies the agent person number and full name.
• IGS_LOOKUP_VALUES (alias L1) — filtered to LOOKUP_TYPE = 'PE_US_VISA_ISSUE_LOC' to resolve issuing post meaning.
• IGS_PE_PASSPORT (alias PP) — supplies the passport number linked to the visa.
• FND_TERRITORIES_VL (alias TER) — resolves the issuing country code into a territory short name.

All joins are outer joins, meaning a visa row is returned even when the related agent organization, agent person, passport, issuing post lookup, or territory is missing. The ETRM metadata records no other documented base objects for this view in release 12.2.2.

Key Columns

• ROW_ID, VISA_ID — the row identifier and primary key of the underlying visa record.
• PERSON_ID — the person to whom the visa belongs.
• VISA_TYPE, VISA_NUMBER, VISA_CATEGORY — classification and identifier of the visa.
• VISA_ISSUE_DATE, VISA_EXPIRY_DATE — validity period of the visa.
• VISA_ISSUING_POST and VISA_ISSUING_POST_M — the issuing post code and its decoded meaning from lookup type PE_US_VISA_ISSUE_LOC.
• VISA_ISSUING_COUNTRY, MEANING — issuing country code and its territory short name.
• PASSPORT_ID, PASSPORT_NUMBER — associated passport details.
• AGENT_ORG_UNIT_CD, ORG_DESC, AGENT_OU_START_DATE — visa agent organization information.
• AGENT_PERSON_ID, AGENT_PERSON_NUMBER, PERSON_FULL_NAME — visa agent person details.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

This view is typically queried for visa compliance reporting, immigration tracking, and student visa expiry monitoring. A common scenario retrieves all visas for a person together with their issuing location and passport:

SELECT person_id, visa_type, visa_number,
       visa_issue_date, visa_expiry_date,
       visa_issuing_post_m, meaning issuing_country,
       passport_number
FROM   apps.igs_pe_visa_v
WHERE  person_id = :p_person_id;

A second scenario lists visas issued at a specific US post by joining on the decoded meaning:

SELECT visa_number, person_id, visa_issue_date
FROM   apps.igs_pe_visa_v
WHERE  visa_issuing_post_m = :p_post
AND    visa_expiry_date >= SYSDATE;

A third uses the audit and flexfield columns for data-quality extract, for example listing all agent organizations associated with visa records. Because all joins are outer joins, consumers should expect nulls in the descriptive columns whenever the corresponding reference data is absent, and should always qualify the view with the APPS schema prefix in custom SQL.