Search Results party_identifier




Overview
Explore in AI Chat

Overview

IGSBV_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.IGSBV_PARTY_BALANCES, the view is assigned a status of VALID and is classified as a BIS view, a category of database object intended to expose denormalized, reporting-ready data to external tools and analytical consumers. Its purpose, as documented, is to return, in the context of an account, the balance amount for a party. The "BV" naming convention marks it as a covered BIS view, distinguishing it from the underlying transactional base tables that store the raw financial and holds data.

The view supports the Oracle Student System (IGS) financials area, where party balances, fee balances, and holds must be surfaced for reporting, integration, and downstream processing. Because it presents balance amounts keyed to a party rather than to internal transaction identifiers, it serves as a stable integration point for extracts, dashboards, and interfaces that require a party-centric financial position without navigating the full normalized schema.

Underlying Base Objects

Per the documented dependency information, IGSBV_PARTY_BALANCES references the following objects: APPS.HZ_PARTIES and APPS.IGS_FI_BALANCES. IGS_FI_BALANCES supplies the balance rows, including the balance identifier, balance date, standard balance, fee balance, and holds balance amounts, together with the rule identifiers used by the balance process. HZ_PARTIES supplies party-level attributes, most notably the party number and party name surfaced in the view.

The join between these two objects is effected through the party identifier, linking each financial balance record to its owning party. The view is not referenced by any other database object, confirming it is a terminal, read-only reporting construct rather than a building block for further database logic. No base tables are documented beyond the two listed, and consumers should treat the view as the supported interface rather than querying the underlying tables directly.

Key Columns

Common Use Cases and Queries

Typical usage centers on retrieving a party's current balance position, reconciling fee and holds amounts, and feeding extracts that require party-level financial data. A frequently used query retrieves all balance rows for a specific party:

SELECT balance_identifier, party_identifier, balance_date, standard_balance, fee_balance, holds_balance, party_number, party_name FROM apps.igsbv_party_balances WHERE party_identifier = :p_party_id;

For reporting over a period, the view supports filtering by balance date and aggregating the three balance components. Because the view exposes party name and number directly, it eliminates the need to join HZ_PARTIES in reporting queries. Integration extracts commonly select the full column list documented in the ETRM query text to populate downstream staging tables, using BALANCE_IDENTIFIER as the unique key and the standard Who columns to support incremental refresh logic.