Results for “exam_constraints”

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

Overview

IGSFV_AS_ASSESSMENT_ITEMS is a read-only view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product. It describes an item that a student might be assessed against, capturing the full descriptive and examination-related attributes of each assessment item. Every item is of a nominated type, determined by the assessment type assigned to it, and may be classified as either examinable or non-examinable. Examinable items may require scheduling, examination papers, working and perusal times, and supervisory or candidate instructions. The "FV" naming convention indicates this is a foreign view, and the presence of the _DF column and "_LA:" lookup columns confirms that it is exposed for use through Oracle Forms and descriptive flexfield processing rather than for direct transactional DML. The view carries WITH READ ONLY, making it suitable exclusively for reporting, integration, and inquiry purposes within the institution's assessment and examination management processes.

Underlying Base Objects

The view text documents a join across two base objects in the IGS schema:

• IGS_AS_ASSESSMNT_ITM_ALL — aliased as AI; the primary source of assessment item data, including description, examination details, flexfield context, and audit columns.
• IGS_AS_ASSESSMNT_TYP — aliased as ATYP; the assessment type reference table, joined on AI.ASSESSMENT_TYPE = ATYP.ASSESSMENT_TYPE to resolve the assessment type description.

The ETRM metadata for version 12.2.2 does not add further documented base objects; the join as shown in the view text is the definitive relationship. The _ALL suffix on the item table indicates a multi-org style table, though the view itself does not expose an org identifier, so the join behaves as presented. Because the assessment type is mandatory in the join, assessment item rows without a valid corresponding assessment type will be excluded from this view's results — a behavior report developers should verify against data integrity expectations.

Key Columns

The principal exposed columns, several of which carry descriptive flexfield or lookup aliasing, include:

• ASSESSMENT_ITEM_DESCRIPTION — the free-text description of the assessment item (source column AI.DESCRIPTION); this is the column most directly relevant to a search on "assessment_item_description".
• ASSESSMENT_TYPE and ASSESSMENT_TYPE_DESCRIPTION — the code and its resolved meaning from the assessment type table.
• EXAM_SHORT_PAPER_NAME, EXAM_PAPER_NAME, EXAM_WORKING_TIME, EXAM_PERUSAL_TIME — examination paper naming and timing attributes.
• "_LA:EXAM_SCHEDULED_INDICATOR" and "_LA:CLOSED_INDICATOR" — lookup-aliased indicators translated via IGS_LOOKUP_VALUES (YES_NO), returning the lookup MEANING.
• EXAM_SUPERVISOR_INSTRUCTIONS, EXAM_ANNOUNCEMENTS, EXAM_ALLOWABLE_INSTRUCTIONS, EXAM_NON_ALLOWED_INSTRUCTIONS, EXAM_SUPPLIED_INSTRUCTIONS, EXAM_CONSTRAINTS — examination conduct and logistics attributes.
• QUESTION_OR_TITLE, ASSESSMENT_LENGTH_OR_DURATION, COMMENTS — item content and length descriptors.
• _DF — the descriptive flexfield segment container, built from IGS_AS_ASS_ITM_DESC_FLEX:AI.
• ASSESSMENT_ID plus standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include listing assessment items by type, retrieving examination scheduling attributes, and exporting item descriptions for integration with external examination or timetable systems. A basic search for the requested term would resemble:

SELECT assessment_item_description, assessment_type_description, exam_paper_name, exam_working_time FROM igsfv_as_assessment_items WHERE UPPER(assessment_item_description) LIKE UPPER('%' || :search_term || '%');

Joining to other IGS assessment structures by ASSESSMENT_ID supports drill-down reporting, while the flexfield and lookup columns are best referenced through their quoted aliases when selecting indicator meanings. Because the view is read-only and does not expose org context, all extraction and transformation should be executed against this view, with transactional maintenance directed to the underlying base tables.