Search Results cst_sequence_number




Overview
Explore in AI Chat

Overview

The IGS_PS_STAGE_RU table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Student Administration (SA) module under the IGS (iGrants) schema. Its primary function is to capture and manage the rules associated with program stages. In the context of academic program management, a program (COURSE_CD) is often broken down into distinct calendar stages (CST_SEQUENCE_NUMBER). This table establishes the linkage between these stages and the specific business rules (S_RULE_CALL_CD, RUL_SEQUENCE_NUMBER) that govern progression, validation, or other processes within that stage. It serves as a critical junction table for enforcing academic policy and workflow logic at the program stage level.

Key Information Stored

The table's structure is designed to uniquely identify a rule for a specific stage of a specific program version. The key columns are:

  • COURSE_CD and VERSION_NUMBER: Together, these uniquely identify the academic program.
  • CST_SEQUENCE_NUMBER: A unique identifier for the calendar stage within the program. This is the column referenced in the user's search, indicating its importance as a foreign key to a calendar stage definition table.
  • S_RULE_CALL_CD and RUL_SEQUENCE_NUMBER: Together, these uniquely identify the specific rule code and its sequence that applies to the program stage.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): For auditing and tracking data changes.

The unique index IGS_PS_STAGE_RU_U1 enforces the primary key constraint on the combination of COURSE_CD, VERSION_NUMBER, CST_SEQUENCE_NUMBER, and S_RULE_CALL_CD.

Common Use Cases and Queries

This table is central to queries that analyze or report on the rule configuration for academic programs. A common use case is auditing all rules attached to the stages of a specific program. For example, to retrieve all stage rules for a program 'BSC_CS', version 1, one would execute:

SELECT * FROM apps.IGS_PS_STAGE_RU WHERE course_cd = 'BSC_CS' AND version_number = 1 ORDER BY cst_sequence_number;

Another critical use case involves impact analysis when a rule is changed or deactivated. To find all program stages that reference a particular rule call code 'ENROLL_CHK', the following query is typical:

SELECT course_cd, version_number, cst_sequence_number FROM apps.IGS_PS_STAGE_RU WHERE s_rule_call_cd = 'ENROLL_CHK';

Integration and data migration scripts also frequently query this table to extract or validate stage-rule relationships for a given set of programs.

Related Objects

Based on the provided metadata, the IGS_PS_STAGE_RU table is referenced by the APPS synonym of the same name (APPS.IGS_PS_STAGE_RU), which is the standard access point for all EBS application code. While explicit foreign key relationships are not detailed in the excerpt, the column semantics strongly imply relationships to other key tables in the IGS schema:

  • COURSE_CD, VERSION_NUMBER: Likely references a program definition table (e.g., IGS_PS_VER).
  • CST_SEQUENCE_NUMBER: Must reference a primary key in a calendar stage table (e.g., IGS_CA_STAGE).
  • S_RULE_CALL_CD, RUL_SEQUENCE_NUMBER: Likely references a rule definition table (e.g., IGS_RU_CALL).

The non-unique indexes on S_RULE_CALL_CD (N1) and RUL_SEQUENCE_NUMBER (N2) are optimized for queries that filter or join based on these rule identifiers.