Results for “action_dt”

50+ results




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

Overview

The view APPS.IGS_AS_UAI_EXAM_CI_V belongs to the Oracle E-Business Suite Student System product (IGS) and is documented as a VALID object in the APPS schema for both ETRM 12.1.1 and 12.2.2. Its purpose is to resolve, for a given unit assessment item record, the examination calendar instances under which that item is examined. In other words, it answers the question: "For this assessment item, which active examination calendar instance(s) apply?" The vendor description states that the view "describes the examination calendar instances that a unit assessment item record is examined," and that this determination "is based on the relationships between the teaching and examination calendar instances and the override uai.exa…" (the remainder of the sentence is truncated in the source documentation but plainly refers to the override columns UAI.EXAM_CAL_TYPE and UAI.EXAM_CI_SEQUENCE_NUMBER on IGS_AS_UNITASS_ITEM).

The view is not a transactional entity; it is a read-only reporting and integration object. It is typically consumed by exam scheduling reports, student assessment inquiry screens, examination timetabling extracts, and downstream interfaces that need to align a unit assessment item with its corresponding exam calendar instance. Because it applies hard filters (only examinable assessment types, only exam-scheduled assessment items, only ACTIVE exam calendar statuses), the view functions as a validated, business-rule-filtered bridge between assessment definition data and calendar instance data.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 records "Referenced base objects: none documented," which is common for older IGS views whose dependencies were not formally registered in the ETRM repository. However, the view text itself unambiguously defines the base objects through its FROM clause:

The join logic therefore enforces four independent conditions: the assessment item must be exam-scheduled, its assessment type must be examinable, the calendar type must be an EXAM calendar, and the calendar status must be ACTIVE. Additionally, the override predicate (UAI.EXAM_CAL_TYPE IS NULL OR CI.CAL_TYPE = UAI.EXAM_CAL_TYPE) and the matching sequence predicate allow an explicit override of the exam calendar instance; when both override columns are null, the view defaults to the calendar instances derived through the teaching-to-examination relationship.

Key Columns

Common Use Cases and Queries

The view is most often used to report or extract the examination calendar instance associated with each unit assessment item, particularly where exam timetabling or student exam scheduling processes require an authoritative, business-rule-filtered list. Typical consumers include exam timetable reports, assessment schedule inquiries, and integration extracts feeding examination seating or invigilation systems.

A representative query listing all exam instances for a unit in a given teaching period:

SELECT exam_cal_type,
       exam_ci_sequence_number,
       unit_cd,
       version_number,
       ass_id,
       sequence_number,
       due_dt,
       reference
  FROM apps.igs_as_uai_exam_ci_v
 WHERE unit_cd = :p_unit_cd
   AND version_number = :p_version_number
   AND cal_type = :p_teaching_cal_type
   AND ci_sequence_number = :p_teaching_ci_seq;

A second common pattern identifies assessment items whose exam calendar instance has been explicitly overridden:

SELECT v.unit_cd,
       v.version_number,
       v.ass_id,
       v.sequence_number,
       v.exam_cal_type,
       v.exam_ci_sequence_number
  FROM apps.igs_as_uai_exam_ci_v v
 WHERE v.exam_cal_type IS NOT NULL
   AND v.exam_ci_sequence_number IS NOT NULL
 ORDER BY v.unit_cd, v.version_number, v.ass_id;

Because the view already excludes logically deleted rows, non-examinable assessment types, non-exam-scheduled items, and inactive calendar statuses, callers do not need to re-apply those predicates. Performance-sensitive integrations should note the ENRS_GET_WITHIN_CI PL/SQL call in the WHERE clause, which can inhibit index-based access paths on large calendar instance volumes; restricting by UNIT_CD, VERSION_NUMBER, and calendar instance sequence typically yields the best response times.