Search Results pricing_agreement_id




Overview
Explore in AI Chat

Overview

APPS.IBE_ORDER_HEADER_ADV_V is an Oracle E-Business Suite internal reporting view owned by the APPS schema and registered under FND Design Data as IBE.IBE_ORDER_HEADER_ADV_V. It exposes order header information for orders originating from the Oracle iStore (IBE) channel, presenting a denormalized, advanced ("ADV") projection of order header attributes joined with customer, party, and address-site data. The view is classified as an internal Oracle object; Oracle Corporation does not support direct access to applications data through this view except from standard Oracle Applications programs. Its primary role is to support order management, iStore order inquiry, and downstream reporting or integration processes that require a single-row-per-order-header representation enriched with customer account, bill-to, and ship-to context — including the SHIP_TO_ACCOUNT_ID and SHIP_TO_ACCT_SITE_ID columns frequently queried by implementation teams performing fulfillment or shipping analysis.

Underlying Base Objects

The documented dependency list identifies the following referenced objects (all resolved as synonyms or views in APPS):

The view is not referenced by any other database object, confirming its role as a leaf-level reporting construct rather than a building block for further views.

Key Columns

  • HEADER_ID — primary identifier of the order header; the join key back to OE_ORDER_HEADERS_ALL.
  • ORDER_NUMBER, CUST_PO_NUMBER, WEB_CONFIRM_NUMBER — business-facing order and reference identifiers, including the web confirmation number generated by iStore checkout.
  • ORDERED_DATE, BOOKED_DATE — order entry and booking timestamps.
  • ORDER_CATEGORY_CODE, ORDER_STATUS_CODE, ORDER_STATUS — coded and decoded order classification and lifecycle state.
  • CUST_ACCOUNT_ID, PARTY_ID, CUSTOMER_NAME — customer account and party context for the ordering entity.
  • BILL_TO_ACCOUNT_ID, BILL_TO_ACCT_SITE_ID — billing account and site identifiers.
  • SHIP_TO_ACCOUNT_ID — the ship-to customer account identifier, the column most commonly searched by users analyzing delivery destinations; it is paired with the corresponding account site in the underlying structure.
  • END_CUST_ACCOUNT_ID — the end-customer account for indirect or reseller-style orders.
  • PRICING_AGREEMENT_ID, CREATED_BY, ORG_ID — pricing agreement reference, record creator, and the operating unit (multi-org) identifier that scopes the row.

Common Use Cases and Queries

Typical uses include iStore order inquiry, ship-to analysis, and multi-org reporting. Because the view contains ORG_ID, all queries must respect the operating unit security context; in EBS 12.1.1 and 12.2.2, a MO: Operating Unit or MO: Security Profile is generally required for meaningful results.

SELECT header_id,
       order_number,
       ship_to_account_id,
       bill_to_account_id,
       order_status,
       ordered_date
FROM   apps.ibe_order_header_adv_v
WHERE  org_id = :p_org_id
AND    ship_to_account_id = :p_ship_to_account_id;

Aggregating orders by ship-to account provides volume reporting by delivery destination:

SELECT ship_to_account_id,
       COUNT(*) order_count
FROM   apps.ibe_order_header_adv_v
WHERE  org_id = :p_org_id
AND    booked_date BETWEEN :p_from AND :p_to
GROUP  BY ship_to_account_id;

Because Oracle does not support direct query access outside standard applications programs, these constructs should be treated as internal reporting aids, with the recommendation to source equivalent data from supported public APIs or the corresponding base tables where a supported interface exists.