Results for “igs_ru_rule”

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

Overview

IGS_RU_RULE is the master repository for rules within the Oracle E-Business Suite Student System (IGS) product family. The table name derives from the IGS "RU" (Rules) schema component, and it functions as the central definition point from which rule identifiers are propagated to admissions, enrollment, financial aid, student records, and progression subsystems. Each row represents a discrete rule entity that can be referenced by downstream transactional and setup tables through the SEQUENCE_NUMBER surrogate key.

From a Data Vault modeling perspective, the FK structure mined from the ETRM metadata classifies IGS_RU_RULE as hub-leaning. This suggests IGS_RU_RULE behaves as a hub: a stable, insert-once anchor for a business concept (a rule) whose descriptive attributes and contextual relationships are distributed across surrounding satellites and link tables. The 6-column physical footprint is consistent with a hub-style table that holds primarily identity and audit columns rather than extensive descriptive payload.

Key Information Stored

The documented 12.1.1 physical schema exposes six columns, with two serving as the core identity and audit anchors:

• SEQUENCE_NUMBER — The primary key column, backed by the unique index IGS_RU_RULE_U1 and the IGS_RU_RULE_PK constraint. This is the surrogate key referenced by every foreign-key relationship in the metadata, making it the single most important column for joins.
• CREATED_BY — Audit column capturing the application user who created the rule row.
• CREATION_DATE — Timestamp of initial row creation.
• LAST_UPDATED_BY — Audit column identifying the most recent modifier of the row.
• LAST_UPDATE_DATE — Timestamp of the most recent modification, frequently used in incremental ETL and change-detection queries.
• LAST_UPDATE_LOGIN — Session-level login identifier associated with the last update, useful for forensic and audit reporting.

SEQUENCE_NUMBER is both the surrogate primary key and the unique business-key candidate (IGS_RU_RULE_U1), indicating that in the documented 12.1.1 ETRM representation the surrogate and business key coincide. Downstream tables reference it either as RUL_SEQUENCE_NUMBER, RULE_SEQUENCE_NUMBER, SCOPE_RUL_SEQUENCE_NUM, MESSAGE_RULE, or RULE_NUMBER, depending on the consuming module.

Common Use Cases and Queries

The dominant use case is resolving rule definitions across modules. Typical query patterns join IGS_RU_RULE to the many dependent tables that carry a rule foreign key. Representative examples include:

• Joining IGS_RU_ITEM on RUL_SEQUENCE_NUMBER to retrieve the individual items that compose a rule.
• Joining IGS_RU_NAMED_RULE on RUL_SEQUENCE_NUMBER to resolve human-readable rule names, and on MESSAGE_RULE to resolve associated message text.
• Joining IGS_PS_VER_RU and IGS_PS_STAGE_RU on RUL_SEQUENCE_NUMBER to determine rule applicability at program version and stage levels.
• Joining IGS_FI_FEE_AS_ITEMS or IGS_FI_FEE_TYPE_CI_H_ALL on SCOPE_RUL_SEQUENCE_NUM to resolve fee scope rules for financial aid and fee assessment.

A representative pattern is: SELECT r.SEQUENCE_NUMBER, n.RUL_NAME FROM IGS_RU_RULE r, IGS_RU_NAMED_RULE n WHERE r.SEQUENCE_NUMBER = n.RUL_SEQUENCE_NUMBER. Reporting scenarios include auditing rule proliferation (count of dependent rows per rule), identifying orphaned rules with no downstream references, and tracking rule creation trends using CREATION_DATE and LAST_UPDATE_DATE for change-data-capture pipelines.

Related Objects

The ETRM relationship data identifies eighteen dependent objects. The most significant, grouped by functional area, are:

• Rule composition and naming — IGS_RU_ITEM (RUL_SEQUENCE_NUMBER, RULE_NUMBER) and IGS_RU_NAMED_RULE (RUL_SEQUENCE_NUMBER, MESSAGE_RULE), which together define the content and label of a rule.
• Program and curriculum rules — IGS_PS_VER_RU, IGS_PS_STAGE_RU, IGS_PS_UNIT_VER_RU, IGS_PS_USEC_RU, and IGS_EN_UNIT_SET_RULE, all keyed on RUL_SEQUENCE_NUMBER, controlling version, stage, unit, and unit-set rule application.
• Admissions and enrollment — IGS_AD_APCTR_RU_ALL (RUL_SEQUENCE_NUMBER) and IGS_EN_CPD_EXT_ALL (RUL_SEQUENCE_NUMBER) for admission category and enrollment extension rules.
• Financial aid and fees — IGS_FI_FEE_AS_ITEMS (SCOPE_RUL_SEQUENCE_NUM), IGS_FI_FEE_TYPE_CI_H_ALL (SCOPE_RUL_SEQUENCE_NUM), IGS_FI_F_CAT_FEE_LBL_ALL, IGS_FI_FEE_DSB_FM_RU, and IGS_FI_F_TYP_CA_INST_ALL (RUL_SEQUENCE_NUMBER and SCOPE_RUL_SEQUENCE_NUM), which govern fee assessment and disbursement rule scoping.
• Cohort definitions — IGS_PR_COHORT (RULE_SEQUENCE_NUMBER), linking population cohorts to their defining rule logic.

These relationships confirm IGS_RU_RULE as the anchor hub of a rule-reference network spanning the admissions, enrollment, records, progression, and financial aid sub-modules of the IGS Student System.