Search Results igs_fi_hold_plan




Overview
Explore in AI Chat

Overview

The IGS_FI_HOLD_PLAN table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS), specifically for the finance module. Its primary function is to serve as a master definition table for hold plans. A hold plan is a configurable rule set that determines when and how a financial encumbrance, or "hold," is placed on a student's account based on unpaid or overdue fee assessments. It acts as a template, defining the conditions and parameters for a hold, which can then be applied to individual students. It is critical to note that the IGS product line is marked as obsolete in the provided ETRM documentation, indicating this table is part of a legacy system that may be deprecated or superseded in more recent EBS implementations.

Key Information Stored

The table's central attribute is the HOLD_PLAN_NAME, which serves as the unique identifier and primary key for each defined plan. Beyond the name, the table stores key references that define the hold's nature and trigger. The HOLD_TYPE column is a foreign key to IGS_FI_ENCMB_TYPE_ALL, linking the plan to a specific type of encumbrance (e.g., a registration hold, transcript hold). The FEE_TYPE column, a foreign key to IGS_FI_FEE_TYPE_ALL, specifies the category of fees (like tuition or library fines) to which the hold plan applies. While the exact full column list is not provided in the excerpt, the foreign key relationships confirm these are the critical links to the encumbrance type and the applicable fee type master tables.

Common Use Cases and Queries

The primary use case is the automated or administrative application of financial holds on student records. A system process would evaluate student fee accounts against active hold plans to determine if the conditions for a hold are met. Common queries would involve listing all defined hold plans, identifying plans linked to a specific fee or encumbrance type, or troubleshooting hold applications. For example, to see all hold plans and their associated encumbrance types, a query would join IGS_FI_HOLD_PLAN to IGS_FI_ENCMB_TYPE_ALL. Another critical query would identify which students have a specific hold plan applied by joining IGS_FI_HOLD_PLAN to IGS_FI_PERSON_HOLDS via the HOLD_PLAN_NAME.

Related Objects

The IGS_FI_HOLD_PLAN table sits at the center of a relational structure for financial holds. It references two master tables and is referenced by two transactional or detail tables.

  • Referenced By (Parent Tables):
    • IGS_FI_ENCMB_TYPE_ALL: Via the HOLD_TYPE column. This provides the specific type of hold (encumbrance) to be applied.
    • IGS_FI_FEE_TYPE_ALL: Via the FEE_TYPE column. This defines the category of fees that trigger the hold plan.
  • Referenced In (Child Tables):
    • IGS_FI_HOLD_PLN_LNS: Linked by HOLD_PLAN_NAME. This table likely stores the detailed line-level conditions or thresholds (e.g., minimum overdue amount, days overdue) for the hold plan.
    • IGS_FI_PERSON_HOLDS: Linked by HOLD_PLAN_NAME. This is the transactional table that records instances where a hold plan has been applied to an individual student.