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.
PE_PERSON_ID— the person for whom the alternate id is recorded; a foreign key toHZ_PARTIES.API_PERSON_ID— the alternate identifier value itself, forming part of the primary key.PERSON_ID_TYPE— the classification of the alternate id; a foreign key toIGS_PE_PERSON_ID_TYP.START_DT— the effective start date of the alternate id; part of the primary key.END_DT— the effective end date, supporting temporal (effective-dated) tracking.API_PERSON_ID_UFandREGION_CD— descriptive qualifiers captured on the identifier record.CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN— standard who-columns.REQUEST_ID,PROGRAM_APPLICATION_ID,PROGRAM_ID,PROGRAM_UPDATE_DATE— concurrent program audit context.ATTRIBUTE_CATEGORYandATTRIBUTE1throughATTRIBUTE20— the standard DFF descriptor flexfield columns.
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_PARTIESfor demographics. - Joining to
IGS_PE_PERSON_ID_TYPto group records by identifier category for reconciliation and migration extracts. - Effective-dated filtering using
START_DTandEND_DTto return only currently valid identifiers.
Related Objects
The documented foreign keys establish the core relationships for this table.
HZ_PARTIES— joined onIGS_PE_ALT_PERS_ID.PE_PERSON_ID = HZ_PARTIES.PARTY_ID; the master party record.IGS_PE_PERSON_ID_TYP— joined onIGS_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_PKand unique indexIGS_PE_ALT_PERS_ID_U1depend on the same four columns. - Standard concurrent-program and DFF audit structures referenced through
PROGRAM_ID,REQUEST_ID, and theATTRIBUTE*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.
-
This entity describes the other ids by which a person is known. eg. OLAA id, VTAC id, old id.
-
Table: IGS_PE_ALT_PERS_ID 12.2.2
This entity describes the other ids by which a person is known. eg. OLAA id, VTAC id, old id.
Not implemented in this database·Explore IGS module →