Results for “igs_pe_stat_details”

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

Overview

IGS_PE_STAT_DETAILS is a table in the Oracle E-Business Suite Student System (IGS) product family. The entity is documented as describing the statistics details of a person, meaning it stores a consolidated set of demographic, socioeconomic, and academic-status attributes associated with an individual tracked by the student system. The product module IGS is flagged as obsolete in the ETRM documentation for release 12.1.1/12.2.2, and the documented implementation note states that the table is not implemented in this database. As a result, IGS_PE_STAT_DETAILS exists as a documented metadata artifact rather than an active operational object in a stock 12.1.1 or 12.2.2 environment.

Based on the foreign key topology mined from the metadata, the heuristic Data Vault classification for this table is link. This reflects a modeling suggestion: the table sits between the person and person-profile hubs while also referencing multiple calendar-instance records, making it a relationship-bearing object rather than a pure descriptive satellite or a standalone hub.

Key Information Stored

The documented schema contains 59 columns under owner IGS. The primary key is defined as IGS_PE_STAT_DETAILS_PK on PERSON_ID, and a separate key, PERSON_PROFILE_ID_PK, is defined on PERSON_PROFILE_ID. A unique index, IGS_PE_STAT_DETAILS_U1, exists on PERSON_ID, identifying PERSON_ID as the business-key candidate. The most significant columns include:

• PERSON_ID — surrogate/primary key column identifying the person; foreign key to HZ_PARTIES.
• PERSON_PROFILE_ID — link to HZ_PERSON_PROFILES; carries its own documented key.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range governing the validity of the statistical record.
• RELIGION_ID, FURTHER_EDUCATION_ID, SOCIO_ECO_ID, RESID_STAT_ID — coded lookups for religion, prior education, socioeconomic status, and residency status.
• RELIGION_CD, FURTHER_EDUCATION_CD, SOCIO_ECO_CD, BIRTH_CNTRY_RESN_CODE — denormalized descriptive codes accompanying the lookup identifiers.
• CRIMINAL_CONVICT, ACAD_DISMISSAL, NON_ACAD_DISMISSAL — disciplinary and status flags.
• COUNTRY_CD3, STATE_OF_RESIDENCE, IN_STATE_TUITION, TUITION_ST_DATE, TUITION_END_DATE — residency and tuition-classification attributes.
• NEXT_TO_KIN — next-of-kin indicator.
• MATR_CAL_TYPE/MATR_SEQUENCE_NUMBER, INIT_CAL_TYPE/INIT_SEQUENCE_NUMBER, RECENT_CAL_TYPE/RECENT_SEQUENCE_NUMBER, CATALOG_CAL_TYPE/CATALOG_SEQUENCE_NUMBER — compound calendar references.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus REQUEST_ID and PROGRAM_APPLICATION_ID/PROGRAM_ID/PROGRAM_UPDATE_DATE, and ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE20 (flexfield support).

Common Use Cases and Queries

Because the table is obsolete and not implemented, live querying is not expected. Where legacy or migrated data exists, typical reporting scenarios include residency and tuition classification, socioeconomic and disciplinary profiling, and person-profile consolidation. A representative join pattern follows:

• Join to HZ_PARTIES on s.PERSON_ID = p.PARTY_ID to retrieve party identity.
• Join to HZ_PERSON_PROFILES on s.PERSON_PROFILE_ID = pr.PERSON_PROFILE_ID.
• Join to IGS_CA_INST_ALL four times on the calendar/sequence pairs (MATR_, INIT_, RECENT_, CATALOG_) to resolve calendar instances.
• Filter by EFFECTIVE_START_DATE/EFFECTIVE_END_DATE and by REQUEST_ID for concurrent-program provenance.

A sample pattern: SELECT s.person_id, s.in_state_tuition, s.resid_stat_id FROM igs_pe_stat_details s WHERE SYSDATE BETWEEN s.effective_start_date AND s.effective_end_date;

Related Objects

The most significant related objects, drawn from the documented foreign key relationships, are:

• HZ_PARTIES — referenced via IGS_PE_STAT_DETAILS.PERSON_ID.
• HZ_PERSON_PROFILES — referenced via IGS_PE_STAT_DETAILS.PERSON_PROFILE_ID.
• IGS_CA_INST_ALL — referenced four times via the MATR_, INIT_, RECENT_, and CATALOG_ calendar type/sequence pairs.

These relationships confirm the link-style role of IGS_PE_STAT_DETAILS, bridging party and profile entities to multiple calendar-instance records.