Results for “oebv_sales_orders”

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

Overview

OEBV_SALES_ORDERS is a read-only reporting view in the Oracle Order Entry (OE) module, delivered as part of the E-Business Suite Trading Community and order management reporting layer. ETRM documents it under product code OE with the description "Retrofitted," indicating it was carried forward or reconstructed across release boundaries rather than natively authored in the current schema generation. In Oracle EBS 12.1.1 and 12.2.2 the object exists in the dictionary definitions but is frequently reported as "Not implemented in this database," depending on the installation. The view presents order header information in a denormalized, presentation-ready form, combining identifying attributes, shipping and packing instructions, conversion data, tax exemption details, and a large set of foreign-key identifiers. It is intended for read-only reporting, ad hoc query, and downstream integration extraction rather than for transactional DML. Because the view is defined WITH READ ONLY, no INSERT, UPDATE, or DELETE is permitted through it.

Underlying Base Objects

The view text is a simple equi-join of two base tables from the Order Entry schema:

• SO_HEADERS_ALL — aliased HEADER, supplying order header columns such as ORDER_NUMBER, SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, and the full set of ID and audit columns.
• SO_ORDER_TYPES_ALL — aliased ORDER_TYPE, supplying the order type NAME.

The join predicate is HEADER.ORDER_TYPE_ID = ORDER_TYPE.ORDER_TYPE_ID. No other base objects are documented in the ETRM metadata. Notably, the view does not expose the shipping method description directly; it exposes the raw code SHIP_METHOD_CODE, annotated in the view text as FK=CARRIER, meaning the value resolves to a carrier definition rather than a simple lookup meaning.

Key Columns

Several columns warrant particular attention for reporting and integration:

• ORDER_NUMBER / ORDER_TYPE_NAME — the human-readable order identifier and its type classification.
• SHIP_METHOD_CODE — the shipping method or carrier code for the order header; the documented foreign-key annotation identifies it as a carrier reference. This is the column most relevant to shipping-method analysis.
• SHIPPING_INSTRUCTIONS and PACKING_INSTRUCTIONS — free-text instructions captured on the header.
• SHIP_PARTIAL_FLAG, OPEN_FLAG, CANCELLED_FLAG, TAX_EXEMPT_FLAG — Y/N flags exposed through SO_LOOKUPS meanings via the '_LA:' label substitution mechanism, which converts stored codes into display meanings at query time.
• FREIGHT_TERMS_CODE, FOB_CODE, SHIPMENT_PRIORITY_CODE, DEMAND_CLASS_CODE, SALES_CHANNEL_CODE, ORDER_CATEGORY — further code-to-meaning columns resolved through SO_LOOKUPS, AR_LOOKUPS, or FND_COMMON_LOOKUPS.
• Identifier and audit columns — HEADER_ID, ORG_ID, CUSTOMER_ID, SHIP_TO_SITE_USE_ID, WAREHOUSE_ID, CURRENCY_CODE, and the CREATION/LAST_UPDATE audit fields, useful for joins and incremental extraction.

Common Use Cases and Queries

The view is well suited to shipping-method and order-header reporting. A typical query filtering on shipping method is:

SELECT order_number, order_type_name, ship_method_code, shipping_instructions
FROM oebv_sales_orders
WHERE ship_method_code = :p_ship_method
AND open_flag = 'Y';

Because SHIP_METHOD_CODE is a carrier code rather than a decoded meaning, joining to the carrier definition table is generally required to display a descriptive shipping method name. Other frequent scenarios include extracting open order headers by organization, auditing orders missing shipping instructions, and reporting freight terms or FOB classifications. Analysts should confirm the object is implemented in the target instance, since the ETRM metadata records it as "Not implemented in this database" and retrofitted — availability may differ between 12.1.1 and 12.2.2 environments.