Search Results visa_id




Overview
Explore in AI Chat

Overview

IGS.IGS_PE_VISIT_HISTRY is a transactional table in the Oracle EBS Student Systems / People Enterprise (IGS) product family, designed to record the history of visits made by a person on a visa, including the port through which the person entered the country. In the Oracle EBS 12.1.1 and 12.2.2 data models, it functions as a supporting detail table within the person and visa management domain, capturing entry and exit events associated with a specific visa record.

Based on heuristic Data Vault classification derived from the foreign key structure, this object is best modeled as a satellite. It hangs off the parent visa entity (IGS_PE_VISA) via the VISA_ID foreign key and stores descriptive, time-bound attributes about each visit rather than acting as an independent hub of business keys. The narrowly scoped nature of the table supports this classification.

Key Information Stored

The table contains 32 documented columns. The most significant are:

  • CNTRY_ENTRY_FORM_NUM (VARCHAR2, 30) — the form number issued to enter the country. This is a business-key candidate and part of the composite primary key.
  • PORT_OF_ENTRY (VARCHAR2, 30) — the port through which the person entered. Also a business-key candidate and part of the primary key.
  • VISA_ID (NUMBER, 15) — the surrogate reference to the parent visa record; this is a foreign key to IGS_PE_VISA and is indexed non-uniquely.
  • VISIT_START_DATE (DATE) — the date the person entered the country.
  • VISIT_END_DATE (DATE) — the date the visit ended.
  • REMARKS (VARCHAR2, 500) — free-text remarks about the port of entry.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard Oracle EBS descriptive flexfield (DFF) context and attribute columns for extensibility.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

The composite primary key IGS_PE_VISIT_HISTRY_PK (PORT_OF_ENTRY, CNTRY_ENTRY_FORM_NUM) uniquely identifies each visit-history row. Notably, the unique index ordering appears in the metadata as (PORT_OF_ENTRY, CNTRY_ENTRY_FORM_NUM), while the primary key is listed as (CNTRY_ENTRY_FORM_NUM, PORT_OF_ENTRY); both columns together form the business key. The VISA_ID column is indexed by IGS_PE_VISIT_HISTRY_N1 for efficient parent-child lookups.

Common Use Cases and Queries

Typical scenarios include tracking all visits associated with a visa, auditing entry events by port, and reporting on visa holders whose visits have ended or remain open. A common retrieval pattern joins the visit history to its parent visa record:

SELECT v.PORT_OF_ENTRY,
       v.CNTRY_ENTRY_FORM_NUM,
       v.VISIT_START_DATE,
       v.VISIT_END_DATE,
       v.REMARKS
FROM   IGS.IGS_PE_VISIT_HISTRY v
WHERE  v.VISA_ID = :p_visa_id
ORDER BY v.VISIT_START_DATE;

Reporting on entries by port and period uses the primary-key columns and dates:

SELECT v.PORT_OF_ENTRY, COUNT(*) entries
FROM   IGS.IGS_PE_VISIT_HISTRY v
WHERE  v.VISIT_START_DATE BETWEEN :p_from AND :p_to
GROUP BY v.PORT_OF_ENTRY;

Because of the DFF columns, queries may also filter on attribute values where country-specific entry data is captured.

Related Objects

  • IGS.IGS_PE_VISA — parent table referenced via VISA_ID; the primary parent-child relationship.
  • IGS_PE_VISA (base view/entity) — the corresponding People Enterprise entity used in OA Framework pages and APIs.
  • Person and visa administrative pages in the IGS People Enterprise module that surface visit history.
  • Standard WHO audit columns reference FND_USER for CREATED_BY / LAST_UPDATED_BY.
  • Descriptive flexfield definitions via FND_DFF for ATTRIBUTE_CATEGORY-driven segments.

Because the metadata documents a single foreign key, the relationship footprint is deliberately small and centers on the visa entity; integrators should treat IGS_PE_VISA as the authoritative parent and use VISA_ID as the join path.