Results for “name_announced”

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

Overview

The view IGSBV_GR_CRMN_STDNT_PRG belongs to the Oracle E-Business Suite product family IGS – Student System, which is documented as obsolete within the ETRM repository. The object describes Graduand Ceremony Student Program information, presenting one row per graduand (graduating student) as that student is associated with a specific graduation ceremony, academic program, and award. It therefore acts as a reporting and integration surface for commencement and convocation processing, exposing the ceremonial, academic, and logistical attributes captured against each participant.

The view is designed for read-only consumption. Its defining query terminates with the WITH READ ONLY clause, confirming that it cannot be used to insert, update, or delete rows in the underlying student system data. It is intended for inquiry, reporting, and downstream extract or interface purposes rather than transactional maintenance. Notably, the ETRM implementation/DBA section states that the object is not implemented in this database, meaning the view is documented metadata rather than a physically deployed object in the referenced environment. Consumers should therefore verify deployment status within their own instance before relying on it for production reporting.

Underlying Base Objects

According to the documented view text, IGSBV_GR_CRMN_STDNT_PRG is defined over a two-table join. Although the ETRM metadata records no referenced base objects, the SQL definition explicitly cites:

• IGS_GR_AWD_CRMN (aliased GAC) — the principal graduation award ceremony table, supplying ceremony scheduling, award identification, seat allocation, regalia, and guest ticket attributes.
• HZ_PARTIES (aliased HP) — the Trading Community Architecture (TCA) party table, supplying the graduand's name and party number.

The join predicate is GAC.PERSON_ID = HP.PARTY_ID, linking each ceremony award record to the corresponding person in the TCA model. Because the join is an inner join, only graduands with a valid matching party row are returned. No other base tables are documented as contributing to the view.

Key Columns

The view exposes a broad set of columns. The attributes most relevant to the search term award_program_code and to ceremony reporting include:

• AWARD_PROGRAM_CODE — the program code associated with the graduand's award, derived from GAC.AWARD_COURSE_CD. This is the primary column a user searching "award_program_code" would target.
• AWARD_PROGRAM_VERSION_NUMBER — the version of the award program, from GAC.AWARD_CRS_VERSION_NUMBER.
• AWARD_CD — the specific award being conferred.
• PERSON_NAME and PERSON_NUMBER — graduand identification from HZ_PARTIES.
• GRD_CAL_TYPE, GRD_CI_SEQUENCE_NUMBER, and CEREMONY_NUMBER — graduation calendar and ceremony identification.
• ORDER_IN_PRESENTATION, GRADUAND_SEAT_NUMBER, NAME_ANNOUNCED, NAME_PRONUNCIATION — presentation and stage-management attributes.
• ACADEMIC_GOWN_SIZE, ACADEMIC_HAT_SIZE, and the descriptive-flexfield column "_LA:ACADEMIC_DRESS_RQRD_IND" — regalia details.
• GUEST_TICKETS_REQUESTED, GUEST_TICKETS_ALLOCATED, GUEST_SEATS — guest management.
• SPECIAL_REQUIREMENTS, COMMENTS, and "_LA:FEES_PAID_IND" — additional notes and fee status.
• GAC_ID, PERSON_ID, and the audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical usage centers on ceremony preparation, program-level rollups, and graduand extracts. A straightforward lookup by program code returns all graduands tied to that award program:

• SELECT person_name, person_number, award_program_code, award_cd, ceremony_number FROM igsbv_gr_crmn_stdnt_prg WHERE award_program_code = :program_code;
• Producing a presentation order listing: SELECT order_in_presentation, name_announced, gradduand_seat_number FROM igsbv_gr_crmn_stdnt_prg WHERE grd_cal_type = :cal AND ceremony_number = :cer ORDER BY order_in_presentation;
• Regalia and guest planning: selecting gown size, hat size, and guest ticket allocation for a given ceremony.
• Feeding downstream interfaces or extracts that require award program and ceremony identifiers together.

Because the view is read-only and, in the documented repository, not implemented, deployments should confirm availability in the target environment prior to use.