Search Results holds_balance_rule_identifier




Overview
Explore in AI Chat

Overview

IGSFV_PARTY_BALANCES is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGSFV_PARTY_BALANCES. The view presents party-level balance information in the context of an account, returning the balance amount calculated for a party across standard, fee, and holds components. It is primarily associated with the Student Systems / Financial Aid family of products (the IGS module stack) and is used for reporting, reconciliation, and integration of student account balances.

The view exposes one row per balance record, keyed by BALANCE_IDENTIFIER, with descriptive attributes for the party (PARTY_IDENTIFIER, PARTY_NUMBER, PARTY_NAME) and a BALANCE_DATE identifying the calculation date. Three distinct balance buckets are returned: STANDARD_BALANCE, FEE_BALANCE, and HOLDS_BALANCE. Because it is a BIS view, it is intended for read-only query access rather than transactional update, and it is commonly consumed by reporting tools, extracts, and downstream interfaces rather than by core online forms.

Underlying Base Objects

The documented metadata for this view lists no referenced base objects. In practice, a view of this naming and column pattern is defined over the base balance table in the IGS schema (typically a table such as IGS_BALANCES or its related party balance table), joined to party and balance rule lookups to resolve PARTY_NUMBER, PARTY_NAME, and the rule name/version attributes. Column naming conventions — the *_IDENTIFIER suffix on BALANCE_IDENTIFIER, PARTY_IDENTIFIER, and the two rule identifiers — indicate surrogate keys resolved from dimension-style lookups, while the VARCHAR2 descriptive fields (PARTY_NUMBER, PARTY_NAME, FEE_BALANCE_NAME, HOLDS_BALANCE_NAME) are denormalized for reporting convenience.

Because the view is exposed with a VALID status in both 12.1.1 and 12.2.2, its definition is presumed stable across those releases. Administrators should confirm the exact base objects in the target instance by querying USER_DEPENDENCIES or ALL_VIEWS for the view definition, since the ETRM metadata does not enumerate them.

Key Columns

  • BALANCE_IDENTIFIER — NUMBER(15); primary key of the underlying balance record.
  • PARTY_IDENTIFIER — NUMBER(15); the person for whom the balance is calculated.
  • BALANCE_DATE — DATE; the date the balance was calculated.
  • STANDARD_BALANCE — NUMBER; balance amount for standard balance.
  • FEE_BALANCE — NUMBER; balance amount for fee balance.
  • HOLDS_BALANCE — NUMBER; balance amount for holds balance.
  • PARTY_NUMBER / PARTY_NAME — VARCHAR2; party identifiers and names.
  • FEE_BALANCE_RULE_IDENTIFIER, FEE_BALANCE_NAME, FEE_BALANCE_VERSION_NUMBER — the balance rule used by the Balance Process to derive the fee balance amount.
  • HOLDS_BALANCE_RULE_IDENTIFIER, HOLDS_BALANCE_NAME, HOLDS_BALANCE_VERSION_NUMBER — the balance rule used by the Balance Process to derive the holds balance amount.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Who audit columns.

Common Use Cases and Queries

Typical uses include student account reporting, reconciliation of balance buckets, and integration of balance and rule information into downstream systems. A common query filters by the holds rule identifier, which is the column most often referenced by administrators reviewing holds balances:

SELECT PARTY_NUMBER, PARTY_NAME, BALANCE_DATE, STANDARD_BALANCE, FEE_BALANCE, HOLDS_BALANCE, HOLDS_BALANCE_RULE_IDENTIFIER, HOLDS_BALANCE_NAME, HOLDS_BALANCE_VERSION_NUMBER FROM APPS.IGSFV_PARTY_BALANCES WHERE HOLDS_BALANCE_RULE_IDENTIFIER = :rule_id;

Other patterns include selecting by party for a statement-style report, or grouping by rule name to compare balances generated under a specific version of a rule. Because the view is read-only, any corrective action must be performed against the underlying base tables, not through the view itself.