Results for “igs_as_exam_instance”

29 results




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

Overview

The view IGS_AS_EXAM_INSTANCE belongs to the Oracle Student System (IGS) product family, which is classified as obsolete in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The view exposes exam instance records — the concrete occurrences of scheduled examinations generated from an exam calendar and its associated calendar instances. Each row represents a single sitting of an examination, carrying scheduling attributes such as start and end times, venue, and collection personnel, together with administrative text fields used for candidate-facing communications.

Because the view applies an operating unit security predicate against ORG_ID, it functions as an operational rather than a global listing. The predicate compares the ORG_ID of each row to the value extracted from USERENV('CLIENT_INFO'), so the set of rows returned depends on the client information established by the reporting session. This org-striping behaviour makes the view suitable for embedding in concurrent programs, Oracle Reports, and OBIEE or Discoverer queries where the caller's operating unit context is already set. It is not implemented as a physical database object in the supplied ETRM extract, meaning no data dictionary row exists for the current installation.

Underlying Base Objects

The ETRM documentation records no referenced base objects for this view, and the implementation status is "Not implemented in this database." The view text nevertheless reveals its single source: IGS_AS_EXAM_INSTANCE_ALL. The _ALL suffix indicates the multi-org table that stores exam instance rows for every operating unit, with ORG_ID as the partitioning attribute. The view is therefore a thin projection over that table, selecting a fixed column list and appending the operating unit filter. The TAB.ROWID column is carried forward as ROW_ID, which allows downstream tools to address the underlying row for update or drill-down purposes. No joins, lookups, or aggregations are present, so the view adds no business logic beyond row-level security.

Key Columns

Common Use Cases and Queries

Typical usage centres on examination timetabling reports, invigilation packs, and candidate notice extraction. The following query retrieves all sitting records carrying special instructions or announcements:

  • SELECT ass_id, exam_cal_type, exam_ci_sequence_number, dt_alias, start_time, end_time, venue_cd, special_session_ind, special_instructions FROM igs_as_exam_instance WHERE special_instructions IS NOT NULL ORDER BY dt_alias, start_time;
  • SELECT venue_cd, COUNT(*) FROM igs_as_exam_instance GROUP BY venue_cd; — venue utilisation counts.
  • SELECT * FROM igs_as_exam_instance WHERE special_session_ind = 'Y' AND TRUNC(start_time) = TRUNC(SYSDATE); — same-day special sittings.

Because the view is obsolete and may be unimplemented in a given environment, callers should verify its presence in ALL_VIEWS and fall back to IGS_AS_EXAM_INSTANCE_ALL with an explicit ORG_ID filter if required.