Search Results agent_org_unit_name

Overview

IGSFV_VISAS is a read-only Oracle E-Business Suite view owned by the APPS schema that consolidates international person visa and passport information for reporting and integration purposes within the Oracle iRecruitment / Human Resources person-extra-information (PEI) model. It is defined over the IGS_PE_VISA, HZ_PARTIES, and IGS_PE_PASSPORT base tables and joins them into a single denormalized result set. In Oracle EBS 12.1.1 and 12.2.2, the view is exposed through the APPS schema and is commonly queried by reporting tools, interfaces, and personalizations that need to resolve a person visa record to its owning party number, associated agent organization, and passport details. The presence of the PARTY_NUMBER column directly addresses the common search term "party_number," allowing consumers to key visa data by the party number rather than the surrogate PERSON_ID or VISA_ID. Because the view is created WITH READ ONLY, no DML is permitted against it, and it is intended purely for query and extraction workloads.

Underlying Base Objects

The view is defined over four base objects:

• IGS_PE_VISA PEV — The driving table aliased PEV, holding visa records per person.
• HZ_PARTIES HZP1 — Joined on PERSON_ID = PARTY_ID to obtain the visa holder's PARTY_NUMBER.
• HZ_PARTIES HZP2 — Outer-joined on AGENT_ORG_UNIT_CD = PARTY_NUMBER to resolve the agent organization's PARTY_NAME.
• HZ_PARTIES HZP3 — Outer-joined on AGENT_PERSON_ID = PARTY_ID to resolve the agent contact's PARTY_NUMBER.
• IGS_PE_PASSPORT PEP — Outer-joined on PASSPORT_ID to bring in passport number and country code.

The ETRM metadata lists no documented referenced base objects for this view reference, so the join structure above is derived from the view text. Three of the four joins (agent organization, agent person, and passport) are outer joins, meaning visa rows will still return when agent or passport data is absent.

Key Columns

• PARTY_NUMBER — The party number of the visa holder (HZP1), the primary search key.
• VISA_TYPE, VISA_CATEGORY, VISA_NUMBER — Visa classification and identifier.
• VISA_ISSUE_DATE, VISA_EXPIRY_DATE — Validity window for the visa.
• AGENT_ORG_UNIT_CD, AGENT_CONTACT_NAME — Agent organization code and contact name.
• PARTY_NAME (HZP2) — Agent organization name.
• PARTY_NUMBER (HZP3) — Party number of the agent person.
• PASSPORT_NUMBER — Linked passport number (outer join).
• PERSON_ID, VISA_ID, AGENT_PERSON_ID, PASSPORT_ID — Surrogate identifiers for joins.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns.

Several columns contain descriptive flexfield and lookup tokens such as _DF:IGS:IGS_PE_INTL_VISA_FLEX:PEV and _LA:... references, which EBS reporting engines resolve at runtime to the corresponding meaning values.

Common Use Cases and Queries

A typical use case is listing all visas for a person identified by party number:

SELECT party_number, visa_type, visa_number, visa_expiry_date
FROM   apps.igsfv_visas
WHERE  party_number = :p_party_number;

Another common scenario retrieves visa and passport details together for immigration compliance reporting:

SELECT party_number, visa_type, visa_number,
       passport_number, visa_issue_date, visa_expiry_date
FROM   apps.igsfv_visas
WHERE  visa_expiry_date BETWEEN :from_date AND :to_date;

Users may also join the view to other party-related views on PARTY_NUMBER to enrich downstream reports. Because the view is read-only, all access is restricted to SELECT statements.