Search Results igs_pe_passport




Overview
Explore in AI Chat

Overview

The IGS_PE_PASSPORT table is a component of the Oracle E-Business Suite IGS (Student System) product family, a module now classified as obsolete in the ETRM documentation set for releases 12.1.1 and 12.2.2. The table's documented purpose is to hold all passport-related information associated with a person record. In the Oracle EBS data model, this object functions as a person-level identity document store, capturing the passport details that institutions collect for applicants, students, and other constituents during admissions, registration, and visa processing workflows.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This classification suggests the table behaves primarily as a satellite attached to a person hub, carrying descriptive and time-bound attributes about a passport rather than acting as an independent business entity hub or a pure link between two hubs. The relationship to HZ_PARTIES via PERSON_ID supports this interpretation, while the presence of dependent child tables (notably IGS_PE_VISA) indicates the satellite participates in a broader document-tracking hierarchy.

Implementation notes in the metadata record that the object is not implemented in the reference database instance, which is consistent with its obsolete status. Organizations running legacy Student System deployments may still encounter the table in historical schemas.

Key Information Stored

The physical schema documents 31 columns owned by the IGS schema. The most significant columns include:

  • PASSPORT_ID — The surrogate primary key, uniquely identifying each passport record. Documented as the basis of the IGS_PE_PASSPORT_PK unique index.
  • PERSON_ID — Foreign key to HZ_PARTIES, linking the passport to the owning party record.
  • PASSPORT_NUMBER — The passport number as issued by the governing authority.
  • PASSPORT_CNTRY_CODE — The country code of the issuing authority, forming part of the business-key candidate.
  • PASSPORT_EXPIRY_DATE — The expiration date of the passport.

A secondary unique index, IGS_PE_PASSPORT_U1, is defined over PERSON_ID, PASSPORT_CNTRY_CODE, and PASSPORT_NUMBER, establishing these three columns as the documented business-key candidate. This composite key enforces the natural uniqueness of a passport within a person and issuing-country combination. The remaining attributes are the standard EBS descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20, together with the standard Who columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting and operational scenarios include retrieving all passports for a given person, identifying passports nearing expiry, and joining passport data to visa records for immigration reporting. A representative query retrieving active passport details is:

  • SELECT p.passport_number, p.passport_cntry_code, p.passport_expiry_date FROM igs_pe_passport p WHERE p.person_id = :person_id;
  • Expiry monitoring: SELECT person_id, passport_number FROM igs_pe_passport WHERE passport_expiry_date < SYSDATE + 90;
  • Visa correlation: joining IGS_PE_PASSPORT to IGS_PE_VISA on PASSPORT_ID to report passport and visa status together.

Because the module is obsolete, these patterns most commonly appear in historical data migration, archival extraction, or reconciliation efforts when moving legacy Student System data to a successor platform.

Related Objects

The following objects are documented as participating in foreign key relationships with IGS_PE_PASSPORT:

  • HZ_PARTIES — Referenced via IGS_PE_PASSPORT.PERSON_ID; the parent party hub supplying the person identity.
  • IGS_PE_VISA — References IGS_PE_PASSPORT via IGS_PE_VISA.PASSPORT_ID; the primary dependent child table.
  • IGS_PE_VISA_INT — Also references IGS_PE_PASSPORT via PASSPORT_ID; the interface variant of the visa entity.

These relationships define the satellite's position within the Student System identity and immigration document model, with HZ_PARTIES as the upstream hub and the visa tables as downstream dependents.