Results for “igs_ru_group”

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

Overview

IGS_RU_GROUP is a core configuration table within the Oracle E-Business Suite Student System (IGS) product family. It stores the definition of rule groups — logical collections of rules that the Student System rule engine evaluates together, typically to determine eligibility, validations, or conditional processing flows applied to applicants, students, programs, or enrollments. The table resides in the IGS schema and is marked VALID in the ETRM 12.1.1 / 12.2.2 data dictionary. It is a low-volume, high-value reference/maintenance object rather than a transactional table.

The documented primary key is IGS_RU_GROUP_PK, defined over the SEQUENCE_NUMBER column. The unique index IGS_RU_GROUP_U1 also covers SEQUENCE_NUMBER, confirming it as both the surrogate identifier and the enforceable uniqueness constraint on the group itself. Based on the heuristic Data Vault classification mined from the foreign-key structure, this object is hub-leaning: it is primarily a parent/key entity whose SEQUENCE_NUMBER is referenced by many dependent child tables. In a Data Vault 2.0 model it would most naturally map to a hub, with descriptive attributes such as GROUP_NAME carried on a corresponding satellite.

The table is one of the more heavily referenced nodes in the IGS rule engine schema. Nine distinct foreign-key columns across six dependent tables point back to it, indicating that the group definition anchors rule members, group membership, and select-group assignments.

Key Information Stored

Only seven physical columns are documented for this table in the 12.1.1 schema. The most significant are listed below.

• SEQUENCE_NUMBER — the surrogate primary key and the anchor of the IGS_RU_GROUP_PK constraint. Every dependent foreign key (RUG_SEQUENCE_NUMBER, MESSAGE_GROUP, SELECT_GROUP) resolves against this column.
• GROUP_NAME — the user-facing name of the rule group. This is the primary business descriptor and is the value most commonly surfaced in reports and maintenance forms.
• CREATED_BY — the user or process that created the group record; standard WHO column.
• CREATION_DATE — timestamp of initial insertion; used for audit and data lineage.
• LAST_UPDATED_BY — the user or process responsible for the most recent modification.
• LAST_UPDATE_DATE — timestamp of the most recent modification; a key column for incremental extract and change-detection logic in ETL or Data Vault loading.
• LAST_UPDATE_LOGIN — the login/session identifier associated with the last update; completes the standard audit trail.

The distinction between the surrogate key and the business key should be noted: SEQUENCE_NUMBER is a system-generated identifier, whereas GROUP_NAME is the human-readable candidate. Because IGS_RU_GROUP_U1 is defined only on SEQUENCE_NUMBER, GROUP_NAME is not independently enforced as unique in the documented dictionary.

Common Use Cases and Queries

Typical scenarios include reviewing rule-group definitions, auditing rule-engine configuration before an upgrade, and extracting group hierarchies for reporting or integration.

SELECT g.sequence_number, g.group_name,
       g.last_updated_by, g.last_update_date
FROM   igs.igs_ru_group g
WHERE  g.group_name LIKE :search_pattern;

To find the rules and items that belong to a given group, join the dependent tables on the RUG_SEQUENCE_NUMBER column:

SELECT g.group_name, i.*
FROM   igs.igs_ru_group g,
       igs.igs_ru_group_item i
WHERE  i.rug_sequence_number = g.sequence_number
AND    g.group_name = :group_name;

Incremental extraction for a warehouse or Data Vault load is driven by the audit columns:

SELECT * FROM igs.igs_ru_group
WHERE  last_update_date >= :last_run_dt;

Reporting use cases include a rule-group inventory across the institution, impact analysis to identify groups touched by a configuration change, and reconciliation between rule groups and their assigned select groups or calls.

Related Objects

The following dependent objects reference IGS_RU_GROUP through documented foreign keys on the indicated columns.

• IGS_RU_NAMED_RULE — RUG_SEQUENCE_NUMBER → IGS_RU_GROUP.SEQUENCE_NUMBER; rule definitions scoped to a group.
• IGS_RU_GROUP_ITEM — RUG_SEQUENCE_NUMBER; individual items composing a group.
• IGS_RU_GROUP_SET — RUG_SEQUENCE_NUMBER; group-to-set membership.
• IGS_RU_NAMED_RULE_GR — three foreign keys: RUG_SEQUENCE_NUMBER, MESSAGE_GROUP, and SELECT_GROUP; associates named rules with groups, message groups, and select groups.
• IGS_RU_TURIN_RULE_GR — RUG_SEQUENCE_NUMBER; group linkage for Turín-style rules.
• IGS_RU_CALL — two foreign keys: RUG_SEQUENCE_NUMBER and SELECT_GROUP; rule calls that invoke a group or select a group during evaluation.

These relationships confirm the table's position as a reference hub for the IGS rule engine. Any modification to a rule-group row (particularly SEQUENCE_NUMBER) must be treated as high impact, since all six downstream tables resolve against it.