Search Results igs_ru_named_rule_n2

Overview

The IGS_RU_NAMED_RULE table is a core repository for defined business rules within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle Student Management) product family. It functions as the master table for storing the executable logic and configuration of named rules, which are reusable components that enforce institutional policies, validations, and automated decisions across student lifecycle processes. The table's role is to centralize rule definitions, enabling their association with rule groups and descriptions, and to optionally link them to specific system messages for user feedback.

Key Information Stored

The table's structure is designed to manage rule metadata and content. The primary identifier is RUL_SEQUENCE_NUMBER. The RUD_SEQUENCE_NUMBER column links the rule to its descriptive text in a related rule description table. The RUG_SEQUENCE_NUMBER is a critical foreign key that assigns the rule to a specific rule group, determining its context and execution scope. The MESSAGE_RULE column, as indicated by the user's search context, is a key field that stores an optional reference number to a system message, allowing the rule to return a predefined informational or error notification upon evaluation. The RULE_TEXT column, with a capacity of 2000 characters, holds the actual rule logic, typically written in a proprietary or PL/SQL-like syntax. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) complete the record for auditability.

Common Use Cases and Queries

This table is central to administrative tasks involving rule maintenance, troubleshooting, and impact analysis. A common use case is investigating rules associated with a specific system message or error code, which involves querying the MESSAGE_RULE column. For instance, to find all rules that might trigger a particular message, one would query: SELECT rul_sequence_number, rule_text FROM igs.igs_ru_named_rule WHERE message_rule = <message_number>;. Another frequent scenario is auditing all rules within a specific rule group for review or deployment: SELECT * FROM igs.igs_ru_named_rule WHERE rug_sequence_number = <group_id> ORDER BY rul_sequence_number;. Reporting on rule creation and modification is also standard, utilizing the WHO columns to track changes over time.

Related Objects

Based on the provided dependency and index information, the IGS_RU_NAMED_RULE table has defined relationships with other rule configuration entities. The primary key (RUL_SEQUENCE_NUMBER) is referenced by other objects within the APPS schema. The non-unique indexes on RUD_SEQUENCE_NUMBER (IGS_RU_NAMED_RULE_N1), RUG_SEQUENCE_NUMBER (IGS_RU_NAMED_RULE_N3), and MESSAGE_RULE (IGS_RU_NAMED_RULE_N2) indicate foreign key relationships to tables storing rule descriptions, rule groups, and system messages, respectively. While the specific parent table names are not listed in the excerpt, a logical data model would include tables such as IGS_RU_RULE_DESC (for RUD_SEQUENCE_NUMBER), IGS_RU_RULE_GROUP (for RUG_SEQUENCE_NUMBER), and a message catalog table (for MESSAGE_RULE). These relationships are essential for joining descriptive and contextual data to the core rule definition.