Results for “igs_az_students”

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

Overview

IGS_AZ_STUDENTS is a table within the Oracle E-Business Suite Student System (IGS) module, which is classified as obsolete in the ETRM documentation. The table stores student details associated with the various Advising Groups maintained in the system. In the broader IGS data model, it functions as the junction between a student person record and an advising group, carrying both membership attributes and hold-related tracking columns. The IGS product line supported higher-education institutions, and advising group management was one of its administrative features; this table is therefore legacy metadata rather than an actively implemented object.

Per the ETRM record, the table is marked "Not implemented in this database," meaning it should not be expected to exist in a standard 12.1.1 or 12.2.2 installation unless the Advising Groups feature or a custom extension created it. The documented schema identifies an owner of IGS and a total of 15 columns. Based on the foreign-key topology, the heuristic Data Vault classification is satellite-leaning: the table appears to hold descriptive, time-stamped attributes attached to a business key rather than acting as a pure hub or link.

Key Information Stored

The primary key is IGS_AZ_STUDENTS_PK, defined on the surrogate column GROUP_STUDENT_ID, which uniquely identifies each advising-group student row. Two unique indexes serve as business-key candidates: IGS_AZ_STUDENTS_PK on GROUP_STUDENT_ID, and IGS_AZ_STUDENTS_U1 on the composite of GROUP_NAME, STUDENT_PERSON_ID, and START_DATE, indicating that a student may belong to the same advising group across distinct start dates.

• GROUP_STUDENT_ID — surrogate primary key and the column referenced by dependent tables.
• GROUP_NAME — the advising group to which the student is assigned; part of the composite business key.
• STUDENT_PERSON_ID — the student's person identifier, also part of the business key and the FK to IGS_PE_PERS_ENCUMB.
• START_DATE / END_DATE — effective dating for the group membership.
• ADVISING_HOLD_TYPE — the type of advising hold applied to the student record.
• HOLD_START_DATE — when the advising hold takes effect, paired with the hold type.
• NOTIFIED_DATE — when the student was notified of the group assignment or hold.
• ACCEPT_ADD_FLAG / ACCEPT_DELETE_FLAG — indicators of acceptance for addition or deletion from the advising group.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Because the object is obsolete and unimplemented, queries are typically investigative or migration-oriented rather than operational. A basic retrieval by student returns group memberships with effective dates:

SELECT group_student_id, group_name, student_person_id, start_date, end_date FROM igs_az_students WHERE student_person_id = :person_id ORDER BY start_date;

A join to the hold-related FK clarifies advising holds per group:

SELECT s.group_name, s.advising_hold_type, s.hold_start_date FROM igs_az_students s, igs_pe_pers_encumb e WHERE s.student_person_id = e.person_id;

To trace advising relationships that reference this table, join through the dependent IGS_AZ_ADVISING_RELS on GROUP_STUDENT_ID. Reporting scenarios include identifying students with active holds, verifying group membership effective dates, and reconciling who was notified and when.

Related Objects

The foreign-key documentation defines the table's immediate neighborhood:

• IGS_AZ_ADVISING_RELS.GROUP_STUDENT_ID → IGS_AZ_STUDENTS — the primary referencing relationship; advising relationship rows point back to this table via the surrogate key.
• IGS_AZ_STUDENTS.STUDENT_PERSON_ID → IGS_PE_PERS_ENCUMB — the outbound FK linking the student person to encumbrance/hold data; the metadata also documents ADVISING_HOLD_TYPE and HOLD_START_DATE involvement in this relationship.

Additional IGS advising and person objects may join indirectly through STUDENT_PERSON_ID or GROUP_STUDENT_ID, but the documented FK data above establishes the primary dependency chain for this obsolete Student System table.