Search Results igs_fi_party_subacts_uk

Overview

The IGS_FI_PARTY_SUBACTS table is a core data structure within the Oracle E-Business Suite's Student System (IGS), specifically for release versions 12.1.1 and 12.2.2. As indicated in its metadata, this table is designated as "Obsolete." Its primary function was to model the specific financial relationship between a person (Party) and a sub-account. It served as a junction table that stored configuration and rule-based attributes applicable only within the context of a particular party and sub-account pairing, thereby enabling personalized financial handling beyond the general settings of the sub-account itself.

Key Information Stored

The table's structure centers on linking a party to a sub-account and storing associated financial parameters. The primary identifier is the system-generated PARTY_SUBACCOUNT_ID. The two critical foreign key columns are PARTY_ID, which references HZ_PARTIES to identify the person or organization, and SUBACCOUNT_ID, which references IGS_FI_SUBACCTS_ALL to identify the specific financial sub-account. According to the provided description, key attributes stored for this relationship include a holds threshold amount, which likely defines a monetary limit for automatic hold application, and a holds waiver flag, which would indicate if standard hold rules are waived for this specific party on this sub-account. These fields allowed for granular control over financial policies at an individual level.

Common Use Cases and Queries

This table was central to scenarios requiring party-specific financial account management. A primary use case was determining if a financial hold should be placed on a student's account by checking their incurred charges against their personalized threshold amount stored in IGS_FI_PARTY_SUBACTS. Another was verifying waiver statuses for administrative overrides. Common reporting queries would join this table to party and sub-account master data. For example, to list all personalized sub-account settings for a student, a query would be:

• SELECT p.party_number, s.subaccount_code, ps.holds_threshold_amount, ps.holds_waiver_flag
• FROM igs_fi_party_subacts ps, hz_parties p, igs_fi_subaccts_all s
• WHERE ps.party_id = p.party_id AND ps.subaccount_id = s.subaccount_id
• AND p.party_number = 'STUDENT123';

It is critical to note the "Not implemented in this database" status from the metadata, indicating this table may not be populated or actively used in many deployments, potentially superseded by other functionality.

Related Objects

IGS_FI_PARTY_SUBACTS has defined relationships with two primary master tables, forming the backbone of its data model. It is directly linked to HZ_PARTIES via the PARTY_ID column, which is the universal table for persons and organizations across Oracle EBS. It also has a foreign key relationship to IGS_FI_SUBACCTS_ALL via the SUBACCOUNT_ID column, which defines the financial sub-account master record. These relationships ensure referential integrity, tying the personalized settings back to the core entity definitions. The existence of a unique key (IGS_FI_PARTY_SUBACTS_UK) on the combination of PARTY_ID and SUBACCOUNT_ID enforces that only one set of such personalized parameters can exist per unique party/sub-account combination.