Results for “igs_ps_unit_ver_ru”

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

Overview

IGS_PS_UNIT_VER_RU is a table in the IGS schema (the Oracle Student System product) that stores unit version rules. In Oracle E-Business Suite 12.1.1 and 12.2.2, it associates a specific version of an academic unit with the rule logic that governs how that version behaves. Each row links a unit-version combination to a rule call, which in turn resolves to an executable rule definition.

Based on the foreign-key structure mined from the metadata, this object is heuristically classified as a link in Data Vault terms. It does not appear to hold descriptive attributes about a single business entity; instead, it resolves a many-to-many association between unit versions and rules. The link connects unit version identity (UNIT_CD, VERSION_NUMBER) to rule call identity (S_RULE_CALL_CD), while a sequence number positions the rule within the version's rule set.

Key Information Stored

The table contains nine documented columns. The most significant are:

• UNIT_CD — the unit code identifying the academic unit.
• VERSION_NUMBER — the version of that unit to which the rule applies.
• S_RULE_CALL_CD — the rule call code, which identifies the rule invocation to be executed against the unit version.
• RUL_SEQUENCE_NUMBER — controls the ordering of the rule relative to other rules attached to the same unit version.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified each row.

The primary key is IGS_PS_UNIT_VER_RU_PK, defined on the composite of UNIT_CD, VERSION_NUMBER, and S_RULE_CALL_CD. A unique index, IGS_PS_UNIT_VER_RU_U1, is defined on the same three columns, making that combination the business-key candidate. Because the primary key is a natural composite rather than a generated surrogate, the table has no separate system-assigned identifier column.

Three foreign keys enforce integrity. RUL_SEQUENCE_NUMBER references IGS_RU_RULE; S_RULE_CALL_CD references IGS_RU_CALL; and the pair UNIT_CD plus VERSION_NUMBER references IGS_PS_UNIT_VER_ALL. The last relationship anchors each rule row to a valid unit version record.

Common Use Cases and Queries

Typical usage centers on determining which rules apply to a given unit version and in what order they execute during enrollment, assessment, or progression processing.

• Retrieve all rules attached to a unit version, ordered by sequence:

  SELECT rul_sequence_number, s_rule_call_cd
  FROM   igs.igs_ps_unit_ver_ru
  WHERE  unit_cd = :unit_cd
  AND    version_number = :version_number
  ORDER BY rul_sequence_number;

• Join to rule definitions to obtain rule detail:

  SELECT ru.rul_sequence_number, rc.rule_call_cd, r.rule_description
  FROM   igs.igs_ps_unit_ver_ru ru,
         igs.igs_ru_call rc,
         igs.igs_ru_rule r
  WHERE  ru.s_rule_call_cd = rc.rule_call_cd
  AND    ru.rul_sequence_number = r.rule_sequence_number
  AND    ru.unit_cd = :unit_cd;

• Identify every unit version that invokes a particular rule, useful for impact analysis before modifying rule logic.
• Validate rule configuration by comparing rule coverage across unit versions, or by detecting gaps where expected rules are missing.

Related Objects

The most significant related objects, based on documented relationships, are:

• IGS_PS_UNIT_VER_ALL — parent table of unit versions; joined on UNIT_CD and VERSION_NUMBER.
• IGS_RU_CALL — rule call definitions; joined on S_RULE_CALL_CD.
• IGS_RU_RULE — rule definitions; joined on RUL_SEQUENCE_NUMBER.
• IGS_PS_UNIT_VER — unit version base data, consulted to validate version context.
• Rule engine and enrollment processing programs that read this table to resolve executable rules for a unit version.

These objects together form the rule-linking layer of the Student System's unit version configuration.