Search Results so_header_id

Overview

The SO_PO_REPORT_V view is a reporting and integration object belonging to the Oracle E-Business Suite Order Entry (OE) module. Its purpose is to present a consolidated, denormalized picture of the relationship between sales orders and their associated drop-ship purchase orders. By joining sales order header and line data with purchasing header, line, and shipment data, the view exposes both the demand side (customer sales order) and the supply side (vendor purchase order) in a single result set. This is particularly valuable in drop-shipment business flows, where goods are shipped directly from a supplier to the end customer, and where the linkage between ordered, cancelled, and received quantities must be reconciled across the OE and PO modules.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a convenient reporting foundation for order management analysts, custom concurrent programs, and downstream integration extracts that need drop-ship visibility without navigating the underlying normalized schema manually. The view is documented as not implemented in this database within the ETRM repository, meaning the metadata captures its definition for reference rather than confirming an active installation in every environment.

Underlying Base Objects

The view text references a substantial set of base tables spanning OE, Purchasing, Receivables, Inventory, and Human Resources. Documented referenced base objects are listed as none, so the following are drawn from the embedded view definition:

• SO_HEADERS and SO_LINES — sales order header and line records.
• SO_DROP_SHIP_SOURCES — the critical linkage table connecting sales order lines to purchase order lines and shipments.
• PO_HEADERS, PO_LINES, and PO_LINE_LOCATIONS — the purchasing side of the drop-ship order.
• PO_VENDORS and PO_LOCATION_ASSOCIATIONS — supplier and location association data.
• RA_CUSTOMERS and RA_SITE_USES — customer and ship-to site information.
• MTL_SYSTEM_ITEMS — item segment data for both sales and purchasing items.
• SO_ORDER_HOLDS, SO_HOLD_SOURCES, and PER_PEOPLE_F — hold tracking and agent (buyer/salesperson) attribution.
• SO_ORDER_TYPES — order type name.

Key Columns

• ORDER_NUMBER, HEADER_ID, DATE_ORDERED — sales order identification and date.
• LINE_NUMBER, LINE_ID — sales order line identification.
• (NVL(ORDERED_QUANTITY,0) - NVL(CANCELLED_QUANTITY,0)) — the effective ordered quantity. Users searching for "so_quantity" will typically target this derived expression, since it is the view's representation of sellable sales order quantity.
• (NVL(POLL.QUANTITY,0) - NVL(POLL.QUANTITY_CANCELLED,0)) — effective purchase order shipment quantity.
• PO_HEADER_ID, SEGMENT1, REVISION_NUM — purchase order identification.
• CURRENCY_CODE — exposed for both sales and purchasing sides.
• SCHEDULE_DATE, NEED_BY_DATE — key date columns for schedule and demand fulfillment analysis.
• VENDOR_NAME, FULL_NAME — supplier and agent names.

Common Use Cases and Queries

Typical scenarios include auditing drop-ship order quantity alignment, identifying cancelled quantity variances between sales and purchase orders, and powering reporting extracts.

• Reconcile sales order quantities against vendor purchase order quantities.
• Identify orders on hold via hold source joins.
• Report effective so_quantity by item and customer.

SELECT order_number, line_number,
       (NVL(ordered_quantity,0) - NVL(cancelled_quantity,0)) so_quantity,
       vendor_name, need_by_date
FROM   so_po_report_v
WHERE  segment1 = :item
ORDER BY order_number;