Search Results igs_en_unit_set_rule

Overview

The IGS_EN_UNIT_SET_RULE table is a core data entity within the Oracle E-Business Suite Student System (IGS). It functions as a junction table that establishes and manages the linkage between academic unit sets and the business rules that govern them. A unit set represents a defined collection of academic units (e.g., a major, minor, or specialization) within a program. This table's primary role is to associate specific rule calls—which define when and how a rule is evaluated—with a particular unit set and its version. This association is fundamental for enforcing academic policies, such as progression requirements, unit prerequisites, or completion criteria, ensuring students adhere to the structured curriculum defined by their enrolled unit sets.

Key Information Stored

The table stores the minimal attributes necessary to create a valid association between a unit set and a rule. The primary key is a composite of three columns, ensuring a unique rule assignment per unit set version. Key columns include:

• UNIT_SET_CD and VERSION_NUMBER: Together, these foreign key columns uniquely identify a specific version of an academic unit set from the IGS_EN_UNIT_SET_ALL table.
• S_RULE_CALL_CD: A foreign key to the IGS_RU_CALL table, this code identifies the specific rule call type (e.g., "ENROLLMENT_VALIDATION", "PROGRAM_COMPLETION").
• RUL_SEQUENCE_NUMBER: A foreign key to the IGS_RU_RULE table, this points to the specific rule sequence number that defines the executable logic or condition to be evaluated for the associated rule call.

Common Use Cases and Queries

This table is central to academic rule engine operations. A primary use case is the batch or real-time validation of a student's academic standing against their unit set requirements. For instance, during enrollment or progression checking, the system queries this table to determine which rules (RUL_SEQUENCE_NUMBER) and of what type (S_RULE_CALL_CD) apply to the student's enrolled unit set. A common reporting query would list all rules attached to a given unit set for audit purposes. A typical SQL pattern involves joining to IGS_RU_RULE and IGS_RU_CALL to get descriptive rule details:

SELECT usr.unit_set_cd, usr.version_number, rc.description AS rule_call_desc, rr.rule_name
FROM igs_en_unit_set_rule usr,
igs_ru_call rc,
igs_ru_rule rr
WHERE usr.s_rule_call_cd = rc.s_rule_call_cd
AND usr.rul_sequence_number = rr.rul_sequence_number
AND usr.unit_set_cd = '&unit_set_code';

Related Objects

The IGS_EN_UNIT_SET_RULE table maintains defined foreign key relationships with three critical tables in the Student System, as documented in the ETRM:

• IGS_EN_UNIT_SET_ALL: The parent table for unit set definitions. The join is on the composite key (UNIT_SET_CD, VERSION_NUMBER). This relationship ensures a rule is attached to a valid, existing unit set.
• IGS_RU_RULE: The parent table storing the rule logic definition. The join is on the RUL_SEQUENCE_NUMBER column.
• IGS_RU_CALL: The parent table for rule call types. The join is on the S_RULE_CALL_CD column, which contextualizes the rule's purpose within the unit set.

These relationships position IGS_EN_UNIT_SET_RULE as a critical configuration point between academic structures (unit sets) and the rule engine that enforces policy upon them.