Results for “rug_sequence_number”

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

Overview

IGS_RU_GROUP_SET is a table within the IGS product family — the Oracle Student System module, now classified as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is Rule Group Set, indicating that the object was designed to associate individual rule groups with rule descriptions, thereby assembling the composite rule sets used by the Rules Engine of the Student System. In the ETRM metadata the table is explicitly reported as "Not implemented in this database," meaning that in many 12.1.1 and 12.2.2 environments the object exists only as a schema artifact or not at all, and no live transactional data resides in it. Administrators who search for igs_ru_group_set typically encounter it while reviewing legacy IGS schema definitions, upgrade scripts, or documentation rather than during active application processing.

Applying a heuristic Data Vault classification derived from the documented foreign-key structure, IGS_RU_GROUP_SET is best modeled as a link table. It carries no descriptive payload columns of its own beyond audit attributes, and its primary key is composed entirely of two foreign-key references — a classic many-to-many association (or "link") between the IGS_RU_GROUP and IGS_RU_DESCRIPTION entities. This modeling suggestion reflects the pure intersection nature of the table.

Key Information Stored

The physical schema documented under ETRM for 12.1.1 shows the owner as IGS with seven columns. Of these, only two are functional business columns; the remaining five are standard Oracle EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). The most important columns are:

• RUG_SEQUENCE_NUMBER — a foreign-key reference to IGS_RU_GROUP. It identifies the rule group participating in the set and forms the first component of the composite primary key.
• RUD_SEQUENCE_NUMBER — a foreign-key reference to IGS_RU_DESCRIPTION. It identifies the rule description linked to the group and forms the second component of the composite primary key.
• CREATED_BY / CREATION_DATE — standard audit fields recording the user and timestamp at row creation.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard audit fields capturing the last modification user, timestamp, and login session.

The surrogate primary key is named IGS_RU_GROUP_SET_PK and is defined over (RUG_SEQUENCE_NUMBER, RUD_SEQUENCE_NUMBER). The unique index IGS_RU_GROUP_SET_U1 covers the same column pair, and because the primary key itself is composed solely of foreign-key columns, the business key and the surrogate key coincide — a characteristic of intersection tables. There is no independent sequence-generated surrogate column documented.

Common Use Cases and Queries

Because the object is documented as obsolete and not implemented, practical querying is largely historical or diagnostic. Typical scenarios include auditing which rule descriptions are attached to which rule groups, verifying referential integrity during upgrades, and reconstructing rule-set definitions for legacy reporting. A representative join query pattern follows:

• SELECT gs.rug_sequence_number, gs.rud_sequence_number, g.group_name, d.description
FROM igs_ru_group_set gs, igs_ru_group g, igs_ru_description d
WHERE gs.rug_sequence_number = g.rug_sequence_number
AND gs.rud_sequence_number = d.rud_sequence_number;
• Integrity checks: identify orphaned rows where RUG_SEQUENCE_NUMBER or RUD_SEQUENCE_NUMBER no longer resolves to a parent record.
• Duplicate detection using the unique index columns to confirm no repeated group/description pair exists.

Reporting use cases center on enumerating the full composition of a rule group set for migration mapping to successor products, since the Student System module was superseded and its rule definitions must be exported before decommissioning.

Related Objects

The following objects are most significant in relation to IGS_RU_GROUP_SET, based on the documented foreign-key relationships:

• IGS_RU_GROUP — referenced via IGS_RU_GROUP_SET.RUG_SEQUENCE_NUMBER; the parent definition of each rule group.
• IGS_RU_DESCRIPTION — referenced via IGS_RU_GROUP_SET.RUD_SEQUENCE_NUMBER; the parent rule description.
• IGS_RU_GROUP_SET_PK — the primary-key constraint spanning both foreign-key columns.
• IGS_RU_GROUP_SET_U1 — the unique index enforcing business-key uniqueness on the same column pair.
• Related IGS rules-engine objects that consume group sets (rules, rule parameters, and rule assignments) are logical dependents, though they are not enumerated as direct FK relationships in the supplied metadata.

Because the metadata confirms the table is not implemented, related-object analysis should be treated as a schema-modeling reference rather than a guide to live data dependencies.