Results for “igsbv_advising_relations”

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

Overview

IGSBV_ADVISING_RELATIONS is a read-only view owned by the APPS schema within the Oracle E-Business Suite Student System (IGS) product family. It exposes student-to-advisor relationships maintained across the various advising groups defined in the institution's advising configuration. The view presents a flattened, reporting-friendly representation of the underlying advising relationship records, combining group identification, advisor identification, student identification, and the effective date range for each pairing.

In Oracle EBS 12.1.1 and 12.2.2, institutional advising data is organized around advising groups, each of which associates a named group with a specific advisor and a specific student. IGSBV_ADVISING_RELATIONS surfaces those combinations directly, making it suitable for reporting, integration extracts, and downstream analytics without requiring consumers to navigate the full relational structure of the base tables. Because the view is defined WITH READ ONLY, it is intended strictly for query access; no inserts, updates, or deletes may be issued against it.

Underlying Base Objects

Per the ETRM-documented view text, IGSBV_ADVISING_RELATIONS is defined over a single base object: IGS_AZ_ADVISING_RELS (aliased as AZR). The view performs a direct column projection from that table with no joins, unions, or aggregations, which means every row returned corresponds one-to-one with a row in the base advising relationships table. The ETRM metadata for the 12.2.2 release notes no additional documented base objects, and the view definition confirms this: the only referenced source is the advising relationships table itself.

Because the view adds no transformation logic, it inherits the base table's data integrity characteristics and any row-level security or filtering applied at the table level. Institutions that need to trace an advising relationship back to its origin should query IGS_AZ_ADVISING_RELS directly.

Key Columns

The view exposes ten columns, several of which are named differently from their base table counterparts to present business-friendly identifiers:

• GROUP_ADVISING_REL_IDENTIFIER — The unique system identifier for the advising relationship record. These are numeric primary keys generated on creation.
• GROUP_NAME — The name of the advising group to which the relationship belongs.
• GROUP_ADVISOR_IDENTIFIER — The identifier of the advisor assigned within the group.
• GROUP_STUDENT_IDENTIFIER — The identifier of the student assigned within the group. This is the column most relevant to searches for group_student_identifier.
• START_DATE and END_DATE — The effective date range during which the advising relationship is active. End dates may be null for open-ended relationships.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns recording the user and timestamp of record creation and last modification.

Common Use Cases and Queries

Typical uses include advising load reports, caseload analysis per advisor, and student roster extracts. To retrieve all relationships for a specific student:

• SELECT group_name, group_advisor_identifier, start_date, end_date FROM igsbv_advising_relations WHERE group_student_identifier = :student_id;

To list active student-advisor pairs as of the current date:

• SELECT group_name, group_advisor_identifier, group_student_identifier FROM igsbv_advising_relations WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));

To count students per advising group:

• SELECT group_name, COUNT(group_student_identifier) FROM igsbv_advising_relations GROUP BY group_name;

Because the view is read-only and directly mirrors its base table, query performance is generally equivalent to querying IGS_AZ_ADVISING_RELS, and results should be treated as current with respect to that table.