Search Results interface_visa_id

Overview

The IGS_PE_VISA_INT table is the interface (staging) table for the IGS_PE_VISA base table within the IGS – Student System product of Oracle E-Business Suite. It functions as a transient landing area where visa-related data extracted from external sources, legacy systems, or feeder processes is loaded, validated, and subsequently transferred into the permanent IGS_PE_VISA table. This staging pattern is standard throughout the Student System, allowing bulk import of person visa records without directly writing to transactional tables.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification labels this object as standalone. A standalone classification typically suggests a hub or independent entity that does not serve as a strict link between two parent hubs; the persistent target (IGS_PE_VISA) holds the durable business keys, while this interface table carries the incoming key values, attributes, and processing control columns.

Key Information Stored

The table contains 48 documented columns. The most significant include:

• INTERFACE_VISA_ID — the surrogate primary key (IGS_PE_VISA_INT_PK), uniquely identifying each staged row.
• INTERFACE_ID and INTERFACE_RUN_ID — correlate records to a specific interface load or run.
• VISA_TYPE, VISA_NUMBER, VISA_CATEGORY, and VISA_ISSUING_POST — the core visa identity attributes.
• VISA_ISSUE_DATE and VISA_EXPIRY_DATE — validity period at the source.
• VISA_ISSUING_COUNTRY — the country of issuance.
• PASSPORT_ID — foreign key to IGS_PE_PASSPORT, linking the visa to its passport of record.
• INTERFACE_VISA_ID also serves as the referenced key for IGS_PE_VST_HIST_INT.
• MATCH_IND, STATUS, and ERROR_CODE — control columns indicating match outcome and processing/validation errors.
• DUP_VISA_ID — identifies potential duplicate visa records detected during staging.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program execution context.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Developer extensibility attributes ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20.

The only unique index documented is IGS_PE_VISA_INT_PK on INTERFACE_VISA_ID, making it the sole business-key candidate; all other columns lack a uniqueness constraint in the metadata.

Common Use Cases and Queries

Typical usage centers on load validation and reconciliation. A common query pattern validates whether staged rows were matched to a passport:

• Filtering records with a non-null ERROR_CODE to isolate failed loads before correction.
• Joining PASSPORT_ID to IGS_PE_PASSPORT to confirm the referenced passport exists.
• Aggregating counts by STATUS and INTERFACE_RUN_ID to report load throughput per concurrent run.
• Detecting duplicates via DUP_VISA_ID or repeated VISA_NUMBER values.
• Auditing by REQUEST_ID/PROGRAM_ID to trace which concurrent program produced each batch.

Reporters frequently purge the interface table after successful transfer, so staging data is short-lived by design.

Related Objects

• IGS_PE_VISA — the persistent target receiving transferred records.
• IGS_PE_PASSPORT — referenced via PASSPORT_ID.
• IGS_PE_VST_HIST_INT — references this table through INTERFACE_VISA_ID.
• IGS_PE_PERSON — person context for the visa holder.
• Concurrent Programs / FND tables — via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.