Search Results unit_section_prev_grade_id




Overview
Explore in AI Chat

Overview

The view IGS_PS_USEC_PRV_GRAD_V belongs to the Oracle E-Business Suite Student System (IGS) product family. IGS was the legacy student information management module shipped in early EBS 11i/12.1.1 releases and is documented as obsolete in ETRM 12.2.2. The view exposes prior (historical) unit section grades recorded against a student's unit-of-study attempt, denormalised against the grading schema definition so that a consumer receives the human-readable grade name alongside the coded grade value.

The view's primary reporting role is to provide a stable, presentation-layer projection of the IGS_PS_USEC_PRV_GRAD table joined to the grading schema grade lookup. Because the join resolves the composite key of GRADING_SCHEMA_CODE, GRADING_SCHEMA_VERSION_NUMBER, and GRADING_SCHEMA_VALUE into a single FULL_GRADE_NAME, downstream reports and integration extracts do not need to replicate the grading schema resolution logic. The user search term grading_schema_version_number corresponds directly to one of the exposed columns and to the join predicate that ties grades to the correct version of a grading schema.

Note that ETRM records the object as "Not implemented in this database" and lists no documented base objects for the 12.2.2 owner. In practice this view is a legacy artefact; it is not created by the standard IGS installation scripts in supported 12.1.1/12.2.2 environments and typically exists only in customised or upgraded instances retained from prior IGS installations.

Underlying Base Objects

The view is defined over two documented base objects:

  • IGS_PS_USEC_PRV_GRAD (aliased USPG) — the driving table holding previous unit section grade rows.
  • IGS_AS_GRD_SCH_GRADE (aliased GSG) — the grading schema grade definition table providing grade descriptions and schema metadata.

The join is an equi-join using three predicates:

The composite match ensures that a grade recorded under a specific version of a grading schema resolves to the correct grade description for that version, rather than to an identically coded grade in a different schema version. The view is a non-key-preserving outer projection only in behaviour; the underlying join is effectively an inner join, so grade rows without a matching schema definition are suppressed.

Key Columns

  • ROW_ID — the ROWID of the underlying IGS_PS_USEC_PRV_GRAD row; useful as a surrogate handle for updates.
  • UNIT_SECTION_PREV_GRADE_ID — primary key of the previous grade record.
  • UOO_ID — identifier of the underlying unit offering option (the student's unit attempt) to which the grade belongs.
  • GRADING_SCHEMA_CODE — code identifying the grading schema applied.
  • GRADING_SCHEMA_VERSION_NUMBER — the specific version of the grading schema; critical for correctly interpreting historical grades after schema revision.
  • GRADING_SCHEMA_VALUE — the coded grade value (for example, a letter or numeric code).
  • FULL_GRADE_NAME — the descriptive grade name resolved from IGS_AS_GRD_SCH_GRADE.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include historical transcript reconstruction, grade-change audit reporting, and legacy data migration extracts where the descriptive grade name must be carried forward. A representative query retrieving previous grades for a unit offering option is:

  • SELECT u.UOO_ID, u.GRADING_SCHEMA_CODE, u.GRADING_SCHEMA_VERSION_NUMBER, u.GRADING_SCHEMA_VALUE, u.FULL_GRADE_NAME, u.LAST_UPDATE_DATE FROM IGS_PS_USEC_PRV_GRAD_V u WHERE u.UOO_ID = :p_ooo_id ORDER BY u.GRADING_SCHEMA_CODE, u.GRADING_SCHEMA_VERSION_NUMBER;

To isolate grades recorded under a specific schema version, constrain on the version column directly:

  • SELECT * FROM IGS_PS_USEC_PRV_GRAD_V WHERE GRADING_SCHEMA_CODE = 'STD' AND GRADING_SCHEMA_VERSION_NUMBER = 1;

Because ETRM documents this view as obsolete and not implemented in a standard 12.2.2 database, queries should be validated against ALL_VIEWS before deployment, and long-term solutions should migrate to the supported Student System replacement interfaces.