Search Results unit_section_ai_reference

Overview

IGSBV_AS_UNT_SECTION_ASS_ITEMS is a read-only database view owned by the APPS schema in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the IGS (Student System) product family—Oracle's legacy Student Information System module that underpins academic records, unit offerings, assessments, and grading. The object type is VIEW, documented with a VALID status in the ETRM reference set.

The view presents a consolidated, presentation-ready picture of every assessment item attached to a unit section. A "unit section" in IGS corresponds to a single teaching occurrence of a unit (for example, a semester- or term-specific offering of a course), while an "assessment item" represents an individual graded or scored component such as an exam, assignment, midterm, or final. The view therefore acts as a query surface that flattens the underlying IGS assessment configuration into a form suited to reporting, integration, and downstream extract routines. It aligns closely with the naming convention user-search term unit_section_ai_reference, which corresponds to the REFERENCE column exposed by the view.

Because the view is implemented WITH READ ONLY, it is intended strictly for queries and reporting; all inserts and updates must be directed at the base table.

Underlying Base Objects

The view is defined over a single documented base object:

• IGS_PS_UNITASS_ITEM (aliased as UNAS) — the base table that stores assessment item definitions for unit sections.

The defining query selects columns directly from this table and applies only light transformation, principally the resolution of several coded columns into their user-facing meanings through lookup column aliases (the _LA: tokens). Specifically, the view resolves MIDTERM_MANDATORY_TYPE_CODE and FINAL_MANDATORY_TYPE_CODE against the IGS_LOOKUP_VALUES view (lookup type IGS_AS_AI_MANDATORY_TYPES), and resolves DFLT_ITEM_IND against IGS_LOOKUP_VALUES (lookup type YES_NO). No joins beyond these lookup translations are documented, and no other referenced base objects are listed in the metadata.

Key Columns

The view exposes approximately twenty-six columns. The most significant include:

• UNIT_SECTION_ASS_ITEM_ID — the primary identifier for the assessment item (derived from UNAS.UNIT_SECTION_ASS_ITEM_ID).
• UNIT_SECTION_AI_DESCRIPTION and UNIT_SECTION_AI_REFERENCE — human-readable description and a reference/code label for the assessment item.
• UNIT_SECTION_ID — links the assessment item to its parent unit section.
• ASSESSMENT_ID — the underlying assessment definition identifier.
• CALENDAR_START_DATE / CALENDAR_END_DATE — the validity window for the item.
• UNIT_SECTION_AI_GROUP_ID and SEQUENCE_NUMBER — grouping and ordering attributes.
• MIDTERM_MNDRY_TYP_CD, MIDTERM_WEIGHT_QUANTITY, FINAL_MNDRY_TYP_CODE, FINAL_WEIGHT_QUANTITY — midterm and final mandatory flags and their weighting quantities.
• GRADING_SCHEMA_CODE / GRADING_SCHEMA_VERSION_NUMBER — grading scheme in force.
• DUE_DATE, RELEASE_DATE, ACTION_DATE — key milestone dates.
• EXAM_CALENDAR_TYPE / EXAM_CALENDAR_SEQUENCE_NUMBER — linkage to examination calendar entries.
• _LA:DEFAULT_ITEM_INDICATOR, LOGICAL_DELETE_DATE, and standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include assessment configuration reporting, load/extract for student records, and integration into grading or examination scheduling feeds. The sample below lists all assessment items for a given unit section:

• SELECT unit_section_ass_item_id, unit_section_ai_reference, unit_section_ai_description ... FROM igsbv_as_unt_section_ass_items WHERE unit_section_id = :p_unit_section_id AND logical_delete_date IS NULL ORDER BY sequence_number;
• Filter by grading schema: WHERE grading_schema_code = :p_schema AND grading_schema_version_number = :p_version
• Identify weighted components: WHERE midterm_weight_quantity IS NOT NULL OR final_weight_quantity IS NOT NULL

All queries should be executed against the APPS schema with appropriate read privileges, and users should honour the LOGICAL_DELETE_DATE filter so that logically deleted items are excluded from current reporting.