Results for “igs_ps_usec_ru”

50+ results




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

Overview

IGS.IGS_PS_USEC_RU is a table in the Oracle E-Business Suite Student System (IGS) product family. Per the ETRM documentation, it stores Unit Section Version Rules. In the Oracle Student System data model, a "unit section version" represents a specific deliverable instance of a unit offering option — the teachable, schedulable version of a course offering that students actually enrol into. This table binds such a version to the rule engine that governs it, recording which rule call is invoked and at what sequence within the rule set the call is evaluated.

The table therefore acts as a configuration and control structure rather than a transactional log. It determines, for a given unit section version, the ordered execution of rule calls used for validation, eligibility, or derivation logic. Because it links a version entity to two independent rule-engine reference entities, the metadata's heuristic Data Vault classification of link is consistent with its shape: it is a relationship table resolving associations between offerings and rules, not a descriptive hub or a time-variant satellite. That classification should be treated as a modeling suggestion rather than a functional statement.

Key Information Stored

The table is documented with nine columns in the 12.1.1 physical schema. The most significant are:

The distinction is important operationally: USECRU_ID is the technical row identifier used by foreign references and by the ORM layer, whereas UOO_ID plus S_RULE_CALL_CD is the business key that expresses the real-world assertion "this version invokes this rule call."

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include determining which rule calls are attached to a unit section version, checking rule sequencing for a term's offerings, and auditing recently modified rule bindings. A representative query joining to the call and rule tables:

  • SELECT u.USECRU_ID, u.UOO_ID, u.S_RULE_CALL_CD, u.RUL_SEQUENCE_NUMBER FROM IGS.IGS_PS_USEC_RU u WHERE u.UOO_ID = :p_uoо_id ORDER BY u.RUL_SEQUENCE_NUMBER;
  • A duplicate-detection check relying on the business key: group by UOO_ID, S_RULE_CALL_CD and flag counts greater than one, although the unique index IGS_PS_USEC_RU_U2 should prevent this in normal operation.
  • An audit query filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration changes made during an admissions or enrolment cycle.
  • A coverage report that outer-joins from IGS_PS_UNIT_OFR_OPT_ALL to identify versions with no configured rule calls.

Because the table is configuration-oriented, extract-and-compare patterns (version-to-version or environment-to-environment) are more common than high-volume transactional reporting.

Related Objects

The following objects are documented as directly related through the FK relationships or as the referencing parent of this table's primary key:

  • IGS_RU_RULE — referenced via IGS_PS_USEC_RU.RUL_SEQUENCE_NUMBER; supplies the rule definition.
  • IGS_RU_CALL — referenced via IGS_PS_USEC_RU.S_RULE_CALL_CD; supplies the callable rule routine.
  • IGS_PS_UNIT_OFR_OPT_ALL — referenced via IGS_PS_USEC_RU.UOO_ID; the unit offering option / section version parent.
  • IGS_PS_UNIT_OFR_OPT_ALL (second documented relationship) — again via UOO_ID, per the ETRM FK listing.
  • Index IGS_PS_USEC_RU_PK / IGS_PS_USEC_RU_U1 on USECRU_ID and IGS_PS_USEC_RU_U2 on (UOO_ID, S_RULE_CALL_CD) — these enforce identity and business-key uniqueness and are the principal supporting structures for query access paths.

Any dependent child table that stores USECRU_ID as a foreign key would extend this link, but no such child is documented in the supplied metadata.