Results for “igs_pe_alt_pers_id”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_PE_ALT_PERS_ID is a Student System table in Oracle E-Business Suite that stores the alternate identifiers by which a person is known. The table belongs to the obsolete IGS product family and is documented in ETRM 12.1.1 with an owner of IGS and a physical schema of 37 columns. The entity carries identifiers such as an OLAA id, a VTAC id, or a superseded legacy id, and is therefore best understood as a secondary identity registry for a party rather than a master party record. The ETRM metadata explicitly records "Not implemented in this database" for this object, which indicates the table is not instantiated in every environment and may be absent or unpopulated in a given 12.1.1 or 12.2.2 instance.

Based on the foreign key structure and the presence of a composite primary key containing both a parent reference and an effective-dated attribute, the heuristic Data Vault classification for this object is link. Under this modeling suggestion, IGS_PE_ALT_PERS_ID functions as an associative structure connecting a party to an identifier type across a validity period, rather than as a standalone hub of the party or of the identifier type.

Key Information Stored

The table is defined by a composite primary key, IGS_PE_ALT_PERS_ID_PK, spanning PE_PERSON_ID, API_PERSON_ID, PERSON_ID_TYPE, and START_DT. The unique index IGS_PE_ALT_PERS_ID_U1 carries the identical column set, so no separate business-key candidate beyond the primary key is documented.

Common Use Cases and Queries

The principal use case is identity reconciliation: resolving an external identifier value, such as an OLAA or VTAC reference, back to an HZ_PARTIES record. A representative query joins the alternate-id table to the person record and to the type lookup, filtering on a specific identifier value:

  • SELECT a.PE_PERSON_ID, a.API_PERSON_ID, a.PERSON_ID_TYPE, a.START_DT, a.END_DT FROM IGS_PE_ALT_PERS_ID a WHERE a.API_PERSON_ID = :id_value AND (a.END_DT IS NULL OR a.END_DT > SYSDATE);
  • Reporting the set of alternate ids held per person, joined through HZ_PARTIES for demographics.
  • Joining to IGS_PE_PERSON_ID_TYP to group records by identifier category for reconciliation and migration extracts.
  • Effective-dated filtering using START_DT and END_DT to return only currently valid identifiers.

Related Objects

The documented foreign keys establish the core relationships for this table.

  • HZ_PARTIES — joined on IGS_PE_ALT_PERS_ID.PE_PERSON_ID = HZ_PARTIES.PARTY_ID; the master party record.
  • IGS_PE_PERSON_ID_TYP — joined on IGS_PE_ALT_PERS_ID.PERSON_ID_TYPE = IGS_PE_PERSON_ID_TYP.PERSON_ID_TYPE; the identifier-type lookup.
  • The primary key IGS_PE_ALT_PERS_ID_PK and unique index IGS_PE_ALT_PERS_ID_U1 depend on the same four columns.
  • Standard concurrent-program and DFF audit structures referenced through PROGRAM_ID, REQUEST_ID, and the ATTRIBUTE* columns support integration with the EBS concurrent manager and descriptive flexfield frameworks.

Because the object is documented as obsolete and not implemented in every database, integration and reporting designs should verify table presence at runtime before depending on it.