Search Results balance_hist_id

Overview

The IGS_FI_BALANCES_HST table is a historical audit table within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary role is to maintain a detailed, immutable audit trail for all changes made to student financial balances, specifically for Fee and Holds balance types. This table is critical for compliance, troubleshooting, and historical reporting, as it captures the state of a balance before and after a transaction or adjustment. It is important to note that the IGS module is marked as "Obsolete" in the provided ETRM documentation, indicating it is a legacy component that may not be actively developed. Furthermore, the metadata explicitly states "Not implemented in this database," suggesting this table may not be present in all EBS 12.1.1 or 12.2.2 instances, potentially existing only in reference documentation or older implementations.

Key Information Stored

The table's structure is designed to capture the essential elements of a balance change event. While a full column list is not provided in the metadata, the documented primary and foreign keys reveal its core components. The BALANCE_HIST_ID column serves as the unique identifier for each audit record. The BALANCE_ID is a foreign key that links each history record back to its parent balance in the IGS_FI_BALANCES table. Typically, a table of this nature would also include columns to store the old and new balance values, the date and time of the change, the identifier of the person or process that initiated the change, and the transaction or event that triggered the modification. This allows for a complete reconstruction of the balance's history over time.

Common Use Cases and Queries

The primary use case for this table is auditing and historical analysis. Common scenarios include generating reports for student account activity, reconciling financial postings, and investigating discrepancies in fee or hold balances. A system administrator or auditor might query this table to trace the complete lifecycle of a specific student's financial obligation. A sample query pattern would involve joining to the IGS_FI_BALANCES table to get current student and balance type context, then filtering by student or a date range.

Sample SQL Pattern:
SELECT hst.*, bal.person_id, bal.balance_type
FROM igs_fi_balances_hst hst
JOIN igs_fi_balances bal ON hst.balance_id = bal.balance_id
WHERE bal.person_id = :student_id
ORDER BY hst.creation_date DESC;

Related Objects

Based on the documented foreign key relationship, this table has a direct and singular dependency on the main balances table.

• IGS_FI_BALANCES: This is the primary parent table. The IGS_FI_BALANCES_HST table references it via the foreign key column IGS_FI_BALANCES_HST.BALANCE_ID to IGS_FI_BALANCES. Every historical record is associated with one specific balance record. The IGS_FI_BALANCES table likely holds the current, active balance for a student and balance type, while IGS_FI_BALANCES_HST stores the sequential history of how that balance reached its current state.