Results for “igs_ru_group_item”

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

Overview

IGS_RU_GROUP_ITEM is a transactional detail table within the Oracle E-Business Suite Student System (IGS) product family, specifically belonging to the Rules Engine (RU) component. It stores the individual line-level items that constitute a rules group, with each record representing one discrete description entry associated with a parent rules group defined in IGS_RU_GROUP. The table functions as the child side of a one-to-many relationship between a rules group header and its member items, and it is registered in the ETRM repository under the IGS schema with a VALID status.

From a dimensional modeling perspective, the ETRM Data Vault classification heuristic marks this object as satellite-leaning. In practice, this means IGS_RU_GROUP_ITEM is best modeled as a satellite attached to a hub or link represented by its parent IGS_RU_GROUP table. The descriptive attributes (description type, description number, audit columns) are the kind of non-key, descriptive payload typical of a satellite table, while the parent sequence number serves as the link back to the hub.

Key Information Stored

The documented physical schema comprises eight columns. The composition of the primary key is central to understanding the table's grain:

• RUG_SEQUENCE_NUMBER — Part of the composite primary key and the foreign key referencing IGS_RU_GROUP. This column identifies the parent rules group to which the item belongs.
• DESCRIPTION_TYPE — Part of the composite primary key. Classifies the kind of description carried by the item, allowing multiple description categories per group.
• DESCRIPTION_NUMBER — Part of the composite primary key. Identifies the specific description value or reference tied to the item.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns that record who created and last modified the row, when, and through which session.

The surrogate primary key IGS_RU_GROUP_ITEM_PK is defined over the three-column combination of RUG_SEQUENCE_NUMBER, DESCRIPTION_TYPE, and DESCRIPTION_NUMBER. A separate unique index, IGS_RU_GROUP_ITEM_U1, is documented over DESCRIPTION_NUMBER, DESCRIPTION_TYPE, and RUG_SEQUENCE_NUMBER — the same attribute set in a different column order. This index is a business-key candidate, indicating that the combination of parent group, description type, and description number must remain unique within the table. The absence of a system-generated single-column surrogate identifier means joins to this table must always be expressed through the three business columns.

Common Use Cases and Queries

Typical reporting and integration scenarios resolve the members of a given rules group and their associated description entries. A standard pattern joins the detail table back to its parent header:

• List all items for a specific group: SELECT i.description_type, i.description_number FROM igs.igs_ru_group_item i WHERE i.rug_sequence_number = :group_seq;
• Resolve a group and its items together: SELECT g.*, i.* FROM igs.igs_ru_group g, igs.igs_ru_group_item i WHERE g.rug_sequence_number = i.rug_sequence_number;
• Audit change activity: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently modified rule group items for reconciliation or troubleshooting.
• Detect duplicate description entries: group by the unique-key columns and count to confirm the uniqueness enforced by IGS_RU_GROUP_ITEM_U1.

Because the table is a rules engine detail table, it is frequently consumed by validation and eligibility processes rather than by end-user transactional screens. Reporting extracts commonly feed curriculum rules, admissions rule evaluation, and configuration migration scripts.

Related Objects

The following objects are the most significant in relation to IGS_RU_GROUP_ITEM:

• IGS_RU_GROUP — Parent rules group header table. Joined on IGS_RU_GROUP_ITEM.RUG_SEQUENCE_NUMBER = IGS_RU_GROUP.RUG_SEQUENCE_NUMBER. This is the only documented foreign key reference and the anchor of the satellite relationship.
• IGS_RU_GROUP_ITEM_PK — Primary key constraint over (RUG_SEQUENCE_NUMBER, DESCRIPTION_TYPE, DESCRIPTION_NUMBER).
• IGS_RU_GROUP_ITEM_U1 — Unique business-key index over (DESCRIPTION_NUMBER, DESCRIPTION_TYPE, RUG_SEQUENCE_NUMBER).
• Related IGS rules engine tables that share the RUG_SEQUENCE_NUMBER grouping convention, which typically participate in the same rule evaluation flow as this detail table.
• Standard EBS audit and concurrency APIs that populate the CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN columns.

Because the ETRM metadata documents only one foreign key, integrators should verify additional dependencies against the live IGS schema before building production joins.