Results for “group_student_identifier”

13 results




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

Overview

The IGSFV_ADVISING_RELATIONS view is a reporting and integration object belonging to the IGS — Student System product family in Oracle E-Business Suite. It presents advisor-to-student relationship data used by the advising functionality of the Student System, consolidating records that link advising groups, students, and advisors into a single denormalized result set. Within Oracle EBS 12.1.1 and 12.2.2, objects of this type are typically exposed for downstream reporting, integration, and inquiry purposes rather than for transactional maintenance.

The ETRM metadata explicitly records the implementation status as “Not implemented in this database,” and the owner and referenced base objects are listed as undocumented. This indication is significant: in 12.2.2 the view is classified under IGS - Student System (Obsolete). As a result, the view may be absent from a given environment, or may exist as a legacy remnant retained for backward compatibility. The view text is defined WITH READ ONLY, confirming its strictly read-only role.

Underlying Base Objects

Although the ETRM “Referenced base objects” field is empty, the documented view text shows that IGSFV_ADVISING_RELATIONS is defined over six tables joined by group name and surrogate identifiers:

  • IGS_AZ_ADVISING_RELS (aliased AZR) — the primary advising relationship table, supplying the relationship identifier, group name, advisor ID, student ID, and effective dates.
  • IGS_AZ_GROUPS (AZG) — provides the advising group description.
  • IGS_AZ_STUDENTS (AZS) — supplies the student’s person identifier.
  • IGS_AZ_ADVISORS (AZA) — supplies the advisor’s person identifier.
  • HZ_PARTIES (PE1) — resolves the student party to its party number.
  • HZ_PARTIES (PE2) — resolves the advisor party to its party number.

The joins are driven by GROUP_NAME in combination with the respective group-level identifiers, and the two HZ_PARTIES instances are joined on PARTY_ID = STUDENT_PERSON_ID and PARTY_ID = ADVISOR_PERSON_ID respectively.

Key Columns

Common Use Cases and Queries

Typical uses include identifying all students assigned to a given advisor, reconciling advising loads, and feeding downstream reporting. A representative query is:

SELECT advisor_person_id,
       advisor_person_number,
       student_person_id,
       student_person_number,
       group_name,
       start_date,
       end_date
FROM   igsfv_advising_relations
WHERE  advisor_person_id = :p_advisor_person_id
ORDER BY start_date;

Because the view is obsolete and may not be implemented, implementations should verify its existence before relying on it, and consider whether supported 12.2.x replacement objects should be used instead.