Search Results examinable_ind




Overview
Explore in AI Chat

Overview

The APPS.IGS_AS_UNIT_ASSESSMENT_ITEM_V view is a public database view owned by the APPS schema in Oracle E-Business Suite, registered under the FND Design Data object IGS.IGS_AS_UNIT_ASSESSMENT_ITEM_V. Its status is VALID for both the 12.1.1 and 12.2.2 releases of EBS, and it is delivered under the Oracle Student System (IGS) product family, specifically the Assessment (AS) module responsible for managing assessment items tied to unit offerings. The view is documented by Oracle as having been created primarily to support the Assignment Due Dates Summary Report, and Oracle explicitly describes it as "a public view which may be useful for custom reporting or other data requirements." This makes it a supported integration and reporting surface rather than an internal-only object.

Functionally, the view exposes a flattened, denormalised picture of unit assessment items, combining unit addressing (unit code, version, calendar type, calendar instance), unit offering option (UOO) context (location, class, mode, ID), and assessment-level attributes (assessment identifier, sequence, due date, assessment type, examinable flag). It is therefore best understood as a reporting convenience view over the underlying IGS assessment and calendar structures, giving report authors a single object from which to drive the Assignment Due Dates Summary and similar extracts.

Underlying Base Objects

The ETRM metadata for this view does not enumerate the referenced base tables — the "Referenced base objects" field is documented as none. Practically, however, a view of this nature draws from the IGS Assessment and Calendar schema families, most plausibly joining unit assessment item tables (such as IGS_AS_UNIT_ASSESSMENT_ITEM and its associated assessment/master records) against unit offering option and calendar instance tables (in the IGS_EN / IGS_CA domains). The "Created By," "Creation Date," "Last Updated By," "Last Update Date," and "Last Update Login" columns confirm the view passes through standard Who columns from its source rows.

Because the source tables are not surfaced in the metadata, consumers should treat the view strictly as a black-box reporting layer. Any join back to base tables should be performed on the identifier columns exposed here — ASS_ID, UOO_ID, UNIT_CD, VERSION_NUMBER, CI_SEQUENCE_NUMBER, and UNIT_ASS_ITEM_GROUP_ID — rather than assuming a particular underlying structure.

Key Columns

  • UNIT_CD / VERSION_NUMBER — Identify the academic unit and its version.
  • CAL_TYPE / CI_SEQUENCE_NUMBER — Calendar type and calendar instance sequence, anchoring the calendar context.
  • UOO_LOCATION_CD, UOO_UNIT_CLASS, UOO_UNIT_MODE, UOO_ID — Unit offering option attributes defining where and how the unit is delivered.
  • ASS_ID, SEQUENCE_NUMBER, UAI_REFERENCE — Assessment identifier, sequence, and the unit assessment item reference number.
  • WEEK_ENDING_DT, UAI_DUE_DT, UAI_LOGICAL_DELETE_DT — Week-ending date, the assessment item due date, and logical deletion date (used for soft-delete filtering).
  • ASSESSMENT_TYPE / S_ASSESSMENT_TYPE — User-facing and system assessment type codes.
  • EXAMINABLE_IND — The examinable indicator searched for; flags whether the assessment item counts as an examination.
  • UNIT_ASS_ITEM_GROUP_ID — Unique identifier grouping the assessment item.
  • MIDTERM_MANDATORY_TYPE_CODE / MIDTERM_WEIGHT_QTY / FINAL — Midterm grading period handling, defining optional/mandatory/pass status and relative weighting.
  • Standard Who columns — Audit trail fields.

Common Use Cases and Queries

A typical use is reporting examinable items and their due dates for a given calendar instance, excluding logically deleted rows:

SELECT unit_cd, version_number, uai_reference, uai_due_dt, assessment_type
FROM   apps.igs_as_unit_assessment_item_v
WHERE  examinable_ind = 'Y'
AND    uai_logical_delete_dt IS NULL
AND    ci_sequence_number = :p_cal_instance
ORDER BY uai_due_dt;

Other scenarios include building the Assignment Due Dates Summary by grouping on UNIT_CD and UAI_DUE_DT, filtering by S_ASSESSMENT_TYPE to isolate examination records, and using UNIT_ASS_ITEM_GROUP_ID to aggregate grouped items. Because the object is a public view, custom reports and interfaces may query it directly without violating support boundaries.