Search Results ncc_version_number




Overview
Explore in AI Chat

Overview

IGS_PE_TYP_INSTANCES is a VALID view owned by the APPS schema within the IGS – Student System product (Oracle EBS 12.1.1 / 12.2.2). It presents a consolidated picture of person type instances — the assignment of a person type code to a person or party within a given organization, optionally linked to an admissions funnel context. The view is designed to unify two distinct data sources: legacy person type instance records stored with an organization identifier and course/funnel attributes, and active person type usages sourced from the human resources person type usage model. This union allows downstream student system reporting and integration processes to consume both native student records and HR-derived person type usages through a single interface.

Underlying Base Objects

The view is defined by a UNION ALL over two distinct source sets:

ETRM documents no referenced base objects for this view in its 12.2.2 metadata, but the view text above establishes the definitive dependency set. Because the second branch reads a date-effective HR table filtered on the current system date, query results vary over time and are sensitive to the application session date.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing all person type instances for an organization, reconciling IGS-native instances against HR person type usages, and driving student status or funnel reporting. A representative query lists native and derived instances for a person:

  • SELECT type_instance_id, person_type_code, person_id, start_date, end_date, system_type FROM igs_pe_typ_instances WHERE person_id = :p_person_id;
  • SELECT org_id, person_type_code, COUNT(*) FROM igs_pe_typ_instances WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date AND end_date GROUP BY org_id, person_type_code;
  • SELECT person_type_code, course_cd, funnel_status FROM igs_pe_typ_instances WHERE admission_appl_number IS NOT NULL;

Because the HR branch is date-dependent, queries should always restrict on START_DATE and END_DATE when a point-in-time result is required.