Search Results amount_credited

Overview

The view ICX_PANEL_INVOICE_SUM_V belongs to the ICX product family, Oracle iProcurement, within Oracle E-Business Suite releases 12.1.1 and 12.2.2. The ETRM documentation record for this object explicitly classifies its Description as Obsolete, and the implementation/DBA section states that it is Not implemented in this database. The view was historically part of the iProcurement "Panel" family of summary views, whose purpose was to aggregate receivables transaction balances for display in the iProcurement self-service interface, typically on the Billing and Payment or invoice summary panels presented to a customer or internal user.

Functionally, the view consolidates amounts from the AR payment schedule at the customer and invoice-currency level, rolling original, remaining, adjusted, applied, credited, tax, freight, discount, dispute, and receivables-charge figures into a single summary row per customer/currency combination. It is therefore a reporting and presentation construct rather than a transactional object. Because it is documented as obsolete and unimplemented in the reference environment, it should be treated as a legacy artifact. Any reference to it in current custom code, reports, or personalizations should be regarded as a candidate for remediation, and developers should verify whether a supported replacement view or direct query against the underlying AR tables is in use.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and the view text is provided only as an excerpt. The visible portion of the definition confirms that the query selects from AR_PAYMENT_SCHEDULES PS joined to RA_CUST... (truncated in the excerpt, conventionally RA_CUSTOMERS RAC on PS.CUSTOMER_ID = RAC.CUSTOMER_ID). AR_PAYMENT_SCHEDULES is the authoritative Oracle Receivables table holding one row per payment schedule line, including original, remaining, adjusted, applied, credited, discount, dispute, and receivables-charge amounts. RA_CUSTOMERS supplies the customer name. The view additionally calls FND_CURRENCY.SAFE_GET_FORMAT_MASK, a standard EBS currency formatting function used to render numeric amounts according to the invoice currency's format mask. Because no base objects are formally documented in ETRM, the join columns and the remaining RA_CUST... table should be confirmed from the deployed source before relying on them.

Key Columns

• CUSTOMER_ID, CUSTOMER_NAME — grouping keys identifying the customer whose balances are summarized.
• INVOICE_CURRENCY_CODE — the currency in which amounts are expressed; also drives the format mask applied to the character-formatted amount columns.
• DAYS_PAST_DUE — sum of days between system date and due date, excluding rows where AMOUNT_DUE_REMAINING is zero.
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING — original and open balances on the schedule.
• AMOUNT_LINE_ITEMS_ORIGINAL, TAX_ORIGINAL, FREIGHT_ORIGINAL — component breakdown of the original amount.
• AMOUNT_ADJUSTED — total adjustments applied to the schedule.
• AMOUNT_ADJUSTED_PENDING — adjustments recorded but not yet fully processed; this is the column associated with the user's search term amount_adjusted_pending. It is summed directly with SUM(PS.AMOUNT_ADJUSTED_PENDING).
• AMOUNT_APPLIED, AMOUNT_CREDITED — cash applied and credit memos applied against the schedule.
• DISCOUNT_TAKEN_EARNED, DISCOUNT_TAKEN_UNEARNED — earned and unearned payment discounts.
• ACCTD_AMOUNT_DUE_REMAINING — remaining balance in the ledger (accounted) currency.
• AMOUNT_LINE_ITEMS_REMAINING, TAX_REMAINING, FREIGHT_REMAINING — remaining component balances.
• RECEIVABLES_CHARGES_CHARGED, RECEIVABLES_CHARGES_REMAINING — late charges and finance charges assessed and outstanding.
• AMOUNT_IN_DISPUTE, DISPUTE_DATE (minimum) — disputed balances and the earliest dispute date.

Common Use Cases and Queries

The principal historical use case was populating iProcurement customer-facing panels with a per-customer, per-currency summary of outstanding receivables, including pending adjustments. A representative query is:

• SELECT customer_id, customer_name, invoice_currency_code, amount_due_remaining, amount_adjusted_pending, amount_in_dispute FROM icx_panel_invoice_sum_v WHERE customer_id = :p_customer_id; — retrieves summarized balances, including pending adjustments, for a single customer.
• SELECT customer_id, invoice_currency_code, days_past_due, amount_due_original, amount_due_remaining FROM icx_panel_invoice_sum_v ORDER BY days_past_due DESC; — ranks customers by aging exposure.
• SELECT invoice_currency_code, SUM(amount_adjusted_pending) pending_adj FROM icx_panel_invoice_sum_v GROUP BY invoice_currency_code; — aggregates pending adjustments across customers by currency.

Given the obsolete status, equivalent results are more reliably obtained by querying AR_PAYMENT_SCHEDULES joined to RA_CUSTOMERS directly, or through supported AR reporting views. The AMOUNT_ADJUSTED_PENDING metric in particular remains meaningful for reconciliation of adjustments that have been entered but not yet finalized, and should be validated against AR_ADJUSTMENTS when used for audit or reporting purposes.