Search Results igs_pe_eit_int

Overview

IGS_PE_EIT_INT is the inbound interface (staging) table for person extra information in the Oracle E-Business Suite Student System (IGS) product family. It resides in the IGS schema and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. The table exists to hold person extra information records — attributes such as Country of Physical Residence, State of Residence, and Citizenship/Residency Status — prior to their validation and transfer into the permanent destination table IGS_PE_EIT.

Functionally, the table is a transient landing area for data originating from external sources (legacy conversions, third-party integrations, or batch loads) that must be subjected to EBS validation rules before becoming authoritative person records. Rows are inserted by an import or conversion process, evaluated for matching and duplication against existing person extra information, marked with a processing status, and then either pushed forward into IGS_PE_EIT or flagged with an error for remediation.

Under a heuristic Data Vault classification, the table is modeled as standalone — that is, it does not exhibit the foreign-key fan-in or fan-out patterns that would place it as a hub, link, or satellite. This reflects its nature as a self-contained staging entity keyed by a surrogate identifier rather than as a component of the integrated person model.

Key Information Stored

The table is documented with 24 columns. The most significant of these are:

• INTERFACE_EIT_ID — the surrogate primary key, defined by the unique index IGS_PE_EIT_INT_PK (and additionally IGS_PE_EIT_INT_U1). This is the technical identity of each staging row; because IGS_PE_EIT_INT_U1 is also a unique index over this column, INTERFACE_EIT_ID serves as both the surrogate and documented business-key candidate.
• INTERFACE_ID — the identifier linking the row back to a parent interface or batch context.
• INTERFACE_RUN_ID — the specific interface execution that loaded the row, enabling run-level auditing.
• INFORMATION_TYPE — the category of extra information being imported, governing how the PEI_INFORMATIONn fields are interpreted.
• PEI_INFORMATION1 through PEI_INFORMATION5 — the five generic, position-based attribute slots that hold the actual values (for example, residence country, state, or residency status) according to the INFORMATION_TYPE.
• START_DATE / END_DATE — the effective date range of the extra information record.
• MATCH_IND — indicates whether the staged row matched an existing person extra information record.
• STATUS / ERROR_CODE — the processing outcome of the row and, when applicable, the validation failure reason.
• DUP_PE_EIT_ID — the identifier of the existing IGS_PE_EIT row identified as a duplicate.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — standard concurrent program tracking columns identifying the job that processed the row.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting an import of person extra information. Operators query the table by request to determine how many rows succeeded, failed, or matched duplicates.

• Error triage: SELECT INTERFACE_EIT_ID, INFORMATION_TYPE, STATUS, ERROR_CODE FROM IGS_PE_EIT_INT WHERE STATUS = 'ERROR';
• Run-level reconciliation: SELECT STATUS, COUNT(*) FROM IGS_PE_EIT_INT WHERE INTERFACE_RUN_ID = :run_id GROUP BY STATUS;
• Duplicate investigation: SELECT INTERFACE_EIT_ID, DUP_PE_EIT_ID, PEI_INFORMATION1 FROM IGS_PE_EIT_INT WHERE MATCH_IND = 'Y';
• Value inspection by type: SELECT INFORMATION_TYPE, PEI_INFORMATION1, PEI_INFORMATION2 FROM IGS_PE_EIT_INT WHERE REQUEST_ID = :request_id;
• Stale-row cleanup: SELECT COUNT(*) FROM IGS_PE_EIT_INT WHERE CREATION_DATE < SYSDATE - 30;

Because the table is a staging area, high row counts are normal and rows are typically purged or truncated once successfully imported into the destination table.

Related Objects

The most significant related objects are those that feed, validate, or consume this interface table.

• IGS_PE_EIT — the destination table into which validated rows are imported; the relationship is logical rather than enforced by a foreign key.
• IGS_PE_EIT_INT_PK / IGS_PE_EIT_INT_U1 — the primary and unique constraints enforcing row identity on INTERFACE_EIT_ID.
• Concurrent programs under FND_REQUEST / FND_CONCURRENT_REQUESTS — joined via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to identify the load job.
• Interface run tracking tables — referenced through INTERFACE_RUN_ID and INTERFACE_ID to associate rows with their parent batch.
• IGS person / person-extra-information setup tables — supply the valid INFORMATION_TYPE and value lookups against which staged rows are validated.

No foreign-key relationships are documented for this object, consistent with its standalone Data Vault classification and its role as a self-contained staging entity within the IGS Student System.