Results for “create_method”

4 results




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

Overview

IGS_PE_TYP_INSTANCES_ALL is a core table in the Oracle EBS Student System (IGS) product family. It stores the individual person type instances assigned to a person record, allowing the same individual to simultaneously or sequentially hold multiple institutional roles such as applicant, student, prospect, alumnus, or staff member. Each row represents one distinct person type instance, identified by a surrogate key and qualified by type code, effective dating, and optional admissions or course context.

Given its foreign key structure — referencing HZ_PARTIES and IGS_AD_PS_APPL_INST_ALL through PERSON_ID and IGS_PE_PERSON_TYPES through PERSON_TYPE_CODE — the ETRM heuristic Data Vault classification is a link table. It resolves many-to-many relationships between parties, person type definitions, and admission or course entities rather than acting as a pure hub or satellite.

Key Information Stored

The table contains 22 documented columns. The most significant are:

Common Use Cases and Queries

Typical reporting scenarios include identifying all current students, finding applicants and their funnel status, and auditing historical person type assignments. Because the table is effective-dated, queries frequently filter on START_DATE and END_DATE to isolate active instances.

A representative query returning all active person type instances for a given party:

  • SELECT t.TYPE_INSTANCE_ID, t.PERSON_TYPE_CODE, p.PERSON_TYPE_NAME, t.START_DATE, t.END_DATE FROM IGS_PE_TYP_INSTANCES_ALL t, IGS_PE_PERSON_TYPES p WHERE t.PERSON_TYPE_CODE = p.PERSON_TYPE_CODE AND t.PERSON_ID = :person_id AND NVL(t.END_DATE, SYSDATE) >= SYSDATE AND t.ORG_ID = :org_id;

For funnel reporting, joining to admission applications via ADMISSION_APPL_NUMBER and SEQUENCE_NUMBER allows counts of applicants by FUNNEL_STATUS. For student rosters, joining to IGS_PS_VER_ALL on COURSE_CD and CC_VERSION_NUMBER narrows results to a specific course version. Multi-organization deployments must consistently bind ORG_ID to enforce operating unit security.

Related Objects

The following objects are most directly associated with IGS_PE_TYP_INSTANCES_ALL through documented foreign keys or reciprocal dependencies:

  • HZ_PARTIES — joined via PERSON_ID; the master party record for the individual.
  • IGS_PE_PERSON_TYPES — joined via PERSON_TYPE_CODE; defines each available person type.
  • IGS_AD_PS_APPL_INST_ALL — joined via PERSON_ID, ADMISSION_APPL_NUMBER, NOMINATED_COURSE_CD, and SEQUENCE_NUMBER; the admission application instance.
  • IGS_PS_VER_ALL — joined via COURSE_CD and CC_VERSION_NUMBER; the course version definition.
  • IGS_PE_TYP_INSTANCES_U1 — the unique index on TYPE_INSTANCE_ID, confirming the business key.
  • IGS_PE_TYPE_INSTANCES_PK — the primary key constraint governing the surrogate identifier.

These relationships establish the table as the central linkage between party identity, person type classification, admissions processing, and course context within the IGS Student System.