Results for “visa_category”

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

Overview

IGSBV_VISAS is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS – Student System product family. Its documented purpose is to expose information about a person's visa details. The view acts as a reporting and integration surface that joins visa records held against a student or person to the corresponding party record, so that consumers do not need to resolve the person-to-party relationship themselves. The view is marked VALID at the documented certifications (Oracle EBS 12.1.1 and 12.2.2) and is defined with a WITH READ ONLY clause, confirming that it is intended strictly for query access rather than for DML.

Because the view reads from IGS_PE_VISA and HZ_PARTIES directly, it sits at the boundary between the Student System's person records and the Trading Community Architecture (TCA) party model. This makes it convenient for extract-style reporting, student services dashboards, and interfaces that require visa attributes keyed against a party number.

Underlying Base Objects

The documented view text defines IGSBV_VISAS over two base objects:

• IGS_PE_VISA (aliased PEV) — the primary table holding visa rows for an individual. It supplies visa type, issue and expiry dates, visa number, visa category, passport identifier, agent organisation and agent person references, and the standard audit columns.
• HZ_PARTIES (aliased HZP) — the TCA party table, joined on PEV.PERSON_ID = HZP.PARTY_ID. It supplies PARTY_NUMBER, exposed by the view as PERSON_NUMBER.

No additional base objects are documented. The ETRM metadata records the referenced base objects as none, but the embedded view text confirms the two-object join above; this is the authoritative definition.

Key Columns

• PERSON_NUMBER — the TCA party number for the person, sourced from HZ_PARTIES.PARTY_NUMBER.
• VISA_CATEGORY — the visa category value, the column most often searched against this view.
• VISA_TYPE — the visa type code, with a descriptive translation exposed through the lookup column "_LA:VISA_TYPE_DESCRIPTION" resolved from HR_LOOKUPS (PER_US_VISA_TYPES:MEANING).
• VISA_NUMBER, VISA_ISSUE_DATE, VISA_EXPIRY_DATE — the identifying number and validity window of the visa.
• _LA:VISA_ISSUING_POST and _LA:VISA_ISSUING_COUNTRY — descriptive values resolved from IGS_LOOKUP_VALUES (PE_US_VISA_ISSUE_LOC:MEANING) and HR_LOOKUPS (PER_US_COUNTRY_CODE:MEANING) respectively.
• AGENT_ORG_UNIT_CD, AGENT_CONTACT_NAME, AGENT_PERSON_ID — details of any agent associated with the visa record.
• PERSON_ID, VISA_ID, PASSPORT_ID — primary and foreign key identifiers linking the visa to the person and passport.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns for change tracking.

Common Use Cases and Queries

Typical usage includes visa compliance reporting, expiry monitoring, and student onboarding checks. Because the view is read-only and pre-joined to HZ_PARTIES, queries are short and do not require manual party resolution.

To list all visas for a given person number:

• SELECT person_number, visa_type, visa_category, visa_number, visa_issue_date, visa_expiry_date FROM apps.igsbv_visas WHERE person_number = :p_party_number;

To find records by the searched attribute, visa_category:

• SELECT person_number, visa_category, visa_type, visa_expiry_date FROM apps.igsbv_visas WHERE visa_category = :p_visa_category ORDER BY visa_expiry_date;

To identify visas expiring within a reporting window:

• SELECT person_number, visa_number, visa_category, visa_expiry_date FROM apps.igsbv_visas WHERE visa_expiry_date BETWEEN TRUNC(SYSDATE) AND TRUNC(SYSDATE) + 90 ORDER BY visa_expiry_date;

Because descriptive translations for visa type, issuing post, and issuing country are exposed as virtual lookup columns, reports can retrieve human-readable values without additional joins, simplifying extract and integration logic across IGS student data and TCA party data.