Search Results so_headers_v

Overview

SO_HEADERS_V is a reporting-oriented view in the Oracle E-Business Suite Order Entry (OE) module that exposes order header information from the OE_ORDER_HEADERS_ALL base table. Unlike many EBS "public" views, SO_HEADERS_V is documented as not implemented in the database, meaning it exists as a seeded dictionary definition or legacy artifact rather than an actively created database object in all environments. Its primary role is to present a denormalized, single-row-per-order-header structure suitable for reporting, integration, and downstream processing where a stable, readable column naming convention is preferred over the raw transactional table.

The view returns a comprehensive projection of the order header record, including audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE), order identification attributes (ORDER_NUMBER, ORDER_CATEGORY), source system information (ORIGINAL_SYSTEM_SOURCE_CODE, SOURCE_HEADER_ID), and a wide range of customer, pricing, shipping, and payment fields. The column naming and column set make it useful in contexts where consumers require a stable interface that abstracts the physical layout of the underlying OE_ORDER_HEADERS_ALL table.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and it is flagged as "Not implemented in this database." The view text, however, clearly selects from a single header source aliased as H, whose column set is that of OE_ORDER_HEADERS_ALL. The view is therefore a simple projection over that table, with no joins to lookup or reference tables in the documented text.

Because the view is documented as not implemented, deployments should not assume it exists at runtime. The authoritative base object remains OE_ORDER_HEADERS_ALL, and any query against SO_HEADERS_V must first confirm its presence via ALL_VIEWS or the appropriate data dictionary before relying on it.

Key Columns

• HEADER_ID — Primary identifier for the order header and join key to order lines (OE_ORDER_LINES_ALL) and other order objects.
• ORDER_NUMBER — Human-readable order number presented to users.
• ORDER_CATEGORY / ORDER_CATEGORY_CODE — Category of the order; ORDER_CATEGORY is projected twice, once as the base attribute and once as ORDER_CATEGORY_CODE, a naming convention common in earlier EBS views.
• ORIGINAL_SYSTEM_SOURCE_CODE — Identifies the source system that originated the order, relevant to source_order_type-style queries.
• SOURCE_HEADER_ID — Reference to the originating header in the source system.
• ORDER_TYPE_ID — Foreign key to the order transaction type, controlling order behavior and workflow.
• CUSTOMER_ID, SHIP_TO_SITE_USE_ID, INVOICE_TO_SITE_USE_ID — Customer and site references.
• OPEN_FLAG, CANCELLED_FLAG — Status flags indicating whether the order is open or cancelled.
• CURRENCY_CODE, CONVERSION_TYPE_CODE, CONVERSION_RATE — Currency and conversion attributes.
• SALESREP_ID, SALES_CHANNEL_CODE, PRICE_LIST_ID — Sales and pricing context.
• PAYMENT_TYPE_CODE, PAYMENT_AMOUNT, CREDIT_CARD_* — Payment and credit card details.
• _SVRID columns — Surrogate/version identifiers used for Oracle Sales Online and synchronization-related processing.

Common Use Cases and Queries

Typical uses include order extraction for reporting, reconciliation against source systems, and building integration payloads. Because the view may not exist in every environment, always confirm its presence and fall back to OE_ORDER_HEADERS_ALL where needed.

Example: retrieving orders by source system.

SELECT HEADER_ID, ORDER_NUMBER, ORDER_CATEGORY_CODE, ORIGINAL_SYSTEM_SOURCE_CODE, SOURCE_HEADER_ID, DATE_ORDERED, OPEN_FLAG, CANCELLED_FLAG FROM SO_HEADERS_V WHERE ORIGINAL_SYSTEM_SOURCE_CODE = 'ORDER MANAGEMENT';

Example: open orders with customer and currency context.

SELECT HEADER_ID, ORDER_NUMBER, CUSTOMER_ID, CURRENCY_CODE, CONVERSION_RATE, SALESREP_ID, PRICE_LIST_ID FROM SO_HEADERS_V WHERE OPEN_FLAG = 'Y' AND CANCELLED_FLAG = 'N' ORDER BY DATE_ORDERED DESC;

Example: joining to order lines for detailed reporting.

SELECT h.ORDER_NUMBER, h.ORDER_CATEGORY, l.LINE_NUMBER, l.ITEM_ID FROM SO_HEADERS_V h, OE_ORDER_LINES_ALL l WHERE h.HEADER_ID = l.HEADER_ID AND h.OPEN_FLAG = 'Y';

These patterns align with the view's documented projection over OE_ORDER_HEADERS_ALL and support both operational reporting and source-system reconciliation requirements.