Search Results accept_add_flag




Overview
Explore in AI Chat

Overview

APPS.IGSBV_ADVISING_STUDENTS is a read-only Oracle EBS view within the Student System (IGS) product family. It exposes advising group enrollment data, associating a student (identified by STUDENT_PERSON_ID) with an advising group and its associated advising holds. In effect, the view presents the roster of students assigned to advising groups, together with the lifecycle and hold characteristics of each assignment.

The view is defined with a WITH READ ONLY clause, meaning it cannot be used as the target of DML. This signals that it is intended purely for querying, reporting, and integration extraction. Within an Oracle EBS 12.1.1 or 12.2.2 environment, a technical or functional consultant would use this view to surface advising-group membership without needing to touch the underlying table directly, and third-party or custom reporting layers can depend on its stable column set. Because the search term of interest is student_person_id, this view is a primary source for linking an advising group to a person record in the Oracle human resources/person model.

Underlying Base Objects

ETRM documentation records no separately documented base objects for this view; the view text itself reveals the source. The view is defined as:

Accordingly, the effective base object is the table IGS_AZ_STUDENTS. The view is a thin projection over that table — it introduces no joins, calculations, or filters in the documented definition. Practically, this makes IGSBV_ADVISING_STUDENTS a controlled read surface over the underlying student/group assignment table, insulating consumers from direct table access while preserving the column semantics of the base table.

Key Columns

  • STUDENT_PERSON_ID — The person identifier for the advised student, allowing joins to person and party tables. This is the column the user searched for.
  • GROUP_STUDENT_ID — Surrogate identifier for a single student-to-advising-group assignment row.
  • GROUP_NAME — The advising group to which the student belongs.
  • START_DATE / END_DATE — The effective date range of the student's advising-group membership.
  • ADVISING_HOLD_TYPE — The type of advising hold applied to the assignment.
  • HOLD_START_DATE — The date the advising hold became effective.
  • NOTIFIED_DATE — The date the student was notified of the hold.
  • ACCEPT_ADD_FLAG / ACCEPT_DELETE_FLAG — Flags indicating whether additions or deletions are accepted for the assignment.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE provide standard EBS who/when tracking.

Common Use Cases and Queries

Typical scenarios include producing advising-group rosters, reconciling students against advising holds, and feeding downstream integration extracts keyed by person identifier. Because the view is read-only, it is well suited to BI Publisher reports and interfaces.

To retrieve all advising assignments for a specific person:

SELECT group_student_id, group_name, student_person_id, start_date, end_date, advising_hold_type, hold_start_date FROM apps.igsbv_advising_students WHERE student_person_id = :p_person_id;

To list active advising holds as of today:

SELECT student_person_id, group_name, advising_hold_type, hold_start_date FROM apps.igsbv_advising_students WHERE advising_hold_type IS NOT NULL AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);

To join to the person record, use STUDENT_PERSON_ID as the correlation key to person/party tables. Consultants should confirm the actual base table name and access privileges in their instance, since the metadata documents IGS_AZ_STUDENTS as the sole source object.