Search Results oe_as_order_headers_v




Overview
Explore in AI Chat

Overview

APPS.OE_AS_ORDER_HEADERS_V is a reporting and integration view in the Oracle Order Management (ONT) module. It exposes a denormalized, human-readable projection of sales order header information drawn from OE_ORDER_HEADERS_ALL and a set of related reference and party objects. Its documented purpose is to "provide details of all existing orders in the Order Management," which makes it a convenient single-source query point for dashboards, extracts, interfaces, and downstream integration routines that need order-level attributes without joining the full transactional schema directly.

The view is owned by the APPS schema and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it introduces no storage of its own and reflects the current state of the underlying base objects at query time. This behavior is important in EBS environments where orders are frequently updated: any committed change to the header or its related lookups is immediately visible through the view.

Underlying Base Objects

The documented dependency list for OE_AS_ORDER_HEADERS_V comprises the following objects:

Most joins to the customer and lookup objects are outer joins, so a header is not suppressed when contact, source, or lookup data is missing.

Key Columns

Common Use Cases and Queries

The view is typically used for order status reporting, operating-unit extracts, and lightweight integration feeds, particularly where readable lookup meanings are preferred over raw codes. The following examples illustrate typical access patterns.

List orders for a given operating unit with decoded status:

  • SELECT order_number, org_name, order_type, flow_status, order_total_numeric FROM oe_as_order_headers_v WHERE org_id = :p_org_id AND flow_status = 'BOOKED' ORDER BY creation_date DESC;

Retrieve a single order with customer and salesrep detail:

  • SELECT order_number, account_number, sold_to_contact, salesrep_name, sales_channel FROM oe_as_order_headers_v WHERE order_number = :p_order_number;

Produce a daily order count by source and type:

  • SELECT TRUNC(creation_date) order_date, order_source, order_type, COUNT(*) total FROM oe_as_order_headers_v WHERE creation_date >= TRUNC(SYSDATE) GROUP BY TRUNC(creation_date), order_source, order_type;

Because ORDER_TOTAL_NUMERIC is computed through a PL/SQL function invoked once per row, queries returning large result sets should apply selective predicates before aggregating totals. Joins back to OE_ORDER_HEADERS_ALL using HEADER_ID remain the standard approach when additional line-level or attribute-level detail is required.