Search Results venue_code

Overview

IGSBV_VENUES is a read-only view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product family. It exposes the physical venues at which examinations or graduation ceremonies can be accommodated. According to the ETRM metadata, a venue may exist within a location such as a campus, or within an examination location such as a Town Hall. The view carries status VALID and is documented against ETRM 12.2.2, and it is equally available in 12.1.1 environments where the IGS module is licensed.

The view functions as a reporting and integration surface for venue reference data. Because the underlying table retains legacy column names such as VENUE_CD and EXAM_LOCATION_CD, the view deliberately renames them to the more readable VENUE_CODE and EXAM_LOCATION_CODE, which is why a search on "venue_code" resolves to this object rather than directly to the base table. Consumers include exam scheduling reports, graduation ceremony planning extracts, venue utilisation queries, and inbound or outbound interfaces that require a stable, read-only projection of venue attributes.

Underlying Base Objects

The view is defined over a single base object, IGS_GR_VENUE_ALL, and is declared WITH READ ONLY. No additional base tables are documented in the ETRM metadata, and the view performs no joins or aggregations; every column is a direct projection of a corresponding column in the base table with an optional alias. Because IGS_GR_VENUE_ALL is an _ALL suffixed table, it is the multi-organisation (multi-tenant) variant of the venue entity, and the view therefore inherits whatever organisation security the base table enforces at the row level. The READ ONLY clause guarantees that DML issued against IGSBV_VENUES will fail, so all maintenance must target IGS_GR_VENUE_ALL through the supported IGS forms or APIs. The absence of documented foreign-key relationships in the view text means downstream joins must be constructed explicitly by the consumer, typically through EXAM_LOCATION_CODE or COORDINATE_PERSON_IDENTIFIER.

Key Columns

• VENUE_CODE — Primary business identifier of the venue; aliased from VENUE_CD in the base table.
• DESCRIPTION — Free-text name or description of the venue.
• EXAM_LOCATION_CODE — The examination location within which the venue resides; aliased from EXAM_LOCATION_CD. Links the venue to its parent location or campus.
• NUMBER_OF_SEATS — Seating capacity, central to room allocation and candidate placement logic.
• BOOKING_COST — Cost associated with reserving or hiring the venue.
• SUPERVISOR_LIMIT — Maximum number of supervisors the venue supports.
• PRIORITY_CODE — Priority ranking used when multiple candidate venues are available; aliased from PRIORITY_CD.
• CLOSED_INDICATOR — Flag indicating the venue is unavailable for booking; aliased from CLOSED_IND.
• COMMENTS, RESOURCES_AVAILABLE, ANNOUNCEMENTS — Descriptive and operational text fields.
• SEATING_INFORMATION, BOOKING_INFORMATION, INSTRUCTIONS — Guidance text for seating layout, booking procedure, and on-site instructions.
• COORDINATE_PERSON_IDENTIFIER — Identifier of the coordinating person; aliased from COORD_PERSON_ID and resolvable to PER_ALL_PEOPLE_F.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include listing active venues for an exam location, computing total seat capacity per location, and extracting venue data for graduation planning or interface staging.

Active venues for a given examination location:

SELECT venue_code, description, number_of_seats, booking_cost
FROM   igsbv_venues
WHERE  exam_location_code = :p_exam_location
AND    closed_indicator = 'N'
ORDER BY priority_code, venue_code;

Capacity and supervisor planning by location:

SELECT exam_location_code,
       COUNT(*)                AS venue_count,
       SUM(number_of_seats)    AS total_seats,
       SUM(supervisor_limit)   AS total_supervisors
FROM   igsbv_venues
WHERE  closed_indicator = 'N'
GROUP BY exam_location_code;

Venue detail with coordinating person:

SELECT v.venue_code, v.description, v.seating_information,
       p.full_name AS coordinator
FROM   igsbv_venues v, per_all_people_f p
WHERE  v.coordinate_person_identifier = p.person_id
AND    TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date;

Because the view is read-only, these queries are safe for concurrent reporting; any correction of venue attributes must be performed through the IGS venue maintenance forms, which write to IGS_GR_VENUE_ALL.