Search Results igs_pe_passport_int

Overview

IGS_PE_PASSPORT_INT is the interface (staging) table for the IGS_PE_PASSPORT entity within the Oracle E-Business Suite IGS – Student System product line. In the ETRM 12.1.1 physical schema, the table is owned by the IGS schema and contains 40 documented columns. Its stated purpose in the ETRM metadata is to act as the inbound interface table for the base passport record, meaning it receives and holds passport-related data during a batch import or concurrent program run before that data is validated and transferred into the production passport table. The metadata explicitly notes that the object is "Not implemented in this database," indicating that in the specific environment surveyed, the table was not present—a common situation in 12.1.1 and 12.2.2 installations where certain IGS functionality was never provisioned or was desupported.

The documented primary key is IGS_PE_PASSPORT_INT_PK, defined on the single column INTERFACE_PASSPORT_ID. A unique index named IGS_PE_PASSPORT_IN_PK exists on the same column, serving as the surrogate identifier for each staged row. Heuristic Data Vault classification derived from the foreign-key structure indicates the object is standalone; there are no documented FK relationships to other tables. In Data Vault modeling terms, this object is best treated as a staging satellite—an inbound, transient artifact that captures descriptive passport attributes and processing metadata before integration into the core model.

Key Information Stored

The most significant columns fall into three groups: identity, business content, and process control.

• INTERFACE_PASSPORT_ID — surrogate primary key; uniquely identifies each staged row.
• INTERFACE_ID — correlates the row to its parent interface batch or run context.
• PASSPORT_NUMBER, PASSPORT_EXPIRY_DATE, PASSPORT_CNTRY_CODE — the core business attributes of the passport record being staged.
• MATCH_IND, STATUS, ERROR_CODE — validation and disposition indicators used by the import concurrent program.
• DUP_PASSPORT_ID — reference to a suspected duplicate passport record when a duplicate is detected.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program execution context.
• INTERFACE_RUN_ID — groups rows belonging to a single interface run.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard EBS DFF (descriptive flexfield) columns providing extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The sole business-key candidate is the surrogate INTERFACE_PASSPORT_ID; no natural-key unique constraint is documented beyond the PK.

Common Use Cases and Queries

The principal use case is diagnosing and monitoring passport data imports. A typical query identifies failed rows for remediation:

SELECT INTERFACE_PASSPORT_ID, PASSPORT_NUMBER, PASSPORT_CNTRY_CODE,
       STATUS, ERROR_CODE, DUP_PASSPORT_ID
FROM   IGS_PE_PASSPORT_INT
WHERE  STATUS = 'E'
AND    INTERFACE_RUN_ID = :run_id;

Another pattern checks for pending unprocessed rows prior to submission of the import program:

SELECT COUNT(*) FROM IGS_PE_PASSPORT_INT
WHERE  STATUS IS NULL OR STATUS = 'N';

Reporting scenarios frequently join staged rows to concurrent program metadata using REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to attribute failures to specific runs.

Related Objects

• IGS_PE_PASSPORT — the base production passport table to which validated interface rows are ultimately migrated.
• IGS_PE_PASSPORT_INT_PK — the primary key constraint/index on INTERFACE_PASSPORT_ID.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to reconcile import runs.
• FND_CONCURRENT_PROGRAMS / FND_APPLICATION — joined on PROGRAM_ID and PROGRAM_APPLICATION_ID.
• FND_FLEX_VALUES — related through ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 DFF usage.

No foreign keys are documented because the object is classified as standalone; all relationships above are logical rather than enforced.