Search Results points_increment




Overview
Explore in AI Chat

Overview

IGS_PS_UNIT_VER is an APPS-owned, VALID view within the IGS (Student System) product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It exposes version-level definitions of academic units of study — the fundamental catalogue records that describe what can be taught, how it is assessed, and how much credit it carries. Each row represents one version of one unit code, bounded by effective dates and a version number, so that historical and future iterations of the same unit can coexist without overwriting prior definitions. The view is read-only by convention and is generally treated as a reporting and integration surface rather than a maintenance object; transactional maintenance of unit versions is performed through the Student System forms and APIs that write to the underlying base tables, while this view presents the current denormalised projection for query access. Its principal role is to serve as a stable, queryable source of unit-version attributes for concurrent programs, extracts, institution-specific reports, and interfaces into assessment, enrolment, and credit-generation processes. Because the view carries ORG_ID, it is multi-organisation aware and can be joined to organisation-based security constructs.

Underlying Base Objects

The ETRM metadata for this object documents no referenced base objects, and the view text is not published in the extract. The projection list is drawn from the IGS unit-version entity, conventionally based on IGS_PS_UNIT_VER_ALL and its associated descriptive, load, and repetition structures within the IGS schema family. What is documented is the shape of the projection itself: the columns exposed correspond to the unit-version table family, with ROWID presented as ROW_ID and the full ATTRIBUTE_CATEGORY / ATTRIBUTE1–20 descriptive flexfield set carried through. Because the base objects are not documented in this metadata set, implementations should confirm the dependency chain using ALL_DEPENDENCIES and ALL_VIEWS in the target instance before relying on any assumed join path. The view appears to apply no visible filtering in its projection list, so consumers should apply their own STATUS, date, and organisation predicates.

Key Columns

Common Use Cases and Queries

Typical uses include validating that lab credit is populated for all lab-bearing units, reconciling credit totals against lecture/lab/other splits, and feeding credit data into enrolment or funding extracts.

  • Locate units with lab credit: SELECT unit_cd, version_number, title, lab_credit_points FROM igs_ps_unit_ver WHERE lab_credit_points IS NOT NULL;
  • Reconcile the credit split: SELECT unit_cd, version_number, enrolled_credit_points, lecture_credit_points + lab_credit_points + other_credit_points AS split_total FROM igs_ps_unit_ver WHERE enrolled_credit_points <> NVL(lecture_credit_points,0) + NVL(lab_credit_points,0) + NVL(other_credit_points,0);
  • Restrict to a teaching period and organisation: SELECT unit_cd, version_number, title, lab_credit_points FROM igs_ps_unit_ver WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_dt AND NVL(end_dt, TRUNC(SYSDATE)+1);

Consumers should always filter by UNIT_STATUS and organisation, and should qualify ROW_ID rather than depending on it for joins.