Results for “message_group”

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

Overview

The view IGS_RU_CALL_GROUP_V is a database object belonging to the Oracle IGS (Student System) product family. In the Oracle E-Business Suite release 12.1.1 and 12.2.2 environment, IGS is documented as an obsolete module, which means the object is preserved primarily for backward compatibility and reference rather than for active functional deployment. The ETRM metadata describes the view as a "New view of rule groups." Within the broader IGS rules engine architecture, a rule group is a logical container that binds together named rules and controls how those rules are invoked at runtime, including which select group and message group govern their evaluation.

The view presents a denormalized, read-friendly projection over the underlying named rule group table. Its role in reporting and integration is to expose rule group configuration — name, group code, description, return type, evaluation sequence, and group routing attributes — as a single queryable surface. Consultants who search for the token "select_group" typically encounter this view because SELECT_GROUP is one of its exposed columns. The view therefore serves as the natural join point when tracing how a rule resolves its applicable selection criteria.

Underlying Base Objects

According to the documented view text, IGS_RU_CALL_GROUP_V is defined over a single base object: IGS_RU_NAMED_RULE_GR (aliased NRG in the view SQL). The view is a straightforward SELECT of columns from that table with no aggregation, join, or filter clauses, so it functions as a column-remapping and aliasing layer.

This relationship has a practical consequence: the view inherits the row cardinality, uniqueness, and constraints of IGS_RU_NAMED_RULE_GR. Any DML performed against the base table is immediately visible through the view, and no additional performance penalty is introduced beyond ordinary SQL parsing. Because the metadata notes the object is "Not implemented in this database" in some environments, availability must be verified against the specific instance before the view is referenced in custom code. Where the underlying table exists, the view can be treated as a stable access path.

Key Columns

• NAME_CD — the name code of the named rule group; maps to S_RULE_CALL_CD and S_RULE_TYPE_CD in the documented column list.
• GROUP_CD — the group code that classifies the rule group.
• DESCRIPTION — descriptive text for the rule group, surfaced as RULE_DESCRIPTION.
• S_RETURN_TYPE — the return type expected from the rule group evaluation.
• RUG_SEQUENCE_NUMBER — controls the ordering in which rule groups are processed.
• SELECT_GROUP — the selection group assignment for the rule, central to queries using the "select_group" search token.
• MESSAGE_GROUP — the message group used to surface validation or outcome messages.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle audit columns inherited from the base table.

Common Use Cases and Queries

The primary use case is configuration reporting: identifying which rule groups are bound to a given selection group or message group, and in what sequence they evaluate. A representative query lists group configuration ordered by evaluation sequence:

SELECT name_cd, group_cd, description, s_return_type, select_group, message_group FROM igs_ru_call_group_v ORDER BY rug_sequence_number;

A second common pattern filters by selection group to enumerate the rules sharing that routing attribute:

SELECT name_cd, rug_sequence_number, s_return_type FROM igs_ru_call_group_v WHERE select_group = :p_select_group;

A third scenario supports impact analysis and auditing, joining the view back to the base table to confirm that the view exposes the expected rows. Because the view carries audit columns, it also supports "changed since" queries for migration or reconciliation work. Given the obsolete status of the IGS module, these queries are most appropriate for legacy data extraction, historical analysis, or pre-upgrade assessment rather than new functional development.