Search Results igs_gr_venue




Overview
Explore in AI Chat

Overview

IGS_GR_VENUE is a security-enabled Oracle E-Business Suite view owned by the APPS schema within the IGS (Student System) product group. In EBS 12.1.1 and 12.2.2, it exposes venue records used by the Graduation Management (GR) module to define the physical rooms, halls, or exam locations where graduation ceremonies, examinations, and related events are staged. Venues carry seating capacity, booking cost, priority, and supervisory limits, and each venue may be assigned a coordinating person, referenced through the COORD_PERSON_ID column.

Because the view is defined over a multi-org (_ALL) table and filtered by an ORG_ID predicate derived from the session CLIENT_INFO, it returns only those venue rows visible to the current operating unit context. This makes it the reporting-safe interface for venue data: the view is keyed with a ROWID alias (ROW_ID) and exposes the standard WHO audit columns, allowing it to be treated as an updatable-style entity for Forms, concurrent programs, and integrations without directly touching the underlying table.

Underlying Base Objects

The view is defined over a single documented base object, IGS_GR_VENUE_ALL. The projection selects all principal attributes from that table, renaming the ORG_ID column explicitly and aliasing the table ROWID as ROW_ID. The multi-org filter is applied through a DECODE against USERENV('CLIENT_INFO'): the first ten characters of CLIENT_INFO are converted to a number, with a fallback of -99 when the value is blank, and this is matched against NVL(TAB.ORG_ID, ...). Rows whose ORG_ID does not match the active operating unit are therefore suppressed, producing an operating-unit-specific result set from a single, org-partitioned base table. The ETRM 12.2.2 metadata documents no additional referenced objects beyond IGS_GR_VENUE_ALL.

Key Columns

Common Use Cases and Queries

Typical reporting retrieves open, high-capacity venues for a given operating unit and identifies their coordinators. Note that the view itself enforces the ORG_ID filter, so callers need not add a security predicate.

To locate a venue by coordinator:

  • SELECT venue_cd, description, number_of_seats, coord_person_id FROM igs_gr_venue WHERE coord_person_id = :p_person_id;
  • SELECT venue_cd, description, booking_cost FROM igs_gr_venue WHERE closed_ind = 'N' AND number_of_seats >= :p_min_seats ORDER BY priority_cd;
  • SELECT v.venue_cd, v.description, p.full_name FROM igs_gr_venue v, per_all_people_f p WHERE v.coord_person_id = p.person_id AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date;

These patterns support venue selection lists, seating-capacity planning, coordinator workload reports, and booking-cost analysis within the Student System.