Search Results igi_dun_charge_all_pk

Overview

The IGI_DUN_CHARGE_ALL table is a core transactional table within the Oracle E-Business Suite module IGI (Public Sector Financials International). Its primary function is to serve as a temporary staging area for calculated dunning charges during a dunning charge run. Dunning is the process of systematically communicating with customers to collect overdue payments. In the context of IGI, this table specifically supports the automated calculation of late payment charges or penalties on delinquent invoices, a common requirement in public sector and international financial operations. The table's role is integral to the dunning workflow, holding intermediate results before they are finalized and posted to the general ledger or used to generate customer communications.

Key Information Stored

The table stores a snapshot of charge calculations linked to specific overdue payment schedules. Its composite primary key, IGI_DUN_CHARGE_ALL_PK, consists of PAYMENT_SCHEDULE_ID, INVOICE_CURRENCY_CODE, and REQUEST_ID. This structure ensures unique identification of a calculated charge for a specific payment schedule, in a specific currency, within a specific concurrent request (dunning run). Key columns include CUSTOMER_ID, linking to the customer account (HZ_CUST_ACCOUNTS), and DUNNING_LETTER_ID, referencing the dunning letter template (AR_DUNNING_LETTERS_B) used. The SET_OF_BOOKS_ID ties the calculation to the correct ledger, while CUSTOMER_PROFILE_CLASS_ID links to the dunning rules defined in IGI_DUN_CUST_PROF_CLASS. Other typical columns would store the calculated charge amount, the applicable interest rate, the overdue period, and the invoice details against which the charge is levied.

Common Use Cases and Queries

The primary use case is the review and audit of dunning charge calculations before final posting. Administrators may query this table to verify the accuracy of charges applied during a specific run. A common reporting need is to list all calculated charges for a given customer or dunning batch. Sample SQL patterns include retrieving details for a specific concurrent request or summarizing charges by customer profile class.

• Review charges for a specific dunning run: SELECT * FROM igi.igi_dun_charge_all WHERE request_id = :req_id;
• Summarize total charges by customer: SELECT customer_id, SUM(charge_amount) FROM igi.igi_dun_charge_all WHERE request_id = :req_id GROUP BY customer_id;
• Validate calculations against customer profile rules by joining with IGI_DUN_CUST_PROF_CLASS.

Related Objects

The IGI_DUN_CHARGE_ALL table maintains defined foreign key relationships with several fundamental EBS tables, ensuring referential integrity and enabling critical joins for data validation and reporting.

• HZ_CUST_ACCOUNTS: Joined via IGI_DUN_CHARGE_ALL.CUSTOMER_ID. Provides the customer master information for whom the dunning charge is calculated.
• AR_DUNNING_LETTERS_B: Joined via IGI_DUN_CHARGE_ALL.DUNNING_LETTER_ID. Links to the dunning letter template that governs the communication strategy for the overdue invoice.
• GL_SETS_OF_BOOKS: Joined via IGI_DUN_CHARGE_ALL.SET_OF_BOOKS_ID. Associates the charge calculation with the specific ledger or set of books for financial reporting.
• IGI_DUN_CUST_PROF_CLASS: Joined via IGI_DUN_CHARGE_ALL.CUSTOMER_PROFILE_CLASS_ID. This is a key relationship that links the calculated charge to the specific dunning rules, rates, and policies defined for the customer's profile class.