Search Results level_of_qual_id




Overview
Explore in AI Chat

Overview

The view IGS_PE_PERSON_DTLS_V belongs to the Oracle EBS IGS — Student System product family, a module documented in ETRM as Obsolete. It exposes a consolidated, denormalized projection of person (party) detail records used throughout the Student System to present biographical, demographic, and identity attributes for both students and staff. The view is not a physical object; it is a read-only query construct intended for reporting, integration, and internal Student System logic. ETRM records the implementation status as "Not implemented in this database," indicating that in the documented environment the underlying dependency chain (notably the IGS_PE_* and FND_LOOKUP_VALUES objects) was either absent or the view was not deployed — a common circumstance for obsolete modules retained only for reference in 12.1.1 and 12.2.2.

Underlying Base Objects

The view text joins six sources. ETRM does not document a base-object list, so the dependencies are derived from the view DDL itself:

  • HZ_PARTIES P — the primary driving table (Oracle Trading Community / HZ party registry), supplying person name parts, party number, email, salutation, attributes, and audit columns.
  • IGS_PE_PERSON_BASE_V PP — a Student System base view carrying gender, birth date, and date of death.
  • IGS_PE_HZ_PARTIES PD — an outer-joined Student System table for student-specific flags (deceased, archive/purge, proof of insurance/immunization, military service, veteran, Oracle username, level of qualification).
  • FND_LOOKUP_VALUES LK — outer-joined lookup for HZ_GENDER meanings (application 222, security group 0, session language).
  • FND_LOOKUP_VALUES LK1 — outer-joined lookup resolving the pre-name adjunct code to a meaningful description.
  • IGS_PE_PERSON_ID_TYPE_V PIT — outer-joined identifier view exposing person ID type and API person ID.

The join conditions confirm PARTY_ID as the unifying key, with outer joins (+) preserving person rows lacking student or identifier detail.

Key Columns

Common Use Cases and Queries

Typical usage centres on person lookup and demographic reporting. A representative query retrieving adjunct meaning and gender is:

  • SELECT PERSON_ID, SURNAME, GIVEN_NAMES, PRE_NAME_ADJUNCT, PRE_NAME_ADJUNCT_MEANING, SEX_MEANING FROM IGS_PE_PERSON_DTLS_V WHERE PRE_NAME_ADJUNCT_MEANING IS NOT NULL;
  • Student roster extracts joining on PERSON_ID to enrolment tables.
  • Staff/encumbrance checks leveraging STAFF_MEMBER_IND and ENCUMBERED_IND.

Because the module is obsolete, references should be migrated to supported HZ_PARTIES-based views in current releases.