Results for “so_headers_oexorrso_v”

4 results




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

Overview

SO_HEADERS_OEXORRSO_V is a reporting and integration view in the Oracle E-Business Suite Order Entry (OE) module. It presents order header information from the SO_HEADERS table, enriched with denormalized descriptive attributes drawn from the order type and customer master data. The view is intended to expose a single, flattened record per sales order header, which simplifies downstream reporting, custom concurrent programs, and integration extracts that would otherwise require multiple joins across the order management and receivables schemas.

The view is documented in ETRM as a reporting object and is not marked as a database-implemented object in the reference database. As such, it is best understood as a logical definition whose column set and joins reflect the standard OE data model; availability depends on whether the object has been created in a given environment.

Underlying Base Objects

The view is defined as a join over three base objects:

  • SO_HEADERS — the primary source, aliased as H, supplying all header-level columns including identifiers, dates, flags, shipping attributes, pricing attributes, and the organization identifier.
  • SO_ORDER_TYPES — aliased as SOT, joined on ORDER_TYPE_ID, supplying the order type name.
  • RA_CUSTOMERS — aliased as RAC, joined on CUSTOMER_ID, supplying the customer name and customer number.

Both joins to SO_ORDER_TYPES and RA_CUSTOMERS are outer joins (indicated by the (+) operator), so header rows are retained even when no matching order type or customer record exists. The ETRM metadata records no separately documented base objects, but the view text itself enumerates these three tables as the referenced sources. The view also invokes OE_QUERY.ORDER_TOTAL to derive the ordered amount as an inline function call rather than a table join.

Key Columns

Common Use Cases and Queries

The view supports order status reporting, fulfillment extracts, and customer-facing order summaries. A typical query filters by operating unit and open status:

  • SELECT ORDER_NUMBER, ORDER_TYPE, CUSTOMER_NAME, DATE_ORDERED, TOTAL_AMOUNT FROM SO_HEADERS_OEXORRSO_V WHERE ORG_ID = :p_org_id AND OPEN_FLAG = 'Y';
  • SELECT HEADER_ID, ORDER_NUMBER, SHIP_PARTIAL_FLAG FROM SO_HEADERS_OEXORRSO_V WHERE SHIP_PARTIAL_FLAG = 'Y' AND CANCELLED_FLAG = 'N';
  • SELECT CUSTOMER_NUMBER, COUNT(*) FROM SO_HEADERS_OEXORRSO_V WHERE DATE_ORDERED >= :p_from_date GROUP BY CUSTOMER_NUMBER;

Because the view exposes SHIP_PARTIAL_FLAG alongside shipping method, warehouse, and customer attributes, it is well suited to building partial-shipment analysis and fulfillment exception reports without additional joins.