Search Results order_total




Overview
Explore in AI Chat

Overview

The view ICX_PANEL_SO_SUMMARY_V belongs to the ICX product family, which corresponds to Oracle iProcurement. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 release streams, ICX objects historically supported the iProcurement storefront, including the informational panels that surfaced summary data to requisitioning users and buyers. The ETRM metadata classifies this particular view plainly as Obsolete. In the documented 12.2.2 repository, the view is listed with no owner and no referenced base objects, indicating that it is not implemented in the database and is retained only as historical documentation.

Despite its obsolete status, the object remains of interest to technical consultants because it illustrates a common iProcurement reporting pattern: aggregating sales order activity against customer records and presenting the results in a display-ready format. Its role in the EBS reporting and integration layers is therefore legacy rather than operational; no current concurrent program, OA Framework region, or interface depends on it in a supported 12.1.1 or 12.2.2 environment.

Underlying Base Objects

According to the documented view text, ICX_PANEL_SO_SUMMARY_V is defined over two base tables joined in a single query. The first is RA_CUSTOMERS, aliased as CUST, which supplies the customer identifier and customer name. The second is SO_HEADERS, aliased as H, which supplies order header attributes including currency, order dates, order number, and header identifier. The join is expressed as an outer join on the customer side (H.CUSTOMER_ID = CUST.CUSTOMER_ID(+)), meaning order rows are preserved even when no matching customer record exists.

The ETRM 12.2.2 metadata records no owner and no documented referenced base objects, which is consistent with an obsolete, non-implemented view. In practice, SO_HEADERS is a legacy synonym or compatibility object that maps to the Order Management order header structures, while RA_CUSTOMERS is the Receivables customer table. The view also invokes the function OE_QUERY.ORDER_TOTAL and the formatting utility FND_CURRENCY.SAFE_GET_FORMAT_MASK, both of which are server-side PL/SQL dependencies rather than base tables.

Key Columns

The order_total column is the element most relevant to the originating search. It is not a stored column but a computed aggregate, meaning any consumer querying this view receives a derived monetary value rather than a persisted amount.

Common Use Cases and Queries

The view was designed to produce a rolling thirty-day summary of order activity per customer and currency, which suits dashboard-style panels and buyer review screens. Because it is documented as obsolete and not implemented, the primary practical use today is migration analysis or historical reconstruction. A representative query against the view, where it exists, would be:

  • SELECT customer_name, currency_code, order_total, total_so_numbers FROM icx_panel_so_summary_v ORDER BY order_total DESC;
  • SELECT customer_id, SUM(TO_NUMBER(order_total)) FROM icx_panel_so_summary_v GROUP BY customer_id; — noting that order_total is a formatted character string, so numeric conversion requires caution.
  • SELECT * FROM icx_panel_so_summary_v WHERE last_date_ordered >= TRUNC(SYSDATE) - 7; — refines the built-in thirty-day window.

For new development on 12.1.1 or 12.2.2, the recommended approach is to bypass this obsolete view entirely and query OE_ORDER_HEADERS_ALL and RA_CUSTOMERS directly, replicating the OE_QUERY.ORDER_TOTAL logic with supported Order Management APIs or a custom aggregation. Any dependency on ICX_PANEL_SO_SUMMARY_V should be treated as technical debt and removed during upgrade or remediation work.