Results for “igi_dun_charge”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGI_DUN_CHARGE view is a multi-org secured database view owned by the APPS schema within the IGI – Public Sector Financials International product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to temporarily hold the calculated charges generated during a dunning charge run. Dunning is the collections process in Oracle Receivables through which reminder letters and associated charges are levied against customers with overdue balances. Because the IGI product extends standard Receivables dunning functionality for public sector customers, this view serves as the reporting and integration surface for charge calculations produced by a dunning run.

As a multi-org view, it enforces operating unit security by filtering rows on ORG_ID, allowing only data belonging to the session's current operating unit to be visible. This makes it suitable for concurrent program logic, Oracle Reports, BI Publisher data models, and custom integrations that must respect organization-level data access rules.

Underlying Base Objects

The view is defined over a single documented base object, IGI_DUN_CHARGE_ALL, referenced through a synonym. The defining query selects the full column list from IGI_DUN_CHARGE_ALL and applies the standard multi-org WHERE clause. That predicate derives the operating unit from the USERENV('CLIENT_INFO') value, decoding the first ten bytes of the client information string and comparing it to ORG_ID, with a fallback value of -99 for rows where ORG_ID is null. This is the canonical Oracle multi-org view pattern used throughout EBS. Because IGI_DUN_CHARGE is a view rather than a table, it stores no data of its own; all persisted rows reside in the underlying _ALL table, and writes against the view are permitted only where the base object is itself updatable.

Key Columns

The view exposes identifying, financial, and dunning-specific attributes:

• CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME – identify the customer subject to the dunning charge.
• SITE_USE_ID, BILL_TO_CUSTOMER_ID, BILL_TO_CONTACT_ID – identify the site and bill-to contact for the dunning communication.
• CUSTOMER_TRX_ID, TRX_NUMBER, CUST_TRX_TYPE_ID, TRX_DATE – the transaction (invoice) generating the charge.
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, SUM_AMT, INVOICE_CURRENCY_CODE – receivable balances and currency context.
• CUSTOMER_PROFILE_CLASS_ID – the customer profile class, referenced by the user's search and used to drive charge rules and dunning letter assignment.
• DUNNING_CHARGE, CHARGE_VALUE, CUST_CHARGE_VALUE, APP_CHARGE_RATIO, CHARGE_PER_INVOICE, DUNNING_CHARGE_TYPE, RULE – the calculated charge, the ratios and rules applied, and whether the charge is assessed per invoice or per run.
• DUNNING_LETTER_ID, DUNNING_LETTER_SET_ID, LETTER_NAME – the dunning letter definition associated with the run.
• PAYMENT_SCHEDULE_ID, SET_OF_BOOKS_ID, ORG_ID, REQUEST_ID – linkage to the payment schedule, ledger, operating unit, and the concurrent request that produced the data.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) – audit information.

Common Use Cases and Queries

Typical uses include auditing the output of a dunning charge run, reconciling charges by customer profile class, and feeding downstream letter generation or reporting. A representative query joining charge data to its originating request might read:

• Charges for a specific run: SELECT customer_name, trx_number, dunning_charge, charge_value, letter_name FROM igi_dun_charge WHERE request_id = :p_request_id ORDER BY customer_name;
• Charges grouped by customer profile class: SELECT customer_profile_class_id, COUNT(*) charges, SUM(dunning_charge) total FROM igi_dun_charge GROUP BY customer_profile_class_id;
• Operating-unit scoped extraction: Because the view filters on ORG_ID, querying it while the session's CLIENT_INFO is set to the target operating unit automatically restricts results, so no explicit ORG_ID predicate is normally required.

Because the underlying table is described as temporary storage for a run, consumers should expect data to be refreshed or purged by subsequent dunning processes and should not treat it as a permanent transactional record.