Search Results unit_version




Overview
Explore in AI Chat

Overview

IGS_PR_SUA_INQ_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGS_PR_SUA_INQ_V. It belongs to the Student Systems / Student Records (IGS) product family and is classified as a supplementary view used to simplify forms coding. In practice, this means the view exists primarily to support an Oracle Forms inquiry block — most likely a Student Unit Attempt (SUA) inquiry form — rather than to serve as a general-purpose reporting interface.

Oracle explicitly warns that this view should not be queried or altered for data manipulation, and that its definition may change dramatically in subsequent minor or major releases. Its status is VALID as documented in ETRM 12.2.2, and the structure is common to both 12.1.1 and 12.2.2 releases. The view is read-only in intent and is denormalized to present a single row per student-unit-attempt context, joining person, course, unit, calendar, and outcome attributes into one flat projection.

Underlying Base Objects

The ETRM metadata does not document explicit referenced base objects for this view. Based on the IGS data model and the columns exposed, the view is derived from core Student Records tables — principally the student unit attempt table (IGS_PR_STD_UNT_ATT) and its related unit version, person, calendar instance, and unit offering option tables. Typically these join IGS_PR_STD_UNT_ATT to HZ_PARTIES / PERSON identifiers, IGS_PS_UNIT_VERSIONS for unit version attributes, IGS_CA_INSTANCES for calendar instance dates, and outcome/grading tables for marks and grades.

Because the underlying joins are not documented in ETRM, consumers should treat the lineage as inferred rather than guaranteed. This is consistent with the warning that the view is a forms-support construct whose internal shape is not contractual.

Key Columns

Common Use Cases and Queries

The primary use case is supporting the SUA inquiry form, where users inspect a student's unit attempt together with unit version, status, and outcome details. For ad hoc reporting, the view can be referenced read-only, but consumers must accept the volatility warning.

Sample query listing unit version details for a person:

  • SELECT PERSON_ID, COURSE_CD, UNIT_CD, UNIT_VERSION, UNIT_TITLE, UNIT_ATTEMPT_STATUS, ENROLLED_DT FROM APPS.IGS_PR_SUA_INQ_V WHERE PERSON_ID = :p_person_id;
  • SELECT UNIT_CD, UNIT_VERSION, GRADE, MARK, S_RESULT_TYPE FROM APPS.IGS_PR_SUA_INQ_V WHERE UNIT_ATTEMPT_STATUS = 'ENROLLED';
  • SELECT PERSON_ID, UNIT_VERSION, ENROLLED_CP, EFTSU, ACHIEVABLE_CP FROM APPS.IGS_PR_SUA_INQ_V WHERE COURSE_CD = :p_course_cd ORDER BY PERSON_ID;

Because of the documented volatility, production integrations should be built against the underlying base tables rather than this view, and any query relying on UNIT_VERSION should treat it as a display convenience value.