Search Results total_order_price

Overview

ASO_I_SEARCH_ORDERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, flagged VALID and registered in FND Design Data as ASO.ASO_I_SEARCH_ORDERS_V. The acronym ASO denotes the Order Capture / Quoting (Oracle Advanced Outbound / iStore order search) product family, and the "I_SEARCH" naming convention identifies the object as part of the internal search infrastructure used by the Order Capture and iStore user interfaces to locate existing sales orders and quotes. The view consolidates order header data with denormalized customer and contact attributes, which allows the search screens to display and filter on order, account, and contact information without issuing multiple joins at run time.

The ETRM metadata carries the standard Oracle restricted-use warning: the view is documented as Oracle Internal Use Only, and Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. The view type is classified as Internal. The column most relevant to the user's search term, total_order_price, is exposed as TOTAL_ORDER_PRICE, a NUMBER column representing the total price of the order header.

Underlying Base Objects

The documented dependency list for ASO_I_SEARCH_ORDERS_V comprises the following objects:

• ASO_ORDER_INT (PACKAGE) — the Order Capture integration package that supplies order and search-related logic and data.
• OE_ORDER_HEADERS (SYNONYM) — the core Order Management order header table, the primary source of order number, version, ordered date, currency, status, and the total order price.
• HZ_CUST_ACCOUNTS (SYNONYM) — the Trading Community Architecture customer account table, providing account number and account identifier.
• HZ_PARTIES (SYNONYM) — the TCA party master, supplying party identifiers and party-level attributes.
• HZ_ORG_CONTACTS (SYNONYM) — the TCA organization contact table, contributing contacts associated with the customer organization.
• HZ_RELATIONSHIPS (SYNONYM) — the TCA relationship table used to resolve party-to-account and contact-to-account associations.

The view is not referenced by any other database object, meaning it functions as a terminal read-only presentation layer rather than a building block for further dependent views or packages.

Key Columns

The view exposes eighteen columns. The principal identifiers are HEADER_ID (the unique order header key), ORDER_NUMBER, and ORDER_VERSION. ORDERED_DATE captures the order date. Customer information is denormalized across CUST_ACCT_ID, CUSTOMER_NAME (VARCHAR2 360), CUSTOMER_NUMBER (VARCHAR2 30), PARTY_ID, and ACCOUNT_NUMBER. Financial context is provided by CURRENCY_CODE (VARCHAR2 15) and TOTAL_ORDER_PRICE (NUMBER). Purchasing reference data is held in CUST_PO_NUMBER (VARCHAR2 50). Contact details are exposed through SOLD_TO_CONTACT_ID, SOLD_TO_CONTACT_FIRST_NAME (VARCHAR2 150), and SOLD_TO_CONTACT_LAST_NAME (VARCHAR2 150). STATUS (VARCHAR2 4000) carries the order status description. Standard WHO audit columns LAST_UPDATE_DATE and CREATION_DATE are included, which allows incremental extraction based on change timestamps.

Common Use Cases and Queries

The primary supported use is the Order Capture / iStore search flow, where the view backs search results for orders and quotes. Practical query patterns include retrieving recent orders by customer, filtering on currency and status, and aggregating order value. For example:

• Retrieve the order value for a specific customer: SELECT order_number, ordered_date, currency_code, total_order_price FROM apps.aso_i_search_orders_v WHERE cust_acct_id = :p_account_id;
• List recent high-value orders: SELECT order_number, customer_name, total_order_price FROM apps.aso_i_search_orders_v WHERE total_order_price > 10000 ORDER BY ordered_date DESC;
• Search by purchase order reference: SELECT order_number, cust_po_number, status FROM apps.aso_i_search_orders_v WHERE cust_po_number = :p_po;

Any custom use should be treated as unsupported per the Oracle Internal Use Only restriction; supported integration should rely on public Order Management APIs instead.