Search Results credit_activity_id




Overview
Explore in AI Chat

Overview

The IGS_FI_BILL_DPSTS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (Oracle Student Financials) module. It functions as a junction or association table designed to capture and maintain the relationship between a bill and eligible deposits that can be applied against it. Its primary role is to ensure accurate financial accounting by linking a specific bill identifier (BILL_ID) to one or more credit activities designated as deposits (CREDIT_ACTIVITY_ID). This linkage is critical for processes that apply prepaid funds or deposits towards outstanding student charges, thereby supporting key accounts receivable operations within the educational institution's financial system.

Key Information Stored

The table is structurally simple, centering on two mandatory foreign key columns that define the core relationship. The BILL_ID column stores the unique identifier for the financial bill or invoice against which a deposit can be applied. The CREDIT_ACTIVITY_ID column holds the unique identifier for the specific credit transaction recorded in the system that is classified as an eligible deposit. This is the column of specific interest to the user's search. The table is completed by a standard set of Oracle EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing, and Concurrent Program WHO columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) to track changes made by batch processes. The table's integrity is enforced by the unique composite primary key index IGS_FI_BILL_DPSTS_PK on the combination of BILL_ID and CREDIT_ACTIVITY_ID.

Common Use Cases and Queries

A primary use case is tracing the application of a student's deposit payment to a generated bill. For instance, an administrator may need to identify all deposits allocated to a particular bill for reconciliation or to generate a detailed statement of account. Conversely, support staff might investigate which bill a specific deposit credit was applied to. Common reporting queries involve joining this table to the underlying bill and credit activity master tables to pull descriptive information.

  • Find deposits for a specific bill: SELECT * FROM igs.igs_fi_bill_dpsts WHERE bill_id = <bill_number>;
  • Find the bill linked to a specific credit activity (deposit): SELECT * FROM igs.igs_fi_bill_dpsts WHERE credit_activity_id = <credit_id>;
  • Join to get descriptive data (conceptual example): SELECT b.bill_number, ca.credit_amount, ca.transaction_date FROM igs.igs_fi_bill_dpsts bd JOIN igs_fi_bills_h b ON bd.bill_id = b.bill_id JOIN igs_fi_cr_activities ca ON bd.credit_activity_id = ca.credit_activity_id WHERE bd.bill_id = <bill_number>;

Related Objects

Based on the provided metadata, the IGS_FI_BILL_DPSTS table does not explicitly reference other objects via foreign keys in its definition. However, it is referenced by an object within the APPS schema. The BILL_ID column is logically a foreign key to a bill header table (commonly named IGS_FI_BILLS or IGS_FI_BILLS_H in the IGS schema), and the CREDIT_ACTIVITY_ID is a foreign key to a credit activities table (such as IGS_FI_CR_ACTIVITIES). These relationships, while not enumerated in the dependency list, are inherent to the table's purpose. The documented reference from the APPS.IGS_FI_BILL_DPSTS synonym indicates this table is accessed through the standard APPS schema synonym for integration and modularity within the EBS architecture.