Search Results igs_ps_ver_ru

Overview

The IGS_PS_VER_RU table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS), specifically designed to manage program version rules. It functions as a junction table that establishes a formal relationship between a specific academic program version and the business rules that govern its administration. This table is critical for enforcing complex academic policies, prerequisites, and progression requirements at the version level of a course or program. The metadata explicitly notes the product module as "Obsolete," indicating this table is part of a legacy architecture within the IGS suite that may have been superseded in later designs or implementations. Furthermore, the documentation states it is "Not implemented in this database," which suggests the table's structure is defined but may not be populated or actively used in a standard deployment, or it may exist for reference or migration purposes only.

Key Information Stored

The table's primary key uniquely identifies a rule assignment through a composite of three columns, linking it directly to a specific program version and a rule type. The most significant columns include COURSE_CD and VERSION_NUMBER, which together identify the precise academic program version. The S_RULE_CALL_CD column stores a code that specifies the type or category of rule being applied (e.g., admission, progression, completion). The RUL_SEQUENCE_NUMBER column is a foreign key that points to the specific rule definition and its detailed logic within the rule engine (IGS_RU_RULE table). This structure allows a single program version to be associated with multiple rules of different call types.

Common Use Cases and Queries

The primary use case is to query all business rules applicable to a given program version for validation engines, audit reports, or student self-service portals. For instance, an application process might query this table to determine which admission rules to evaluate for a specific course version. A common reporting query would join to the program version and rule definition tables to list active rules. Due to the "Obsolete" and "Not implemented" status, direct operational use in newer environments is unlikely. However, understanding its structure is vital for data migration, historical reporting, or supporting legacy customizations. A typical analytical SQL pattern would be: SELECT pv.course_cd, pv.version_number, rc.meaning AS rule_call, ru.rule_text FROM igs_ps_ver_ru ru JOIN igs_ps_ver_all pv ON (ru.course_cd = pv.course_cd AND ru.version_number = pv.version_number) JOIN igs_ru_call rc ON ru.s_rule_call_cd = rc.s_rule_call_cd WHERE pv.course_cd = :p_course;

Related Objects

The table maintains defined foreign key relationships with several core IGS tables, as documented in the metadata:

• IGS_PS_VER_ALL: The parent table for program versions. The join is on (COURSE_CD, VERSION_NUMBER). This relationship ensures every rule is attached to a valid, existing program version.
• IGS_RU_RULE: The master table for rule definitions. The join is on RUL_SEQUENCE_NUMBER, linking the assignment to the actual rule logic and text.
• IGS_RU_CALL: The reference table for rule call types. The join is on S_RULE_CALL_CD, providing the meaning and context for the type of rule being applied (e.g., 'ADM' for Admission).

These relationships position IGS_PS_VER_RU as a central hub connecting the academic catalog (program versions) with the rule engine infrastructure.