Search Results calculate_balance

Overview

The APPS.IGS_FI_PRC_BALANCES package is a financial processing component within the Oracle E-Business Suite Student System (IGS) module, specifically the Financials (IGS_FI) sub-module. Its principal business function is the calculation, maintenance, and conversion of student and person-related financial balances. It supports the institution's ability to track what a student or party owes based on balance rules, holds, credits, and related financial activity. The package was created in May 2001 and has undergone multiple enhancements, most notably around hold conversion processing and the restructuring of its balance calculation logic.

The package specification explicitly defines its purpose as containing the definitions of the calc_balances and calculate_balances procedures, with additional procedures added over time to support enhanced functionality. The most recent documented revision (2005) reflects the mature state of the package, consolidating earlier changes relating to exclusion rules, hold conversion, and parameter simplification.

Key Procedures and Functions

The package exposes six documented procedures and functions:

• CALC_BALANCES — Drives balance calculation at the person and person-group level. It accepts parameters identifying the person, person group, balance type, balance date, and organization context, and returns standard concurrent program status values (errbuf, retcode). It originally included a subaccount parameter, later removed under Bug #2564643.
• CALCULATE_BALANCE — The core balance calculation routine. Per change history, an earlier local function named calculate_balance_1 was renamed and promoted to this public procedure when a balance rule identifier parameter was introduced (Enh#2562745).
• UPDATE_BALANCES — Persists calculated balance results. It gained a source_id parameter in December 2001 (Bug #2124001) to improve traceability of balance updates.
• CHECK_EXCLUSION_RULES — A generic function that evaluates whether a given record is excluded from balance processing. The p_balance_rule_id parameter was added to support rule-specific exclusions.
• CONVERT_HOLDS_BALANCES — Introduced in October 2002 (Enh#2562745) to support a new concurrent program for hold conversion, translating hold data into balance form.
• CONV_BALANCES — The companion conversion procedure supporting the same Hold Conversion concurrent program.

Tables Accessed

The package operates against a substantial set of IGS financial and person tables accessed through APPS synonyms:

• IGS_FI_BALANCES and IGS_FI_BALANCE_RULES — store computed balances and the rules governing their calculation.
• IGS_FI_CONTROL_ALL, IGS_FI_CREDITS_ALL, and IGS_FI_CR_ACTIVITIES — provide control parameters, credit records, and credit activity data used in deriving balances.
• IGS_FI_HOLD_PLAN, IGS_FI_PERSON_HOLDS, and IGS_PE_PERS_ENCUMB — hold plans, applied holds, and encumbrances that affect or trigger balance conversion.
• IGS_FI_INV_WAV_DET — invoice waiver detail that participates in net balance computation.
• HZ_PARTIES — the TCA party registry, linking balances to the correct party.
• FND_NEW_MESSAGES — the standard messaging table used for user-facing notifications during processing.

Usage Notes

IGS_FI_PRC_BALANCES is typically invoked through concurrent programs and internal EBS processes rather than direct form interaction. The Hold Conversion concurrent program is a documented caller of CONVERT_HOLDS_BALANCES and CONV_BALANCES, while CALC_BALANCES exposes the standard concurrent program OUT parameters (errbuf, retcode), confirming its use as a concurrent program entry point. The package is referenced by six other packages, indicating it occupies a foundational position in the student financials processing chain. Custom code should invoke the public procedures only, respecting the documented parameter signatures and supplying a valid p_org_id to maintain multi-org integrity. Because balance rules and exclusion logic govern behavior, changes to IGS_FI_BALANCE_RULES directly affect outcomes, and callers should anticipate conditional exclusion when interpreting results.