Results for “igs_ad_visa_type_all”

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

Overview

IGS_AD_VISA_TYPE_ALL is a reference (setup) table within the Oracle IGS – Student System product family. Its documented purpose is to describe the types of visas required for, or held by, international applicants and students tracked in the Oracle E-Business Suite student information model. In the EBS 12.1.1 and 12.2.2 data dictionary, the object is owned by the IGS schema and, per the ETRM metadata, is classified as obsolete and is not implemented in the surveyed database instance. The "_ALL" suffix follows the standard multi-organization convention, indicating that rows are filtered by ORG_ID, allowing a single logical visa-type list to be defined per operating unit or institution.

From a heuristic Data Vault modeling perspective, the mined relationship data classifies this table as standalone, with neither incoming nor outgoing foreign keys identified. That classification is consistent with its nature as a small domain-reference object: were it modeled in Data Vault terms, the natural hub would be built on VISA_TYPE as the business key, while descriptive attributes such as DESCRIPTION and CLOSED_IND would reside in an adjacent satellite keyed by the hub. Because there are no documented foreign-key relationships, it does not participate as a link table.

Key Information Stored

The documented physical schema for the 12.1.1 release defines nine columns. The most significant are:

• VISA_TYPE — the business identifier for each visa category (for example, student, exchange, or dependent classifications). It is the documented primary key component (IGS_AD_VISA_TYPE_PK) and the single-column unique index IGS_AD_VISA_TYPE_ALL_U1, making VISA_TYPE both the surrogate pivot and the sole business-key candidate.
• DESCRIPTION — the user-facing label presented in application lists of values and reports.
• ORG_ID — the multi-org discriminator that scopes each row to an operating unit, supporting the "_ALL" partitioning semantics.
• CLOSED_IND — an enable/disable flag allowing a visa type to be retired without deleting historical references.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set recording row provenance and last modification.

No additional descriptive columns beyond these are documented; the table carries no effective-dating columns or site-level overrides.

Common Use Cases and Queries

Typical usage is driven by validation and reporting. Application logic performs referential lookups to confirm that a visa type entered for an applicant is valid and open, while reporting layers join enrollment or admission data to this list to aggregate international-student populations by visa category.

A standard validation query checks that a submitted value is active within the caller's operating unit:

• SELECT visa_type, description FROM igs_ad_visa_type_all WHERE org_id = :p_org_id AND closed_ind = 'N' ORDER BY description;
• SELECT description FROM igs_ad_visa_type_all WHERE visa_type = :p_visa_type AND org_id = :p_org_id;

Reporting scenarios include headcount by visa category, auditing recently added categories using LAST_UPDATE_DATE, and identifying stale setup rows via CLOSED_IND. Because the table is a flat reference list, queries are inexpensive and are frequently cached by the application's list-of-values mechanism.

Related Objects

The supplied metadata documents no foreign-key relationships, so dependencies are best understood at the functional level. Objects expected to reference VISA_TYPE include the following;

• IGS_AD_APPLICANTS_ALL — holds visa type for incoming international applicants.
• IGS_AD_PERSONS / student records — carry visa status for enrolled students.
• IGS_AD_ADM_APPLN_ALL — admission applications capturing visa intent.
• IGS_EN_STUDENT_* enrollment tables — join visa category for aggregated reporting.
• IGS_AD_VISA_TYPE_TL (if implemented) — translated descriptions keyed by VISA_TYPE.

Because the metadata records the object as obsolete and not implemented, integration work should confirm whether the equivalent domain is now sourced from a successor table or from a shared reference set before building dependent logic.