Search Results per_us_country_code

Overview

IGS.IGS_PE_VISA_INT is a public interface (staging) table in the Oracle E-Business Suite Student Systems (IGS) product line. Its display name, Import Visa, reflects its purpose: it holds visa information for each person to be imported into the permanent IGS_PE_VISA table. This is a classic interface-table pattern in Oracle EBS, where external or legacy data is loaded first into a staging structure, validated and matched, and then pushed to the production entity via a concurrent program.

The table resides in the APPS_TS_INTERFACE tablespace with PCT Free 10 and carries an FND Design Data registration of IGS.IGS_PE_VISA_INT, indicating it is a recognized, dictionary-registered object. Its lifecycle is active and its scope is public. Functionally, the table is categorized as a BUSINESS_ENTITY associated with HZ_PERSON, tying visa records to the person model shared with Oracle Trading Community Architecture.

From a Data Vault modeling perspective, the heuristic classification is standalone. No foreign keys were mined from the schema, so the object does not behave as a hub, link, or satellite in the strict relational sense. It is best treated as a transient staging satellite keyed by its own surrogate identifier, with the natural business key of the visa record materialized only after the import process resolves it.

Key Information Stored

The table contains 48 documented columns. The most significant are listed below.

• INTERFACE_VISA_ID (NUMBER 15, NOT NULL) — the surrogate primary key, uniquely indexed by IGS_PE_VISA_INT_PK. It is a technical identifier assigned at staging time, not a business key.
• INTERFACE_ID (NUMBER 15) — links the row to the parent interface batch; indexed non-uniquely by IGS_PE_VISA_INT_N1.
• INTERFACE_RUN_ID (NUMBER 15) — identifies the specific concurrent run that processed the row; indexed by IGS_PE_VISA_INT_N3.
• STATUS (VARCHAR2 30) — processing state of the staged row; indexed by IGS_PE_VISA_INT_N2 and central to error/retry queries.
• DUP_VISA_ID — identifier of a duplicate visa record detected during matching; the column directly relevant to the "dup_visa_id" search.
• MATCH_IND — match indicator flag set by the matching logic.
• ERROR_CODE — validation or processing error assigned during import.
• VISA_TYPE, VISA_NUMBER, VISA_ISSUE_DATE, VISA_EXPIRY_DATE, VISA_CATEGORY, VISA_ISSUING_POST, VISA_ISSUING_COUNTRY — the core visa attributes carried forward to IGS_PE_VISA.
• PASSPORT_ID (NUMBER 15) — the passport associated with the visa.
• AGENT_ORG_UNIT_CD, AGENT_PERSON_ID, AGENT_CONTACT_NAME — agent attribution for the visa record.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

The only documented unique index is the primary key on INTERFACE_VISA_ID; no separate natural business-key unique index is defined, so business-key enforcement occurs downstream.

Common Use Cases and Queries

The dominant scenario is diagnosing duplicates. The DUP_VISA_ID column supports queries that isolate rows flagged as duplicates during the import match:

• Identify failed or duplicate rows: SELECT INTERFACE_VISA_ID, INTERFACE_ID, VISA_NUMBER, DUP_VISA_ID, STATUS, ERROR_CODE FROM IGS.IGS_PE_VISA_INT WHERE DUP_VISA_ID IS NOT NULL;
• Scope by interface run: add WHERE INTERFACE_RUN_ID = :run_id to reconcile a single concurrent request.
• Validate batch contents before import: SELECT STATUS, COUNT(*) FROM IGS.IGS_PE_VISA_INT WHERE INTERFACE_ID = :interface_id GROUP BY STATUS;
• Track records that never reached production: compare INTERFACE_VISA_ID counts against the target IGS_PE_VISA rows.

Reporting typically joins the staging row to its interface header to obtain batch-level context, and uses the STATUS and ERROR_CODE columns to produce remediation worklists for data stewards.

Related Objects

• IGS.IGS_PE_VISA — the permanent target entity into which validated staged rows are imported.
• HZ_PERSON (and its parent business entity) — the person model the visa records attach to.
• The IGS interface header table — joined via INTERFACE_ID.
• FND_CONCURRENT_REQUESTS — reconciled through REQUEST_ID and PROGRAM_ID to identify the processing run.
• The Import Visa concurrent program — the executable that reads this table, populates MATCH_IND, STATUS, ERROR_CODE, and DUP_VISA_ID, and writes to IGS_PE_VISA.
• FND Design Data registration IGS.IGS_PE_VISA_INT — the metadata layer used by ETRM and the diagnostics tools.

Because no FK constraints are documented, relationships are logical rather than enforced, and joins should be written defensively with appropriate outer joins on INTERFACE_ID and INTERFACE_RUN_ID.