Search Results igs_pr_ou_unit_set_all




Overview
Explore in AI Chat

Overview

The table IGS_PR_OU_UNIT_SET_ALL is a core data object within the Oracle E-Business Suite Student System (IGS) for releases 12.1.1 and 12.2.2. It functions as a junction table that establishes a critical relationship between progression rules and academic unit sets. Specifically, it stores the unit sets from which a student will be automatically failed if they fail the associated progression rule. This table is central to the automated enforcement of academic standing policies, enabling institutions to define precise academic consequences based on student performance against defined rules. Its "ALL" suffix indicates it is a multi-org table, capable of storing data partitioned by operating unit, which is a standard design pattern in Oracle EBS for supporting complex enterprise structures.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies each record by linking a specific progression rule to a specific unit set. The key columns are PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, and PRO_SEQUENCE_NUMBER, which together reference a specific progression outcome rule defined in IGS_PR_RU_OU_ALL. The columns UNIT_SET_CD and US_VERSION_NUMBER reference a specific version of an academic unit set defined in IGS_EN_UNIT_SET_ALL. Therefore, each row represents the enforcement condition: failure of the referenced progression rule results in failure from the referenced unit set. The table primarily serves as a relationship mapper and does not typically contain extensive descriptive attributes beyond these foreign key identifiers.

Common Use Cases and Queries

This table is primarily accessed for configuration, reporting, and batch processing related to academic progression. Common use cases include auditing the unit sets linked to a specific progression rule to verify policy setup, and identifying all progression rules that can result in failure from a particular unit set during student advising. A typical reporting query would join to the related tables to provide descriptive context. For example, to list all unit sets linked to a specific rule category:

  • SELECT us.unit_set_cd, us.us_version_number, us.unit_set_name FROM igs_pr_ou_unit_set_all ous JOIN igs_en_unit_set_all us ON ous.unit_set_cd = us.unit_set_cd AND ous.us_version_number = us.version_number WHERE ous.progression_rule_cat = :rule_cat;

Another critical use case is during the batch process that evaluates student progression. The system queries this table to determine the specific unit sets from which a student must be failed after a rule failure is triggered.

Related Objects

The table IGS_PR_OU_UNIT_SET_ALL has defined foreign key relationships with two primary tables in the Student System, as documented in the ETRM metadata:

  • IGS_PR_RU_OU_ALL: This is the parent table for progression outcome rules. The relationship is established via the columns PROGRESSION_RULE_CAT, PRA_SEQUENCE_NUMBER, and PRO_SEQUENCE_NUMBER. This defines the specific rule whose failure triggers the action.
  • IGS_EN_UNIT_SET_ALL: This is the parent table for academic unit sets (e.g., majors, minors). The relationship is established via the columns UNIT_SET_CD and US_VERSION_NUMBER. This defines the academic program from which the student will be failed.

The table's primary key constraint, IGS_PR_OU_UNIT_SET_PK, enforces the uniqueness of these relationships. There are no other documented foreign keys where this table is the parent, indicating it is a terminal detail table in this relationship chain.