Results for “igs_pe_person_alias”

50+ results




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

Overview

IGS_PE_PERSON_ALIAS is a transactional table in the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Per the ETRM metadata, this entity describes aliases by which a person may be known — alternate surnames, given names, titles, or professional names recorded against a learner, applicant, or staff member. It is the person-level name-alias repository within the Student System's Person/Entity (PE) data model, allowing multiple historical or concurrent name forms to be retained against a single party record without overwriting the authoritative name held in the trading community model.

The heuristic Data Vault classification mined from the foreign-key structure is link. As a modeling suggestion, this reflects that the table's principal role is to associate a person party with alias attributes across time, rather than acting as a standalone hub of core identity or a pure descriptive satellite. Analysts building a Data Vault representation should treat it as an associative construct between the person hub and the alias detail it carries.

Key Information Stored

The table comprises 14 documented columns. The most operationally significant are:

  • PERSON_ID — Party identifier for the person whose alias is recorded; part of the composite primary key and the column that joins back to HZ_PARTIES.
  • SEQUENCE_NUMBER — Ordinal that distinguishes multiple aliases for the same person; the second component of the primary key.
  • ALIAS_TYPE — Classification of the alias (for example, an alternate surname or professional name category).
  • START_DT and END_DT — Effective date range during which the alias applies, enabling temporal (point-in-time) reconstruction of a person's known names.
  • SURNAME and GIVEN_NAMES — The alias name components themselves.
  • TITLE — Honorific or title associated with the alias.
  • ALIAS_COMMENT — Free-text annotation describing or qualifying the alias.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last changed each row.

The surrogate primary key is IGS_PE_PERSON_ALIAS_PK (PERSON_ID, SEQUENCE_NUMBER). A unique index, IGS_PE_PERSON_ALIAS_U1, covers the same column pair, making (PERSON_ID, SEQUENCE_NUMBER) the documented business-key candidate. Because the primary key is composite and the unique index is redundant with it, SEQUENCE_NUMBER must be generated per person to guarantee uniqueness.

Common Use Cases and Queries

Typical applications include name-change auditing, applicant-name matching during admissions, and reconciliation of legacy name spellings against the HZ_PARTIES master record.

  • Retrieve all current aliases for a person:
    SELECT PERSON_ID, SEQUENCE_NUMBER, ALIAS_TYPE,
           SURNAME, GIVEN_NAMES, TITLE
      FROM   IGS_PE_PERSON_ALIAS
     WHERE  PERSON_ID = :person_id
       AND  (END_DT IS NULL OR END_DT >= SYSDATE);
  • Point-in-time name lookup using the effective-dating columns (START_DT, END_DT) to reconstruct what a person was known as on a given date.
  • Audit reporting against the LAST_UPDATE_DATE / LAST_UPDATED_BY columns to detect recently modified aliases.
  • Reconciliation joins between alias records and the authoritative name on HZ_PARTIES to flag mismatched or stale entries.

Related Objects

The documented foreign-key relationships point the table's PERSON_ID column to HZ_PARTIES (recorded twice in the ETRM relationship data). The most significant related objects are:

  • HZ_PARTIES — joined on IGS_PE_PERSON_ALIAS.PERSON_ID = HZ_PARTIES.PARTY_ID; the master party record supplying the primary name.
  • HZ_PERSON_PROFILES — person-profile extension of the party model, joined via PARTY_ID.
  • IGS_PE_PERSON_BASE_V / IGS_PE_PERSON_V — person views in the IGS PE layer that surface alias data alongside other person attributes.
  • IGS_PE_PERSON_NAME — sibling name entity in the same PE model, complementing the alias records.
  • Other IGS person-related tables keyed on PERSON_ID, which depend on the same party identifier used here.

Because all joins flow through PERSON_ID to HZ_PARTIES, any integration or extract that consumes IGS_PE_PERSON_ALIAS must preserve the party identifier to maintain referential integrity with the trading community model.