Results for “true_message”

5 results




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

Overview

IGS_RU_CALL is a core configuration table in the Oracle EBS Student System (IGS) product family, documented in ETRM as "Rule call name." It resides in the IGS schema and holds the definitions of the rule calls that drive the institution's rules engine — the mechanism by which the Student System decides which validation, derivation, or processing logic to invoke for a given academic entity. Each row names a rule call, ties it to a rule type, an optional rule description, and one or more rule groups, and provides the messages and default behavior returned to the calling process.

The table participates in a classic hub-style reference pattern. Heuristic Data Vault classification mined from the foreign-key structure labels IGS_RU_CALL as hub-leaning, so a dimensional modeler should treat it as the business hub of rule-call identity, with the description and group tables acting as outriggers and the many dependent transactional tables acting as satellites and links that reference the hub by rule call code.

Key Information Stored

The physical schema documented for 12.1.1 contains 13 columns; the columns listed below carry the functional weight:

No descriptive name column is documented beyond the rule type and description references, so S_RULE_CALL_CD itself is the human-recognizable identifier used throughout the application.

Common Use Cases and Queries

Because IGS_RU_CALL is the reference point for rule calls, most queries either validate that a code exists or resolve a code into its group, type, and messages for troubleshooting. A typical lookup is:

  • SELECT c.s_rule_call_cd, c.s_rule_type_cd, c.true_message, c.false_message, c.default_rule FROM igs.igs_ru_call c WHERE c.s_rule_call_cd = :code;
  • Joining to IGS_RU_GROUP on both RUG_SEQUENCE_NUMBER and SELECT_GROUP to reproduce the group context of a rule call.
  • Joining to IGS_RU_DESCRIPTION via RUD_SEQUENCE_NUMBER to retrieve the narrative description for documentation or audit reports.
  • Reverse-impact analysis: querying the dependent tables (see below) for a rule call code before changing or retiring it.
  • Reporting on rule call inventory by S_RULE_TYPE_CD to identify duplicate or unused calls, and auditing LAST_UPDATE_DATE to detect configuration drift between environments.

Related Objects

The FK metadata identifies two outbound reference targets and eight inbound dependents:

  • IGS_RU_DESCRIPTION — joined via IGS_RU_CALL.RUD_SEQUENCE_NUMBER for rule descriptive text.
  • IGS_RU_GROUP — joined via IGS_RU_CALL.RUG_SEQUENCE_NUMBER and IGS_RU_CALL.SELECT_GROUP for rule grouping.
  • IGS_EN_CPD_EXT_ALL — references IGS_RU_CALL.S_RULE_CALL_CD on its own S_RULE_CALL_CD column (continuing professional development extensions).
  • IGS_PS_STAGE_RU and IGS_PS_VER_RU — program stage and program version rules that call this table by S_RULE_CALL_CD.
  • IGS_FI_FEE_DSB_FM_RU — fee disbursement rule calls.
  • IGS_PR_RU_CAT — prospect/recruitment rule category calls.
  • IGS_PS_USEC_RU, IGS_EN_UNIT_SET_RULE, and IGS_PS_UNIT_VER_RU — usec, unit set, and unit version rule calls that reference S_RULE_CALL_CD.

These inbound references confirm that IGS_RU_CALL is a widely shared configuration hub; any change to a rule call code propagates to program, fee, recruitment, and unit-level rule processing across the Student System.