Results for “igs_ps_unit_lvl_all”

45 results




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

Overview

The IGS_PS_UNIT_LVL_ALL table is an entity within the Oracle E-Business Suite IGS – Student System product family. As documented in the ETRM (E-Business Suite Technical Reference Manual) metadata, this table describes the level of a unit within a particular university program type. The stored value is intended to override the default unit level that would otherwise be inherited from the unit definition itself. This makes the table a specialization or override mechanism layered on top of the base unit and program-type definitions maintained elsewhere in the Student System schema.

It is important to note that the ETRM metadata explicitly records this object as “Not implemented in this database” and classifies the product module as Obsolete. Consultants should therefore treat IGS_PS_UNIT_LVL_ALL as a legacy or deprecated construct. It may still exist in earlier 12.1.1 installations where the Student System was licensed and installed, but it will generally be absent from 12.2.2 environments unless a specific legacy installation persists.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is “link.” This is consistent with the table’s behavior: it connects a unit (via UNIT_CD and VERSION_NUMBER) to a program/version (COURSE_CD, COURSE_VERSION_NUMBER) and associates a level value. The composite key and heavy FK usage reinforce this link-like role rather than a pure hub or satellite pattern.

Key Information Stored

The physical schema documents 13 columns. The most consequential for understanding and querying the table are:

The primary key is documented as IGS_PS_UNIT_LVL_PK, comprising UNIT_CD, VERSION_NUMBER, COURSE_CD, and COURSE_VERSION_NUMBER. Notably, there is also a unique index IGS_PS_UNIT_LVL_ALL_U1 over the same four columns, which represents the business-key candidate. In this case the surrogate PK and the business key coincide column-wise, so no separate numeric surrogate identifier is present in the documented column list.

Common Use Cases and Queries

Because the table captures context-specific overrides, the most natural reporting scenario is comparing the effective unit level against the base unit definition. A representative join pattern follows the documented FKs:

  • Identifying all units whose level differs in a given program type versus the default. Join IGS_PS_UNIT_LVL_ALL to IGS_PS_UNIT_VER_ALL on UNIT_CD and VERSION_NUMBER.
  • Enriching a unit listing with its program type by joining IGS_PS_TYPE_ALL on COURSE_TYPE.
  • Resolving the descriptive level text via IGS_PS_UNIT_LEVEL_ALL on UNIT_LEVEL.
  • Resolving the program/course description through IGS_PS_VER_ALL on COURSE_CD and COURSE_VERSION_NUMBER.
  • Reporting WAM weighting exceptions by program type for academic quality or governance analysis.

A typical analytical skeleton:

SELECT ul.UNIT_CD, ul.VERSION_NUMBER, ul.COURSE_CD,
       ul.COURSE_TYPE, ul.UNIT_LEVEL, ul.WAM_WEIGHTING
FROM   IGS_PS_UNIT_LVL_ALL ul
WHERE  ul.ORG_ID = :org_id;

Related Objects

The following directly related objects, derived from the documented FK and PK relationships, are the most significant:

  • IGS_PS_UNIT_VER_ALL – referenced via UNIT_CD, VERSION_NUMBER; the base unit-version source of default levels.
  • IGS_PS_VER_ALL – referenced via COURSE_CD, COURSE_VERSION_NUMBER.
  • IGS_PS_TYPE_ALL – referenced via COURSE_TYPE.
  • IGS_PS_UNIT_LEVEL_ALL – referenced via UNIT_LEVEL.

Given its obsolete status, no standing API dependencies are documented; integration should be validated against the live target environment before reliance.