Search Results hold_start_dt




Overview
Explore in AI Chat

Overview

The IGS_FI_PERSON_HOLDS table is a core transactional table within the Oracle E-Business Suite (EBS) 12.1.1/12.2.2 Student Financials module. It functions as an intermediate staging table for the automated processing of financial holds (encumbrances) placed on students. Its primary role is to be populated by the "Apply Hold Process" and subsequently queried by the "Release Hold Process" to identify students who have incurred financial obligations under defined hold plans. The table serves as a critical link between the assessment of charges, the application of business rules for holds, and the final enforcement of those holds on a student's academic and administrative records.

Key Information Stored

The table stores a snapshot of hold eligibility data generated during a specific run of the Apply Hold Process. Key columns include the identifier of the person (PERSON_ID), the specific HOLD_TYPE to be applied, and the critical HOLD_START_DT which signifies the effective date of the hold. The combination of PERSON_ID, HOLD_TYPE, and HOLD_START_DT forms the table's primary key, ensuring a unique record for each hold instance. Other significant columns capture the context of the process run, such as the HOLD_PLAN_NAME, the process execution dates (PROCESS_START_DT, PROCESS_END_DT), the calculated PAST_DUE_AMOUNT, and calendar details (FEE_CAL_TYPE, FEE_CI_SEQUENCE_NUMBER) if the hold was applied at the fee type level.

Common Use Cases and Queries

The primary use case is the automated release of holds, where a concurrent program queries this table to determine which holds, based on their start date and associated rules, should be formally posted to the student's account. For reporting and troubleshooting, common queries involve identifying all pending holds for a person or within a date range. A sample query to find active holds for a specific student would be:

  • SELECT hold_plan_name, hold_type, hold_start_dt, past_due_amount FROM igs.igs_fi_person_holds WHERE person_id = :p_person_id AND hold_start_dt <= SYSDATE ORDER BY hold_start_dt DESC;

Another typical pattern is analyzing the output of a specific Apply Hold Process run by filtering on PROCESS_START_DT. Administrators may also query this table to audit the financial conditions that triggered hold eligibility before the holds are officially released.

Related Objects

IGS_FI_PERSON_HOLDS is centrally connected to several key master and transactional tables via foreign key relationships, as documented in the ETRM. These relationships enforce data integrity and define the table's role in the data model: