Results for “igs_as_exmvnu_sesavl”

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

Overview

IGS_AS_EXMVNU_SESAVL is a reporting view within the Oracle E-Business Suite Student System (IGS) product family. In the ETRM metadata for release 12.2.2 it is classified under IGS - Student System (Obsolete), which indicates that the component predates the current Student System architecture (the Oracle Student System / Campus Solutions lineage) and is retained only for backward compatibility or historical reference. Its documented purpose is straightforward: the view exposes examination venue data, that is, the scheduled location and time details associated with examination sittings. As a view rather than a base table, it is intended for read access in reporting and integration scenarios, presenting a stable projection over the underlying transaction entity without exposing the physical storage layout.

Underlying Base Objects

The view text selects from a single underlying object, IGS_AS_EXMVNU_SESAVL_ALL, aliased as TAB in the defining query. This naming convention follows the standard multi-organization (multi-org) pattern used throughout EBS: the _ALL table stores rows for every operating unit, and the non-suffixed view applies an operating unit security predicate on top of it. In this case the predicate compares the row's ORG_ID against the value derived from USERENV('CLIENT_INFO'), the client information string populated by the Multi-Org initialization logic. The expression NVL(TAB.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTRB(USERENV('CLIENT_INFO'), 1, 10))), -99)) = NVL(...) restricts output to the current operating unit, with a default of -99 where no client information is available. The ETRM record notes "Referenced base objects: none documented" and "Not implemented in this database," meaning the view definition was captured from the documentation set rather than introspected from a live installation.

Key Columns

• ROW_ID - the ROWID of the underlying row, used by Oracle Forms-based maintenance screens for optimistic locking.
• VENUE_CD - the code identifying the examination venue.
• EXAM_CAL_TYPE and EXAM_CI_SEQUENCE_NUMBER - the calendar type and sequence number identifying the examination calendar instance to which the venue assignment belongs.
• DT_ALIAS and DAI_SEQUENCE_NUMBER - the date alias and its sequence, defining which day or slot within the examination pattern the session occupies.
• START_TIME and END_TIME - the scheduled start and end of the venue session.
• ESE_ID - the internal identifier of the examination session element linking the venue record to its parent examination scheduling entity.
• COMMENTS - free-text remarks attached to the venue allocation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN - the standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE - concurrent program audit columns identifying the request that last touched the row.
• ORG_ID - the operating unit that owns the venue session record.

Common Use Cases and Queries

Typical uses include examination timetable reports, venue utilization analysis, and integration extracts feeding downstream scheduling systems. Because the view enforces multi-org security, a session must run with the correct operating unit context (via FND_CLIENT_INFO or the standard Multi-Org initialization) or rows will be filtered out.

A basic listing for the current operating unit:

• SELECT venue_cd, exam_cal_type, exam_ci_sequence_number, dt_alias, start_time, end_time FROM igs_as_exmvnu_sesavl ORDER BY exam_cal_type, exam_ci_sequence_number, dt_alias;

Joining to the examination calendar instance to enrich the extract with examination descriptors:

• SELECT v.venue_cd, v.exam_cal_type, v.start_time, v.end_time FROM igs_as_exmvnu_sesavl v WHERE v.exam_cal_type = :cal_type AND v.exam_ci_sequence_number = :ci_seq;

Because IGS is marked obsolete, new development should avoid this view; existing reports and interfaces that still reference it should be reviewed against the current Student System data model before migration or upgrade.