Search Results igs_pr_rule_all




Overview
Explore in AI Chat

Overview

The IGS_PR_RULE_ALL table is a core data object within the Oracle E-Business Suite's now-obsolete Student System (IGS) module. It serves as the master repository for defining standard progression rules. A progression rule is a configurable business rule that governs a student's academic advancement, typically based on criteria like grade performance, unit completion, or attendance. The table's purpose is to store the rule's definition and metadata, which can then be applied to various academic elements within the system. As indicated by the "_ALL" suffix, it is a multi-org table designed to store data partitioned by operating unit, supporting deployments with multiple institutions or legal entities.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies each rule. The key columns are PROGRESSION_RULE_CAT and PROGRESSION_RULE_CD, which together form a unique rule identifier, likely representing a rule category and a specific code within that category. While the specific descriptive columns are not detailed in the provided metadata, a table of this nature would typically store attributes such as the rule's effective dates, status (active/inactive), a descriptive name, the rule type (e.g., exclusion, probation, warning), and the logical conditions or parameters that define the rule's logic. The critical function of this table is to act as a reusable template; the rule itself is enforced through its application to specific entities.

Common Use Cases and Queries

The primary use case involves the administration and application of progression rules. System administrators would use this table to create, query, or modify the standard rule definitions. Common operational queries would include listing all active rules for a given category or retrieving a specific rule's definition for review. A typical reporting use case is to analyze which rules are applied across the student population. A fundamental query pattern involves joining this table to its application table to see where rules are in effect.

SELECT rule.progression_rule_cat,
       rule.progression_rule_cd,
       appl.application_type,
       appl.reference_code
FROM igs_pr_rule_all rule,
     igs_pr_ru_appl_all appl
WHERE rule.progression_rule_cat = appl.progression_rule_cat
  AND rule.progression_rule_cd = appl.progression_rule_cd
  AND rule.rule_status = 'ACTIVE';

Related Objects

The IGS_PR_RULE_ALL table has a direct and critical relationship with the IGS_PR_RU_APPL_ALL table, as documented by the foreign key. This relationship is how a defined rule is linked to a specific system element for enforcement.

  • IGS_PR_RU_APPL_ALL: This is the rule application table. It records instances where a specific progression rule from IGS_PR_RULE_ALL is applied to an allowable system element, such as a course version, course type, organizational unit, or an individual student's course attempt. The join is performed on the composite key: IGS_PR_RU_APPL_ALL.PROGRESSION_RULE_CAT = IGS_PR_RULE_ALL.PROGRESSION_RULE_CAT and IGS_PR_RU_APPL_ALL.PROGRESSION_RULE_CD = IGS_PR_RULE_ALL.PROGRESSION_RULE_CD.

It is important to note the provided ETRM metadata explicitly states this table is "Not implemented in this database," indicating it may be a reference or legacy structure in some installations.