Search Results ship_confirm_status

Overview

SO_LINES_CURRENT_DEMAND_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped under the Order Entry (OE) product family. It consolidates order-header, order-line, and order-type information into a single denormalized result set that exposes the current demand picture for sales order lines. The view is documented as VALID in both EBS 12.1.1 and 12.2.2 and is intended for reporting and lightweight integration scenarios where a flattened, read-only representation of order-line demand is required without navigating the full OE entity model.

The view's distinguishing characteristic is that it does not simply project columns from the base tables. It also invokes server-side functions from the OE_QUERY package to derive display values such as formatted line numbers, shipment numbers, pick-released quantities, and open backordered quantities. This makes the view a practical shortcut for operational queries, but it also means its cost is higher than a plain join and that its output reflects the state of the underlying data at execution time rather than any persisted snapshot.

Underlying Base Objects

The documented metadata lists the following referenced base objects:

• OE_QUERY (PACKAGE) — supplies the PL/SQL functions LINE_NUMBER, SHIPMENT_NUMBER, RELEASED_QUANTITY, and OPEN_BACKORDERED_QUANTITY used in the select list.
• SO_HEADERS (VIEW) — the OE order headers view, supplying ORDER_NUMBER, ORDER_TYPE_ID, CUSTOMER_ID, ORIGINAL_SYSTEM_REFERENCE, and HEADER_ID.
• SO_LINES (VIEW) — the OE order lines view, supplying line-level attributes including quantities, flags, status codes, and item identifiers.
• SO_ORDER_TYPES (SYNONYM) — resolves to the order type definition used to derive ORDER_TYPE_NAME.

The view joins these sources on the keys SOT.ORDER_TYPE_ID = H.ORDER_TYPE_ID and H.HEADER_ID = L.HEADER_ID, producing one row per order line (including option lines, which are flagged via OPTION_FLAG). Because SO_LINES and SO_HEADERS are themselves views over the OE base tables, the effective dependency chain extends to the underlying OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL structures with their associated _ALL/_TL relationships and security policies.

Key Columns

• ORDER_NUMBER / ORDER_TYPE_NAME / CUSTOMER_ID — header-level identifiers for user-facing reporting and customer segmentation.
• LINE_ID, PARENT_LINE_ID, ATO_LINE_ID — structural hierarchy keys used to reconstruct configured or bundled line relationships.
• LINE_NUMBER, SHIPMENT_NUMBER, OPTION_NUMBER — derived display identifiers; OPTION_NUMBER is populated only when OPTION_FLAG = 'Y'.
• DATE_REQUESTED_CURRENT, DEMAND_STREAM_ID — scheduling and demand-stream attribution for each line.
• ORDERED_QUANTITY, CANCELLED_QUANTITY, SHIPPED_QUANTITY, INVOICED_QUANTITY — the core demand and fulfillment quantity set. CANCELLED_QUANTITY, SHIPPED_QUANTITY, and INVOICED_QUANTITY are wrapped in NVL(...,0) so nulls are returned as zero.
• PICK_RELEASED_QUANTITY, OPEN_BACKORDERED_QUANTITY — derived via OE_QUERY.RELEASED_QUANTITY and OE_QUERY.OPEN_BACKORDERED_QUANTITY.
• OPEN_FLAG, ATO_FLAG — status flags, defaulted to 'N' when null.
• PICK_RELEASE_STATUS, SHIP_CONFIRM_STATUS, MFG_RELEASE_STATUS, SERVICE_INTERFACE_STATUS — workflow status columns sourced from line flexfield segments S2, S4, S25, and S27.

The presence of INVOICED_QUANTITY is significant for users researching this view; it provides a straight read of the line's invoiced quantity (zero when not populated), enabling reconciliation between order, shipment, and billing without a separate join to AR interfaces.

Common Use Cases and Queries

Because the view exposes both demand quantities and derived status, it is commonly used for open-order reporting, shipment-versus-invoice reconciliation, and backorder analysis. A typical query to compare ordered, shipped, and invoiced quantities for open lines resembles the following:

SELECT order_number,
       line_number,
       inventory_item_id,
       ordered_quantity,
       shipped_quantity,
       invoiced_quantity
FROM   apps.so_lines_current_demand_v
WHERE  open_flag = 'Y'
  AND  ordered_quantity > NVL(shipped_quantity, 0);

For backorder-focused reporting, callers constrain on derived quantities:

SELECT order_number, shipment_number, open_backordered_quantity
FROM   apps.so_lines_current_demand_v
WHERE  open_backordered_quantity > 0;

When using the view, note that the OE_QUERY function calls execute once per returned line, so restricting the result set with ORDER_NUMBER, CUSTOMER_ID, or DATE_REQUESTED_CURRENT predicates is advisable before scanning for aggregate reporting. Always reference the view with the APPS schema prefix or via an APPS synonym, and grant SELECT explicitly to any reporting or integration schema that needs access.