Search Results dup_cntry_entry_form_num

Overview

IGS.IGS_PE_VST_HIST_INT is the interface staging table used by Oracle EBS Student System / PeopleSoft-adjacent Person and Visa import processes to hold visit history and port-of-entry information before it is validated and promoted into the permanent IGS_PE_VISIT_HISTRY table. It belongs to the IGS product (the legacy "Student Systems" schema family) and resides in the APPS_TS_INTERFACE tablespace, which is the standard EBS location for open interface tables. The table's display name, "Import Visit History," and its documented scope ("Contains the visit history/port of entry information for each person to be imported into IGS_PE_VISIT_HISTRY") confirm its role as a transient landing zone in a batch import pipeline.

The metadata classifies this object as standalone under the heuristic Data Vault analysis. In Data Vault modeling terms, a standalone classification typically suggests this table behaves like a satellite at the raw interface layer—it holds descriptive attributes keyed by a surrogate identifier (INTERFACE_VISIT_HISTRY_ID) with no direct foreign-key enforcement outward. The only documented FK relationship (INTERFACE_VISA_ID → IGS_PE_VISA_INT) reinforces that this is a child/detail staging entity rather than a hub or link itself.

Key Information Stored

The table carries 43 documented columns, dominated by a large block of WHO/DDF-style audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) and 20 generic ATTRIBUTE1–ATTRIBUTE20 flex columns. The functionally significant columns are:

• INTERFACE_VISIT_HISTORY_ID (NUMBER) — surrogate primary key, backed by unique index IGS_PE_VST_HIST_INT_PK. It is the only documented unique business-key candidate.
• INTERFACE_VISA_ID (NUMBER) — FK to IGS_PE_VISA_INT, linking the visit record to its parent visa import row.
• PORT_OF_ENTRY (VARCHAR2 30) — the port through which the person entered the country.
• CNTRY_ENTRY_FORM_NUM (VARCHAR2 30) — the form number issued at country entry. This is the column many users search for by the misspelled variant dup_cntry_entry_form_num; the actual stored duplicate-detection column is DUP_CNTRY_ENTRY_FORM_NUM.
• DUP_PORT_OF_ENTRY and DUP_CNTRY_ENTRY_FORM_NUM — duplicate-detection mirrors populated by the import validation logic to flag suspected duplicate entries before merge.
• VISIT_START_DATE / VISIT_END_DATE (DATE) — the date range of the visit.
• REMARKS (VARCHAR2 500) — free-text port-of-entry notes.
• MATCH_IND — indicator of whether the row matched an existing record.
• STATUS — interface processing state (indexed by IGS_PE_VST_HIST_INT_N2).
• ERROR_CODE — populated when validation fails.
• INTERFACE_RUN_ID — groups rows by batch run (indexed by IGS_PE_VST_HIST_INT_N1).
• ATTRIBUTE_CATEGORY — standard DFF context column.

Common Use Cases and Queries

Typical uses include pre-import review, error triage, duplicate investigation, and post-run reconciliation. Common query patterns:

• Review pending rows for a batch: SELECT * FROM igs.igs_pe_vst_hist_int WHERE interface_run_id = :run_id AND status = 'NEW';
• Find validation failures: SELECT interface_visit_histry_id, error_code FROM igs.igs_pe_vst_hist_int WHERE status = 'ERROR';
• Duplicate investigation using the user-search column: SELECT a.interface_visit_histry_id, a.cntry_entry_form_num, a.dup_cntry_entry_form_num FROM igs.igs_pe_vst_hist_int a WHERE a.dup_cntry_entry_form_num IS NOT NULL;
• Join to the parent visa import to build a combined view of visa and entry details.

Related Objects

• IGS.IGS_PE_VISA_INT — parent interface table via INTERFACE_VISA_ID.
• IGS.IGS_PE_VISIT_HISTRY — the permanent target table populated from this interface.
• IGS_PE_VST_HIST_INT_PK / _N1 / _N2 / _N3 — indexes on the primary key, INTERFACE_RUN_ID, STATUS, and INTERFACE_VISA_ID respectively.
• Standard concurrent program and request metadata (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) link back to FND_CONCURRENT_REQUESTS.