Search Results igs_fi_subaccts_all




Overview
Explore in AI Chat

Overview

The table IGS_FI_SUBACCTS_ALL is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS), specifically for financial management. It functions as the master repository for all defined sub-accounts within an institution. A sub-account is a critical financial entity used to segregate and track accounting transactions, such as receivables, revenue, and cash, for specific purposes, departments, or programs. This table supports multi-org architecture, as indicated by the '_ALL' suffix and the ORG_ID column in its unique key, allowing data to be partitioned by operating unit. Its primary role is to provide a centralized definition that is referenced by numerous transactional and setup tables across the student financials module to ensure consistent financial posting and reporting.

Key Information Stored

Each row in IGS_FI_SUBACCTS_ALL defines a single, valid sub-account. While the full column list is not detailed in the provided metadata, the description and key structure highlight the essential data points. The primary identifier is SUBACCOUNT_ID. Crucially, the unique key combines ORG_ID, SUBACCOUNT_NAME, and EFFECTIVE_START_DATE, enforcing that sub-account names are unique within an operating unit from a specific date. According to the description, each row stores the sub-account's name and description, along with associated account details for receivables, revenue, cash, and unapplied amounts. It also stores receipt lockbox numbers assigned to the sub-account, linking it to automated cash receipt processing.

Common Use Cases and Queries

This table is primarily referenced for setup validation, transaction processing, and financial reporting. Common operational scenarios include validating a sub-account during fee assessment or cash receipt entry, and generating reports that summarize financial activity by sub-account. Typical queries involve joining to transactional tables to aggregate balances or retrieve setup information for a given transaction. For example, to list all active sub-accounts for a specific operating unit, one might use:

  • SELECT subaccount_name, description FROM igs_fi_subaccts_all WHERE org_id = :org_id AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE) ORDER BY subaccount_name;

Another common pattern is joining to the IGS_FI_BALANCES table to analyze financial summaries:

  • SELECT sa.subaccount_name, fb.balance_amt FROM igs_fi_subaccts_all sa, igs_fi_balances fb WHERE sa.subaccount_id = fb.subaccount_id AND sa.org_id = :org_id;

Related Objects

As evidenced by the extensive foreign key relationships, IGS_FI_SUBACCTS_ALL is a pivotal parent table. Key child tables include IGS_FI_BALANCES (stores running balances), IGS_FI_CREDITS_ALL (credit memos), IGS_FI_FEE_TYPE_ALL (fee type setup), IGS_FI_BILL_ALL (invoices), and IGS_FI_PARTY_SUBACTS (assigns sub-accounts to customers/students). It is also referenced by configuration tables for lockboxes (IGS_FI_SA_LOCKBOXES), payment plans (IGS_FI_FIN_LT_PLAN), and credit types (IGS_FI_CR_TYPES_ALL). This wide integration underscores its central role in ensuring that all financial transactions in the Student System are posted to a valid and properly configured sub-account.