Search Results igs_pe_vst_hist_int

Overview

IGS_PE_VST_HIST_INT is the interface (staging) table for the IGS_PE_VISIT_HISTRY entity within the Oracle EBS Student System (IGS) product module. It exists to receive and validate inbound records describing a person's visit history — typically entry/exit events associated with visas, ports of entry, and country entry forms — before those records are processed into their final destination tables. Like other IGS performance and person interface tables, it acts as a transient landing zone that supports bulk data loads, concurrent program-based imports, and error handling for rejected rows.

From a heuristic Data Vault classification, this table is modeled as a standalone satellite — it is heavily descriptive, carries no foreign key relationships to parent hubs beyond its interface reference to IGS_PE_VISA_INT, and is anchored by a single surrogate key. The metadata indicates it does not participate in a link structure, so it is best modeled as a satellite recording visit-history attributes keyed by its own identifier.

Key Information Stored

The table contains 43 documented physical columns. The most significant are:

• INTERFACE_VISIT_HISTRY_ID — the surrogate primary key (index IGS_PE_VST_HIST_INT_PK); serves as the unique business-key candidate for each staged visit-history record.
• INTERFACE_VISA_ID — foreign key referencing IGS_PE_VISA_INT, linking the visit-history row to the associated visa interface record.
• PORT_OF_ENTRY and CNTRY_ENTRY_FORM_NUM — the port and country entry form details describing the visit.
• VISIT_START_DATE and VISIT_END_DATE — the temporal boundaries of the visit event.
• REMARKS — free-text notes attached to the visit.
• DUP_PORT_OF_ENTRY and DUP_CNTRY_ENTRY_FORM_NUM — duplicate-detection flags capturing values that match existing records.
• MATCH_IND, STATUS, and ERROR_CODE — interface processing controls indicating match status, row-level status, and validation errors.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, and INTERFACE_RUN_ID — concurrent program audit columns identifying the loading process.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard EBS extensibility (flexfield) columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical uses include loading external visit-history extracts, monitoring import errors, and reconciling staged rows against the base IGS_PE_VISIT_HISTRY table. A common validation query identifies failed rows:

• SELECT interface_visit_history_id, status, error_code FROM igs.igs_pe_vst_hist_int WHERE status = 'ERROR';
• SELECT interface_visit_history_id, port_of_entry, visit_start_date, visit_end_date FROM igs.igs_pe_vst_hist_int WHERE match_ind = 'N';
• Joining to the visa interface to enrich reporting: SELECT h.*, v.* FROM igs.igs_pe_vst_hist_int h, igs.igs_pe_visa_int v WHERE h.interface_visa_id = v.interface_visa_id;

Reporting scenarios commonly track rows by INTERFACE_RUN_ID or REQUEST_ID to audit a specific concurrent import run.

Related Objects

• IGS_PE_VISA_INT — referenced via INTERFACE_VISA_ID; the immediate parent interface record.
• IGS_PE_VISIT_HISTRY — the base (non-interface) table this staging table ultimately populates.
• IGS_PE_VST_HIST_INT_PK — the primary key index enforcing uniqueness on INTERFACE_VISIT_HISTRY_ID.
• IGS person/visa import concurrent programs that consume rows from this table and write the processed results forward.
• Related IGS interface tables sharing the ATTRIBUTE and PROGRAM_* audit pattern, useful for consistent error-reporting queries.