Results for “aso_i_order_headers_v”

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

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

• HEADER_ID, ORG_ID, ORDER_NUMBER – primary identifiers for the order header and operating unit.
• ORDER_TYPE_ID, ORDER_TYPE_NAME – order transaction type identifier and descriptive name.
• SOLD_TO_ORG_ID, PARTY_NAME, ACCOUNT_NUMBER – selling-party customer context from HZ_CUST_ACCOUNTS and HZ_PARTIES.
• ORDERED_DATE, REQUEST_DATE – order placement and requested dates.
• BOOKED_FLAG, OPEN_FLAG, CANCELLED_FLAG – order lifecycle status indicators.
• PAYMENT_TERM_ID, PAYMENT_TERM, PAYMENT_TYPE_CODE, PAYMENT_AMOUNT – commercial and payment terms.
• TRANSACTIONAL_CURR_CODE, CONVERSION_RATE, CONVERSION_TYPE_CODE – currency and conversion details (e.g., for ASO currency),
• INVOICE_TO_* / SHIP_TO_* address columns – flattened address components (ADDRESS_LINE_1..3, TOWN_OR_CITY, STATE, POSTAL_CODE, COUNTRY) from the invoice-to and ship-to address views.
• SHIPPING_METHOD_CODE, FREIGHT_CARRIER_CODE, SHIPMENT_PRIORITY_CODE, FOB_POINT_CODE, FREIGHT_TERMS_CODE – fulfillment attributes.
• CREDIT_CARD_CODE, CREDIT_CARD_NUMBER, CREDIT_CARD_EXPIRATION_DATE – payment card fields exposed for Order Capture processing.

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.