Results for “graduand_appr_status”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_GR_GRADUAND_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and delivered as part of the IGS — Student System product family, which covers the Oracle Student System (OSS) graduation and conferral functionality. The view consolidates graduand records — individuals eligible for or awarded an academic award — together with their ceremony allocation details, and exposes the result through a single denormalised result set suitable for concurrent programs, Oracle Reports outputs, OBIEE extracts, and integration interfaces operating in release 12.1.1 and 12.2.2.

The view is defined as a UNION of two queries. The first returns graduands held in IGS_GR_GRADUAND that have no corresponding ceremony allocation row; the second returns graduands that do have a matching row in IGS_GR_AWD_CRMN, supplying the ceremony-specific attributes. In the absence of a ceremony allocation, ceremony columns are populated with TO_NUMBER(NULL) so that the columns remain type-consistent across the union. Person name information is joined from HZ_PARTIES, the Trading Community Architecture (TCA) party table, rather than from a person-specific table, so the view depends on TCA being populated and on PERSON_ID being aligned with PARTY_ID.

The literal EXCLUDE_IND column — the term that drew the user to this object — is hard-coded as 'N' in both branches of the union. It is a presentation-layer flag, not a persisted attribute, and is therefore never sourced from a base table.

Underlying Base Objects

The documented definition references three base objects, all owned by APPS:

The distinguishing logic is the correlated NOT EXISTS sub-query against IGS_GR_AWD_CRMN. A graduand appearing in IGS_GR_GRADUAND for a given CREATE_DT with no ceremony allocation is returned from the first branch; a graduand with an allocation is returned from the second branch with ceremony detail. Because both branches can theoretically match on different key combinations, the union is not a strict partitioned union — a graduand may, in principle, appear twice if ceremony rows exist for more than one CREATE_DT relative to the graduand key.

Key Columns

  • PERSON_ID — internal identifier of the graduand, matching HZ_PARTIES.PARTY_ID.
  • PERSON_NUMBER — the TCA party number, the user-facing person identifier.
  • NAME — concatenated as PERSON_LAST_NAME || ', ' || PERSON_FIRST_NAME.
  • CREATE_DT — key date linking the graduand record to its ceremony allocation.
  • AWARD_CD, AWARD_COURSE_CD, AWARD_CRS_VERSION_NUMBER — the award and course/version context of the conferral.
  • GRD_CAL_TYPE, GRD_CI_SEQUENCE_NUMBER — graduation calendar type and calendar instance sequence.
  • CEREMONY_NUMBER, US_GROUP_NUMBER, ORDER_IN_PRESENTATION — ceremony seating/ordering attributes; NULL where no allocation exists.
  • GRADUAND_STATUS, GRADUAND_APPR_STATUS, S_GRADUAND_TYPE, PROXY_AWARD_IND — workflow and eligibility indicators.
  • EXCLUDE_IND — always literal 'N'; intended for downstream filtering, not derivable from the database.

Common Use Cases and Queries

Typical usage includes graduation ceremony invitation lists, eligibility extracts, and reconciliation of graduands lacking ceremony allocation.

  • List graduands with ceremony detail: SELECT person_number, name, ceremony_number, order_in_presentation FROM igs_gr_graduand_v WHERE ceremony_number IS NOT NULL;
  • Identify unallocated graduands: SELECT person_number, name, award_cd FROM igs_gr_graduand_v WHERE ceremony_number IS NULL;
  • Filter graduands by status: SELECT * FROM igs_gr_graduand_v WHERE graduand_status = :p_status AND exclude_ind = 'N';

Because EXCLUDE_IND is constant, filtering on it has no effect on the result set; exclusion logic must be applied in the consuming report or through the base tables.