Search Results igs_pe_person_base_v




Overview
Explore in AI Chat

Overview

The IGS_PE_PERSON_BASE_V view is a dictionary object owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the IGS product family, which constitutes the Student System module of EBS. As its description states, this view is a "Person Base View to hold basic person information," designed to present a denormalized, secure, and reporting-friendly projection of the core person records stored in the Trading Community Architecture (TCA) tables.

In Oracle EBS 12.1.1 and 12.2.2, the Student System relies extensively on TCA for identity management. Rather than querying HZ_PARTIES and HZ_PERSON_PROFILES independently — and handling the effective-dating logic manually — developers and report writers use IGS_PE_PERSON_BASE_V to retrieve a consolidated, current view of an individual. This makes the view a foundational object for student biographical lookups, enrollment processing, and third-party integrations that require clean person data without navigating the complexity of TCA partitioning.

Underlying Base Objects

Although the ETRM metadata in this release associates no referenced base objects explicitly, the view definition itself is documented and resolves over two TCA entities. The primary source is HZ_PARTIES (aliased as P), which stores the top-level party record — the master identifier for any person or organization known to the application. The secondary source is HZ_PERSON_PROFILES (aliased as PP), which holds person-specific attributes that apply only to human parties, including date of birth, gender, and date of death.

The join condition links the two tables on PARTY_ID. Critically, the view filters person profiles using an effective-dating predicate: SYSDATE BETWEEN PP.EFFECTIVE_START_DATE AND NVL(PP.EFFECTIVE_END_DATE, SYSDATE). This ensures that only the currently active profile row for each party is returned, preventing duplication that would otherwise occur when a person's profile has been versioned over time. The view therefore inherits its referential integrity from TCA while encapsulating date-effective selection logic for the consumer.

Key Columns

The view exposes twenty-one columns that map person identity and profile attributes. Notable columns include:

Common Use Cases and Queries

Typical usage centers on biographical reporting and student identity lookups. A common pattern joins the view to student records in the Student System:

  • Producing enrollment rosters with current legal and preferred names.
  • Feeding downstream data warehouses or integrations with a single source of person data.
  • Validating demographic completeness prior to admissions or registration processing.
  • Supporting correspondence generation where addressable person details are required.

A representative query retrieves active person information for a given party:

SELECT person_id, person_number, full_name, known_as, birth_date, gender
FROM apps.igs_pe_person_base_v
WHERE person_id = :p_person_id;

Because the view applies effective dating internally, no additional date filtering is required by callers, which reduces the risk of returning stale or duplicate profile rows in dependent reports.