Results for “igs_en_unit_set_rule”

39 results




Overview
Explore in AI Chat

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

Overview

IGS_EN_UNIT_SET_RULE is a configuration table within the Oracle E-Business Suite IGS — Student System product family, which Oracle has since classified as obsolete. The entity describes the unit set rules that govern how a unit set — a curated grouping of academic units or modules — is assembled, validated, and sequenced within an academic program. In the historical ETRM (EBS Technical Reference Manual) documentation for release 12.1.1, the table is listed as not implemented in this database, meaning the physical object is documented for reference but is absent from the delivered 12.1.1 schema. Despite this status, the metadata preserves its full structural definition, including its primary key, unique index, foreign keys, and complete column list, allowing technical consultants to reason about it when performing legacy analysis or upgrade assessments.

Under the heuristic Data Vault classification mined from its foreign key structure, IGS_EN_UNIT_SET_RULE is modelled as a link table. This classification is a modelling suggestion: the table does not hold descriptive attribute history but instead resolves the many-to-many associations between unit set definitions and the rule-call routines that apply to them. It sits at the intersection of the unit set hierarchy and the rules engine, functioning as an association entity rather than a transactional hub or satellite.

Key Information Stored

The table contains nine documented columns, of which the following are the most significant for functional and technical analysis:

The surrogate primary key is defined by the index IGS_EN_UNIT_SET_RULE_PK, comprising the composite of UNIT_SET_CD, VERSION_NUMBER, and S_RULE_CALL_CD. A separate unique index, IGS_EN_UNIT_SET_RULE_U1, covers the same three columns, making them simultaneously the business-key candidate and the uniqueness guarantee for the entity. The primary key is therefore composite and natural rather than a generated sequence identifier.

Common Use Cases and Queries

Because the table is obsolete and not implemented in the current database, its principal use cases relate to historical data migration, legacy interface analysis, and documenting the rules framework of the Student System. A typical query pattern joins the table back to its parent unit set and rule definitions:

  • Retrieving all rules for a given unit set version: SELECT S_RULE_CALL_CD, RUL_SEQUENCE_NUMBER FROM IGS_EN_UNIT_SET_RULE WHERE UNIT_SET_CD = :unit_set AND VERSION_NUMBER = :version ORDER BY RUL_SEQUENCE_NUMBER;
  • Resolving rule definitions through IGS_RU_RULE and rule calls through IGS_RU_CALL to display human-readable rule text.
  • Reporting on rule sequencing conflicts where multiple rules share a sequence position within the same unit set version.
  • Auditing changes using the WHO columns to determine when a rule association was last modified.

Related Objects

The foreign key metadata identifies three direct parents, each joined on a documented column:

  • IGS_EN_UNIT_SET_ALL — joined on UNIT_SET_CD and VERSION_NUMBER; the master unit set definition.
  • IGS_RU_RULE — joined on RUL_SEQUENCE_NUMBER; the rule definition supplying sequencing and rule metadata.
  • IGS_RU_CALL — joined on S_RULE_CALL_CD; the callable routine executed for the rule.

These three parents constitute the complete documented relationship set for the object. Together they establish the table as the binding link between the unit set structural hierarchy and the rules engine implemented via the IGS_RU_* family of tables.