Results for “advising_code”

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

Overview

The IGS_AZ_GROUPS_V view belongs to the IGS - Student System product family, which Oracle classifies as obsolete in the EBS 12.1.1 / 12.2.2 release set. The view exists to present the definition of an advising group in the self-service page used by students and advisors. Advising groups are the organizational construct that ties a responsible organization unit, a responsible person, a set of advisors, and a set of students together for the purpose of scheduling and tracking advising sessions. The view flattens the base group record and resolves several foreign keys into human-readable descriptions so the self-service layer does not need to perform those lookups itself.

The suffix "V" indicates this is a database view rather than a table, and the documentation for this particular object records it as "Not implemented in this database," meaning the definition is shipped in the application metadata but the view may not be instantiated in every environment. Its role is primarily read-only presentation and reporting; it supplies the columns that a self-service advising page or a concurrent report requires without exposing the caller to the underlying normalization.

Underlying Base Objects

The view is defined over a single base table, IGS_AZ_GROUPS, from which it selects the group columns and adds correlated subqueries and inline scalar lookups. The documented ETRM metadata records no referenced base objects other than this table, though the view text names several additional objects used in the scalar subqueries:

• HZ_PARTIES — joined with IGS_PE_HZ_PARTIES to derive the responsible organization unit description via PARTY_NAME, and used standalone to compose the responsible person's full name.
• IGS_PE_PERSID_GROUP — used twice to resolve ADVISOR_GROUP_ID and STUDENT_GROUP_ID into their group descriptions.
• IGS_LOOKUP_VALUES — used to resolve DELIVERY_METHOD_CODE against the lookup type IGS_AZ_DELIV_METHOD.

The ROWID of the base row is exposed as the first column of the view, which allows the self-service page to maintain a stable handle on each advising group row even though the view has no declared primary key of its own.

Key Columns

The most significant column for the user search term is ADVISING_CODE, the short business identifier that distinguishes one advising group from another. Alongside it, GROUP_NAME and GROUP_DESC provide the descriptive identity of the group. The responsibility context is captured by RESP_ORG_UNIT_CD and its resolved companion RESP_ORG_UNIT_DESC, together with RESP_PERSON_ID and RESP_PERSON_NAME, the latter composed as last name, first name, and middle name.

Operational behavior is controlled by DEFAULT_ADVISOR_LOAD_NUM, MANDATORY_FLAG, ADVISING_SESSIONS_NUM, ADVISING_HOLD_TYPE, and CLOSED_FLAG. The LOCATION_CD and DELIVERY_METHOD_CODE columns, with DELIVERY_METHOD_DESC resolved from the lookup, describe where and how advising is delivered. Membership is expressed through ADVISOR_GROUP_ID, STUDENT_GROUP_ID and their resolved descriptions. A set of AUTO_* flags (AUTO_REFRESH_FLAG, AUTO_STDNT_ADD_FLAG, AUTO_STDNT_REMOVE_FLAG, AUTO_ADVISOR_ADD_FLAG, AUTO_ADVISOR_REMOVE_FLAG, AUTO_MATCH_FLAG, AUTO_APPLY_HOLD_FLAG) drives automatic population and hold application, with LAST_AUTO_REFRESH_DATE recording the last execution. Twenty descriptive flexfield columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20) plus standard audit columns complete the row.

Common Use Cases and Queries

Typical usage is to list the advising groups available in self-service for a given organization unit, or to look up a group by its advising code. A simple listing query is:

• SELECT advising_code, group_name, resp_org_unit_desc, delivery_method_desc FROM igs_az_groups_v WHERE closed_flag = 'N' ORDER BY advising_code;
• SELECT group_name, advisor_group_desc, student_group_desc, advising_sessions_num FROM igs_az_groups_v WHERE advising_code = :p_advising_code;
• SELECT advising_code, resp_person_name, mandatory_flag, advising_hold_type FROM igs_az_groups_v WHERE resp_org_unit_cd = :p_org_unit;

Because the view resolves the descriptions inline, reports should reference the *_DESC columns rather than re-joining to HZ_PARTIES, IGS_PE_PERSID_GROUP, or IGS_LOOKUP_VALUES. Note that this product is obsolete; new development should confirm the object is implemented in the target database before relying on it.