Search Results aso_i_order_headers_bali_v




Overview
Explore in AI Chat

Overview

The ASO_I_ORDER_HEADERS_BALI_V view is a public APPS schema database object within the Oracle E-Business Suite Order Capture (ASO) product family. It is registered in ETRM with a status of VALID and is defined against the OE_ORDER_HEADERS_ALL synonym together with the ASO_ORDER_INT package and the HR_OPERATING_UNITS view. The object presents a flattened, reporting-oriented picture of order headers joined to their associated sales quote headers, customer accounts, party relationships and order-flow status lookup meanings.

Its name prefix ASO_I indicates an Order Capture integration/reporting interface view intended for inquiry access rather than transactional data entry. The BALI suffix denotes a business-area/line-of-business specific variant commonly used in the Oracle iStore and Quoting flows. The primary role of the view is to expose the order total alongside other header attributes so that downstream reports, dashboards, or interfaces can retrieve a monetary total without independently invoking pricing or order-total APIs.

Because a user searched on the term order_total, the most relevant point is that this view does not simply select a stored column — the ORDER_TOTAL column is returned by a call to the PL/SQL function ASO_ORDER_INT.GET_ORDER_TOTAL(OH.HEADER_ID, NULL) executed at query time.

Underlying Base Objects

The documented base objects referenced by this view are:

  • OE_ORDER_HEADERS_ALL (accessed via a SYNONYM) — the primary source of order header attributes such as ORDER_NUMBER, ORDERED_DATE, SOLD_TO_ORG_ID, TRANSACTIONAL_CURR_CODE, FLOW_STATUS_CODE, HEADER_ID and ORG_ID.
  • ASO_ORDER_INT (PACKAGE) — supplies GET_ORDER_TOTAL, the API invoked in the SELECT list to derive the ordered total for each header.
  • HR_OPERATING_UNITS (VIEW) — provides organizational context for multi-org filtering, aligning the order's operating unit with resource and quote operating units.

The view additionally joins ASO_QUOTE_HEADERS_ALL, HZ_CUST_ACCOUNTS, ASO_PVT_PARTIES_V, ASO_PVT_PARTY_RLTN_V, JTF_RS_SRP_VL and OE_LOOKUPS. The quote header join is outer (QH.ORDER_ID(+)), so the view returns order headers regardless of whether a quotation exists. Multi-org security is enforced by comparing ORG_ID values against the numeric portion of USERENV('CLIENT_INFO'), defaulting unmatched rows to -99.

Key Columns

Common Use Cases and Queries

The view is typically queried to obtain order totals and status alongside customer and quote context without writing custom pricing logic. A minimal query returning the searched column is:

  • SELECT order_number, order_total, currency_code, order_status, ordered_date FROM apps.aso_i_order_headers_bali_v WHERE order_number = :p_order_number;

Additional practical scenarios include:

  • Reconciling header totals to quote values by selecting ORDER_TOTAL with QUOTE_NUMBER_VERS for a given customer.
  • Building status dashboards by grouping on the ORDER_STATUS lookup meaning.
  • Feeding integration staging tables that require both the order header and its computed total in one pass.

Because ORDER_TOTAL is calculated through the ASO_ORDER_INT package, queries across large header volumes should be filtered before projection to avoid invoking the function for every row, and results should be analyzed with the operating-unit context applied automatically by the view's ORG_ID predicate.