Search Results ibe_oe_order_headers_v

Overview

The IBE_OE_ORDER_HEADERS_V view belongs to the Oracle iStore (IBE) module and is designed to expose order header and order summary information for use in the Post Sales Interaction with Customer flow. Its purpose is to present a consolidated, presentation-ready view of order header data so that iStore self-service pages and related reporting components can display order details without directly querying the more granular transactional tables. The view is built upon ASO_I_OE_ORDER_HEADERS_V, an Oracle Order Capture foundation view, and layers additional formatting and derived values on top of it, including currency-formatted monetary amounts and computed status text.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2. In the source environment referenced by the ETRM documentation, the object is listed as not implemented in the database, meaning the definition is documented but not physically present in that particular instance. This is a common situation for seeded views that exist only when the corresponding iStore or Order Capture functionality is installed and configured.

Underlying Base Objects

The documented base object for this view is ASO_I_OE_ORDER_HEADERS_V, from which the order header attributes such as header identifier, order number, order type, ordered date, price list, sold-to account, and address details are sourced. Additional joins are implied by the view text: customer information is drawn from a customer/party source aliased CUST, payment terms from TERM, and invoice and ship-to address attributes from INVADDR and SHIPADDR respectively. Lookup meanings, such as freight terms, are resolved through an alias OLKP. No base tables are documented as directly referenced beyond this foundation view, so the lineage should be traced through ASO_I_OE_ORDER_HEADERS_V and the corresponding Order Management header tables when performing impact analysis.

Key Columns

• HEADER_ID, ORDER_NUMBER, ORDER_TYPE_ID, ORDERED_DATE, BOOKED_FLAG, OPEN_FLAG, CANCELLED_FLAG — core order identity and lifecycle indicators.
• ORDER_TOTAL, PAYMENT_AMOUNT — monetary values formatted using FND_CURRENCY.SAFE_GET_FORMAT_MASK against TRANSACTIONAL_CURR_CODE, producing display-ready amounts.
• TRANSACTIONAL_CURR_CODE — the transaction currency code, which drives the format mask applied to ORDER_TOTAL and PAYMENT_AMOUNT. This is the column most commonly searched in conjunction with currency-related reporting.
• ORDER_STATUS — derived via ASO_ORDER_INT.GET_HEADER_STATUS.
• CUST_ACCOUNT_ID, PARTY_ID, CUSTOMER_NAME — customer identification.
• INVOICE_TO_LOCATION, SHIP_TO_LOCATION and their component address columns — consolidated address display values.
• FREIGHT_TERMS, SHIPPING_METHOD_CODE, PAYMENT_TERM, CUST_PO_NUMBER — fulfillment and commercial reference attributes.

Common Use Cases and Queries

Typical usage includes iStore order summary pages, post-sales order tracking, and ad hoc operational reporting requiring formatted order totals. The following query retrieves recently booked orders with their transactional currency and formatted totals:

SELECT order_number,
       ordered_date,
       transactional_curr_code,
       order_total,
       order_status,
       customer_name
FROM   ibe_oe_order_headers_v
WHERE  booked_flag = 'Y'
AND    ordered_date >= SYSDATE - 30
ORDER BY ordered_date DESC;

Because ORDER_TOTAL and PAYMENT_AMOUNT are already formatted using the transaction currency mask, consumers should treat these as display strings rather than raw numeric values when performing arithmetic. For aggregation or reconciliation, query the underlying Order Management tables or the unformatted source instead.