Search Results IGS_PS_STAGE_RU




Overview
Explore in AI Chat

Overview

The IGS_PS_STAGE_RU table is a core data entity within the Oracle E-Business Suite Student System (IGS). It functions as a junction table that establishes and manages the linkage between academic program stages and the business rules that govern them. In the context of program progression, a stage represents a defined phase or milestone within a course of study. This table's role is to associate one or more specific rules—such as prerequisites, co-requisites, or progression requirements—to a particular stage of a program. This enables the automated enforcement of complex academic policies, ensuring students meet the necessary criteria before advancing to subsequent stages of their program.

Key Information Stored

The table's structure is designed to uniquely identify a rule assignment for a program stage through its primary key and to maintain referential integrity through foreign keys. The critical columns are:

  • COURSE_CD, VERSION_NUMBER, CST_SEQUENCE_NUMBER: These columns form part of the composite primary key and foreign key to the IGS_PS_STAGE table. They uniquely identify the specific program (course and version) and the sequence number of the stage within that program to which a rule is attached.
  • S_RULE_CALL_CD: Completes the primary key and is a foreign key to IGS_RU_CALL. This code identifies the type or category of the rule being invoked (e.g., a prerequisite check, a unit set rule).
  • RUL_SEQUENCE_NUMBER: A foreign key to the IGS_RU_RULE table. This column stores the identifier that points to the specific rule definition detailing the condition or logic to be evaluated.

Common Use Cases and Queries

This table is central to academic rule processing. A primary use case is during student enrollment or progression checking, where the system queries for all rules attached to a student's current or target program stage to validate eligibility. Administrators use interfaces tied to this table to maintain stage-specific requirements. Common reporting queries involve listing all rules for a program or analyzing rule assignments across different program versions. A typical SQL pattern to retrieve rule details for a stage would be:

SELECT stg.*, ru.rule_cd, call.s_rule_call_cd
FROM igs_ps_stage_ru ru_link,
igs_ps_stage stg,
igs_ru_rule ru,
igs_ru_call call
WHERE ru_link.course_cd = stg.course_cd
AND ru_link.version_number = stg.version_number
AND ru_link.cst_sequence_number = stg.sequence_number
AND ru_link.rul_sequence_number = ru.rul_sequence_number
AND ru_link.s_rule_call_cd = call.s_rule_call_cd
AND stg.course_cd = :p_course_cd
AND stg.version_number = :p_version_number;

Related Objects

The IGS_PS_STAGE_RU table maintains documented foreign key relationships with three key entities in the Student System, as per the provided metadata:

  • IGS_PS_STAGE: Defines the program stage itself. The join is on the composite key of COURSE_CD, VERSION_NUMBER, and CST_SEQUENCE_NUMBER.
  • IGS_RU_RULE: Stores the master definition of the business rule's logic and conditions. The join is on the RUL_SEQUENCE_NUMBER column.
  • IGS_RU_CALL: Defines the valid types or callings for a rule. The join is on the S_RULE_CALL_CD column, which categorizes the rule's purpose within the stage context.