Results for “igs_fi_app_rules”

27 results




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

Overview

IGS_FI_APP_RULES is a transactional configuration table within the Oracle E-Business Suite IGS (Student System) product family. It stores the application rules associated with each Application Hierarchy defined by an institution, capturing the fee types eligible for application and the order in which those fee types are selected when fees are applied against a student account. In practical terms, the table functions as the sequencing and eligibility matrix that drives automated fee application logic within the Student Financials component of the obsolete IGS module.

The metadata identifies the Data Vault classification as satellite-leaning, derived heuristically from its foreign key structure. This suggests that the table is best modeled as a satellite entity: it holds descriptive attributes (fee type, rule type, sequence, enabled status) that qualify a parent business key defined in IGS_FI_A_HIERARCHIES, rather than acting as an independent hub or as a pure many-to-many link. The APPL_HIERARCHY_ID foreign key anchors each row to its owning hierarchy, reinforcing the satellite interpretation. ETRM notes that the object is not implemented in the current database, consistent with the retirement of the IGS product line.

Key Information Stored

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

  • APPL_RULE_ID — surrogate primary key (IGS_FI_APP_RULES_PK) uniquely identifying each rule row.
  • APPL_HIERARCHY_ID — foreign key to IGS_FI_A_HIERARCHIES; the Application Hierarchy to which this rule belongs. Also part of the business unique key.
  • FEE_TYPE — the fee type selected for application purposes; a business-key component.
  • RULE_TYPE — categorizes the rule governing how the fee type participates in application logic; a business-key component.
  • RULE_SEQUENCE — the ordinal position controlling the order in which fee types are evaluated and applied.
  • ENABLED_FLAG — indicates whether the rule is currently active.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard Oracle EBS audit and concurrency columns.

The surrogate key is APPL_RULE_ID, exposed through unique index IGS_FI_APP_RULES_U1. The natural business key is defined by IGS_FI_APP_RULES_U2, a composite of APPL_HIERARCHY_ID, FEE_TYPE, and RULE_TYPE, which ensures a fee type/rule pairing is unique within a hierarchy. Note that the foreign key references IGS_FI_A_HIERARCHIES.APPL_HIERARCHY_ID, not the IGS_FI_APP_RULES primary key described in the excerpt above.

Common Use Cases and Queries

Typical reporting scenarios include auditing which fee types are enabled for a hierarchy and verifying application sequence. A representative query joining to the parent hierarchy is:

  • Retrieve all active rules for a hierarchy in application order: SELECT fee_type, rule_type, rule_sequence FROM igs_fi_app_rules WHERE appl_hierarchy_id = :hierarchy AND enabled_flag = 'Y' ORDER BY rule_sequence;
  • Detect gaps or duplicate sequences within a hierarchy for data-quality validation.
  • Trace which hierarchies reference a given fee type for impact analysis before fee-type retirement.
  • Generate configuration extracts comparing rule definitions across hierarchies or across environments.
  • Confirm enforcement of the U2 business key when validating migration or interface loads.

Related Objects

The most significant related objects, based on the documented foreign key relationship and IGS Student Financials context, are:

  • IGS_FI_A_HIERARCHIES — parent table; joined on IGS_FI_APP_RULES.APPL_HIERARCHY_ID = IGS_FI_A_HIERARCHIES.APPL_HIERARCHY_ID.
  • IGS_FI_FEE_TYPES — reference source for FEE_TYPE values.
  • IGS_FI_RULE_DEFNS — likely source of RULE_TYPE definitions.
  • IGS_FI_APPLICATIONS — downstream transaction table consuming applied fee results.
  • IGS_FI_ACCT_DETAILS — account-level fee application outcomes.

Given the product's obsolete status, no supported APIs or concurrent programs are documented as active dependencies; the table remains relevant primarily for archival and historical data analysis.