Search Results igs_pe_stat_v




Overview

IGS_PE_STAT_V is a reporting view within the Oracle E-Business Suite IGS (Student System) product family. IGS was the legacy Oracle Student System module, and it is documented in ETRM as Obsolete — meaning it is no longer actively supported or implemented in current 12.1.1 / 12.2.2 environments. The view presents a consolidated, denormalized snapshot of student personal and statistical data, joining person-level identifiers with profile-level demographic, socio-economic, and academic-calendar attributes.

Its role is primarily read-only reporting and integration: it flattens the underlying person, person-profile, and student-detail records so that downstream reports, extracts, and interfaces can retrieve a student's biographical and enrollment-context attributes through a single query rather than multiple joins. The ETRM metadata records the view as "Not implemented in this database," confirming that in the reference 12.2.2 environment the object is documented but absent from the data dictionary.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view. The view text, however, reveals the aliased source tables used in its definition:

  • P — the person/party table supplying ROW_ID, PERSON_ID, and PERSON_NUMBER.
  • PP — the person-profile table supplying PERSON_PROFILE_ID, effective dates, ethnicity, marital status, internal flag, household size and income, and place of birth.
  • SD — the student-detail table supplying religion, next-of-kin, socio-economic and further-education codes, tuition attributes, the several calendar/sequence number pairs, and the WHO columns and ATTRIBUTE1–20 flexfield segments.
  • LK1, LK2, LK3, CC2, CC4, CC5 — lookup and code tables that resolve stored codes into descriptive meanings.

Because these joins are not enumerated in the ETRM metadata, they must be treated as inferred from the supplied view text rather than as formally documented dependencies.

Key Columns

The view exposes identity, demographic, academic, and audit columns. Notable examples include:

Common Use Cases and Queries

Typical use cases include student demographic reporting, tuition/residency analysis, and data extracts for external systems. Because the object is obsolete and absent from the database, queries are documented for historical reference only:

  • Retrieving a student's initial program term by sequence number:
    SELECT person_number, init_cal_type, init_sequence_number FROM igs_pe_stat_v WHERE person_id = :p_id;
  • Listing socio-economic bands resolved to descriptions:
    SELECT person_number, socio_eco_status_desc, ann_family_income FROM igs_pe_stat_v;
  • Filtering current profiles by effective dates and internal flag.

Analysts migrating from IGS to successor products should map INIT_SEQUENCE_NUMBER and the related calendar/sequence pairs to equivalent term-enrollment attributes in the target model.