Search Results rud_sequence_number




Overview
Explore in AI Chat

Overview

The IGS_RU_GROUP_SET table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle's Higher Education product) module. It functions as a junction or mapping table that defines the composition of rule groups. Its primary role is to associate individual rule components, referred to as "set pieces" or "items," with their parent rule groups. This structure enables the modular construction and management of complex business rules by linking rule definitions (RUD_SEQUENCE_NUMBER) to the logical groups (RUG_SEQUENCE_NUMBER) that contain them, facilitating rule reuse and organized application logic within the student system.

Key Information Stored

The table's schema is relatively simple, centering on two key foreign key columns that establish the critical relationship. All other columns are standard EBS audit attributes.

  • RUG_SEQUENCE_NUMBER (NUMBER): The mandatory foreign key that stores the unique identifier for a rule group. This column, in conjunction with RUD_SEQUENCE_NUMBER, forms the table's unique constraint (IGS_RU_GROUP_SET_U1).
  • RUD_SEQUENCE_NUMBER (NUMBER): The mandatory foreign key that stores the unique identifier for an individual rule description or component. This is the column referenced in the user's search. It is indexed both as part of the unique key and via a separate non-unique index (IGS_RU_GROUP_SET_N1), indicating frequent querying and filtering operations based on this identifier.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): These columns track the audit trail for each record, capturing the user and timestamp for creation and last update, which is standard practice for EBS transactional tables.

Common Use Cases and Queries

This table is primarily accessed for reporting on rule group composition, troubleshooting rule execution, and during data validation or migration tasks. A fundamental query retrieves all components of a specific rule group, which is essential for understanding its logic. For example, to list all rule description IDs within rule group 1001:

SELECT RUD_SEQUENCE_NUMBER FROM IGS.IGS_RU_GROUP_SET WHERE RUG_SEQUENCE_NUMBER = 1001 ORDER BY RUD_SEQUENCE_NUMBER;

Conversely, to identify all rule groups that incorporate a specific rule component (e.g., RUD_SEQUENCE_NUMBER = 205), the following query would be used, leveraging the non-unique index on that column:

SELECT RUG_SEQUENCE_NUMBER FROM IGS.IGS_RU_GROUP_SET WHERE RUD_SEQUENCE_NUMBER = 205;

For comprehensive audit reporting, a join with the FND_USER table on the WHO columns can provide usernames for the creators and modifiers of these rule group assignments.

Related Objects

Based on the provided ETRM metadata, the IGS_RU_GROUP_SET table is referenced by the APPS synonym named IGS_RU_GROUP_SET. This synonym allows other PL/SQL code and database sessions within the APPS schema to access the table without prefixing the IGS owner schema. The metadata indicates the table does not itself reference other objects, confirming its role as a dependent child table. The columns RUG_SEQUENCE_NUMBER and RUD_SEQUENCE_NUMBER are foreign keys. They logically reference primary keys in parent tables, most likely named IGS_RU_GROUP (or similar) for RUG_SEQUENCE_NUMBER and IGS_RU_DESCRIPTION (or similar) for RUD_SEQUENCE_NUMBER, which would store the master definitions for rule groups and rule descriptions, respectively. These relationships are enforced at the application level within the IGS module.