Search Results number_of_seats




Overview
Explore in AI Chat

Overview

APPS.IGSBV_VENUES is a Business Intelligence System (BIS) view owned by the APPS schema and registered under the FND Design Data reference IGS.IGSBV_VENUES. It is part of the Oracle IGS (Advanced Benefits / Higher Education / Student Systems) family of reporting views and is delivered with a status of VALID. This view exposes information about physical venues at which examinations or graduation ceremonies may be accommodated. A venue in this model is always subordinate to a parent location — either an institution location (such as a campus) or an examination location (such as a town hall).

As a BIS view, IGSBV_VENUES is intended for read-only reporting and integration rather than transactional data entry. Consumers include institutional reporting teams building examination timetabling extracts, graduation ceremony planning reports, and downstream integrations that need to synchronise venue capacity, booking costs, or supervisor limits into scheduling or facilities management systems.

Because it is presented as a reporting view rather than a base table, querying IGSBV_VENUES avoids exposing the underlying denormalised storage and provides a stable, documented column set for external consumers. In a search context such as "autodromo bariloche", the view is the authoritative source within EBS for the descriptive and capacity attributes of any venue record, including externally named venues whose description field carries the venue's common name.

Underlying Base Objects

The ETRM metadata for this object does not document any referenced base objects. In practice, the IGSBV_VENUES view is defined over the IGS examination/graduation venue base table (typically IGS_VENUES in the APPS schema), which stores the persisted venue records. The view layers column naming and BIS presentation rules over that table and inherits its foreign-key relationship to the parent examination/graduation location entity through the EXAM_LOCATION_CODE column. Because the dependency list is undocumented in the supplied metadata, any impact analysis or extension work should be validated directly against the view definition in the target instance using ALL_VIEWS and ALL_DEPENDENCIES before changes are made.

Key Columns

  • VENUE_CODE (VARCHAR2(10)) — the unique identifier for the examination or graduation venue; the primary business key for joins and lookups.
  • DESCRIPTION (VARCHAR2(60)) — the human-readable venue name. This is the column most likely to hold a value such as a named motor racing circuit or similar external venue.
  • EXAM_LOCATION_CODE (VARCHAR2(10)) — the code of the parent examination/graduation location. An open venue must always have an open parent location.
  • NUMBER_OF_SEATS (NUMBER) — maximum seating capacity, used for allocation and scheduling decisions.
  • BOOKING_COST (NUMBER) — the cost of booking the venue.
  • SUPERVISOR_LIMIT (NUMBER) — the maximum number of supervisors normally allocated to the venue.
  • PRIORITY_CODE (NUMBER) — priority used to order venue preference when allocating examinations.
  • CLOSED_INDICATOR (VARCHAR2) — indicates whether the venue is closed.
  • COORDINATE_PERSON_IDENTIFIER (NUMBER(15)) — identifier of the coordinating person associated with the venue.

Several large VARCHAR2(2000) text columns — COMMENTS, RESOURCES_AVAILABLE, ANNOUNCEMENTS, SEATING_INFORMATION, BOOKING_INFORMATION, and INSTRUCTIONS — carry free-form operational detail such as seating layout, seat-number ranges, available equipment, and booking contact information.

Common Use Cases and Queries

Typical reporting scenarios include listing all open venues with capacity and cost, identifying venues by parent location, and extracting supervisor limits for examination resource planning.

SELECT venue_code,
       description,
       exam_location_code,
       number_of_seats,
       booking_cost,
       supervisor_limit
FROM   apps.igsbv_venues
WHERE  closed_indicator = 'N'
ORDER  BY priority_code, description;

To find a venue by its descriptive name, for example an externally named venue:

SELECT venue_code, description, number_of_seats
FROM   apps.igsbv_venues
WHERE  UPPER(description) LIKE '%AUTODROMO%BARILOCHE%';

To report venue usage against parent locations:

SELECT v.exam_location_code,
       v.venue_code,
       v.description,
       v.number_of_seats
FROM   apps.igsbv_venues v
ORDER  BY v.exam_location_code, v.priority_code;

Because the design intent is read-only reporting, these queries can be run safely from a reporting user or a custom concurrent program, subject to the standard APPS schema grants and any row-level security applied to the parent location entity.