Search Results rug_sequence_number




Overview

The IGS_RU_GROUP_ITEM table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically designed for the now-obsolete Student System (IGS) module. Its primary role is to function as a child table within the Rules Engine framework, storing the individual items or elements that constitute a defined rules group. A rules group is a logical collection of specific criteria or conditions used to evaluate student data for processes like admissions, progression, or graduation. This table enables the system to manage complex, multi-part rules by associating discrete descriptive items with a parent rule group sequence.

Key Information Stored

The table's structure is defined by a composite primary key that precisely links each item to its parent group and identifies the item's type. The critical columns are:

  • RUG_SEQUENCE_NUMBER: The foreign key linking the item to its parent rule group in the IGS_RU_GROUP table. This is the primary identifier for the group itself.
  • DESCRIPTION_TYPE: A code or identifier that classifies the type of the associated descriptive item (e.g., a course code, a unit set, a specific requirement).
  • DESCRIPTION_NUMBER: The specific identifier or value corresponding to the DESCRIPTION_TYPE, representing the actual rule criterion.
Together, these columns define a unique rule group item: a specific criterion (DESCRIPTION_NUMBER of a given DESCRIPTION_TYPE) belonging to a specific rules group (RUG_SEQUENCE_NUMBER).

Common Use Cases and Queries

This table is central to queries that need to list, validate, or report on the composition of rule groups. A common operational use case is generating a detailed breakdown of all criteria within a rule group for audit or troubleshooting purposes. For example, to retrieve all items for a specific rule group sequence (e.g., 1001), a developer or administrator might execute:

SELECT rug_sequence_number, description_type, description_number
FROM igs_ru_group_item
WHERE rug_sequence_number = 1001
ORDER BY description_type;
Another critical use case is in the runtime evaluation of rules, where the system would join this table to master data tables (like courses or requirements) based on the DESCRIPTION_TYPE and DESCRIPTION_NUMBER to check if a student's record satisfies all items in the group. Reporting on rule usage and complexity often involves aggregating counts from this table by RUG_SEQUENCE_NUMBER.

Related Objects

The IGS_RU_GROUP_ITEM table has a direct and singular parent-child relationship within the Rules module schema, as documented by its foreign key constraint.

  • IGS_RU_GROUP: This is the primary parent table. The relationship is maintained via the RUG_SEQUENCE_NUMBER column in IGS_RU_GROUP_ITEM, which references the corresponding sequence number in IGS_RU_GROUP. This enforces referential integrity, ensuring every group item is associated with a valid, existing rule group.
Given the module's obsolete status and the note that it is "Not implemented in this database," this documented foreign key likely represents the intended or historical design. In active implementations, this table would be central to views or APIs that assemble complete rule definitions for application logic.