Search Results aso_i_order_headers_v




Overview
Explore in AI Chat

Overview

ASO_I_ORDER_HEADERS_V is a denormalized reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ASO – Order Capture (iStore / Oracle iStore Order Capture) product family. The view exposes order header information in a single flattened result set that combines core order attributes from the order management tables with customer, address, payment term, and order type context. It is provided as a read interface so that calling programs — particularly the Order Capture and order import/inbound processing paths — do not need to join across the many OE and HZ tables directly. The object is documented in ETRM for both 12.1.1 and 12.2.2 with a status of VALID.

Underlying Base Objects

The view is defined primarily over OE_ORDER_HEADERS_ALL (presented through the OE_ORDER_HEADERS synonym), joined to several lookup and reference views. The documented referenced objects in ETRM 12.2.2 are: OE_ORDER_HEADERS, OE_TRANSACTION_TYPES_VL, RA_TERMS_VL, OE_SHIP_TO_ORGS_V, OE_INVOICE_TO_ORGS_V, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_PARTIES. The joins are driven by foreign key relationships: ORDER_TYPE_ID joins to OE_TRANSACTION_TYPES_VL.TRANSACTION_TYPE_ID and is restricted to TRANSACTION_TYPE_CODE = 'ORDER'; PAYMENT_TERM_ID joins to RA_TERMS_VL; SOLD_TO_ORG_ID links to HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUST_ACCOUNT_ROLES; and SHIP_TO_ORG_ID and INVOICE_TO_ORG_ID resolve through OE_SHIP_TO_ORGS_V and OE_INVOICE_TO_ORGS_V respectively.

Key Columns

Common Use Cases and Queries

The view is typically queried by order capture or order import interfaces that need a single row per order header with customer name and shipping/invoicing addresses already resolved. A representative query is:

SELECT order_number, order_type_name, party_name,
       ordered_date, transactional_curr_code,
       payment_term, shipping_method_code
  FROM apps.aso_i_order_headers_v
 WHERE org_id = :p_org_id
   AND booked_flag = 'Y';

Order Capture developers also use it to validate captured header data, to look up the sold-to customer’s account number, or to retrieve address lines for display. Because the definition constrains ORDER_TYPE_CODE to 'ORDER', the view only returns standard order transaction types. Any query must be schema-qualified as APPS and should be executed with the correct operating unit (ORG_ID) filter to respect multi-org security. Performance depends on the underlying OE_ORDER_HEADERS_ALL and HZ joins; standard indexing on HEADER_ID, ORDER_NUMBER, and ORG_ID should be leveraged.